Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't think this works with Yarn #11

Closed
wearhere opened this issue Mar 29, 2017 · 1 comment
Closed

Don't think this works with Yarn #11

wearhere opened this issue Mar 29, 2017 · 1 comment

Comments

@wearhere
Copy link
Contributor

wearhere commented Mar 29, 2017

Files are not copied over upon doing yarn add <install-files-using-package>, nor on yarn upgrade <install-files-using-package>. No error, just no files. yarnpkg/yarn#2878 might explain no files on upgrade but idk about no files on install. Haven't yet done local testing to see whether/when the install scripts are executed.

Tested with yarn 0.21.3.

@wearhere
Copy link
Contributor Author

wearhere commented Mar 29, 2017

A workaround, for the meantime: after adding/upgrading an install-files-using module, from the project root, do

cp -r node_modules/path/to/module/source/ .

If the install-files-using module has put its files-to-be-installed in source/ (like here), this will do the same thing as the install script (recursively merge source/ into the current directory).

So then at least you continue to get the benefits of using npm to version / distribute your files even if they're not installed atm.

skeggse pushed a commit that referenced this issue May 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant