-
Notifications
You must be signed in to change notification settings - Fork 605
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
Can we reduce npm package size? #649
Comments
Examples are responsible for 3.7M. They are usually helpful for development, but are generally useless in an npm installation. We could remove them from the npm package. Temporary |
In a way, examples are part of the documentation, which is useful to include. I don't follow how they end up at 3.7 MB though. Maybe that's nested node_modules that you had locally when you published, and npm just published them along with everything else? If that's the issue, we should definitely exclude those nested node_modules. |
Jörn, you're correct, just found the culprit
|
Probably simpler would be adding those to |
Good point. |
These files were already in |
Can it be worked around using explicit |
I believe not since the npm-linked issue is about |
Could try to remove the nested |
Used negate expressions in package.json files entry, although it goes against recommendation below, because that's the only thing that worked. > "The consequences are undefined" if you try to negate any of the files > entries (that is, "!foo.js"). Please don't. Use .npmignore. https://github.com/npm/npm/wiki/Files-and-Ignores#details Fixes globalizejs#649 Closes globalizejs#658
Used negate expressions in package.json files entry, although it goes against recommendation below, because that's the only thing that worked. Read the github references below for details. > "The consequences are undefined" if you try to negate any of the files > entries (that is, "!foo.js"). Please don't. Use .npmignore. https://github.com/npm/npm/wiki/Files-and-Ignores#details Fixes globalizejs#649 Closes globalizejs#658
dist/.build
for another ~1M.The text was updated successfully, but these errors were encountered: