We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've seen quite a few reports like this: https://twitter.com/schep_/status/819642790137200641. We need to figure out if it's Yarn bug causing it or not.
If it is caused Yarn we should disable the integration until it's more stable. This leaves a bad impression on React.
The text was updated successfully, but these errors were encountered:
It indeed was the yarn integration. Tho still not as small as you're expecting it to be.
$ rm -rf node_modules && npm install && du -sh node_modules 274M node_modules/
Sorry, something went wrong.
Will need to investigate, thanks. Probably some dependencies have updated their dependencies and resulted in duplicate near identical trees.
The size issue was worked around in 0.9.0 so closing this. 🎊
No branches or pull requests
I've seen quite a few reports like this: https://twitter.com/schep_/status/819642790137200641. We need to figure out if it's Yarn bug causing it or not.
If it is caused Yarn we should disable the integration until it's more stable. This leaves a bad impression on React.
The text was updated successfully, but these errors were encountered: