-
Notifications
You must be signed in to change notification settings - Fork 486
Reduce installed size #622
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
Comments
Previously: #583. Are you using npm v2? |
Yep. Sorry, searched issues and didnt find that. I guess the fix then is for me to use something that dedupes babel modules. |
Hey Max! Good to hear from ya Yep, as @jfirebaugh, npm v2 is the cause of much of our installation troubles and will cause those troubles unavoidable on practically any module that uses Babel. That said: even with npm v3, size is still an issue and one that we'd love to pare down, so that it's a no-brainer install even for those with very minimal requirements. So reducing size would be very welcome and I'm open to ideas. We use babylon as the parser central to documentation.js, so some reliance on the babel ecosystem would be hard to work away from - supporting a different parser would mean supporting a different AST format, so it might be a door to more complexity rather than less. Besides Babel, we also just need to keep track of which dependencies are consuming space in node_modules and whether they're pulling their weight.
|
Closing - happy to accept PRs implementing any significant install size improvements. The problem encountered here is with npm v2, though, so it's not something I can fix. |
Hi, I noticed the installed size (of dependencies only, not devDependencies) is 410mb.
It looks like ~%80 is coming from babel related modules (which I don't personally use). Is there any way to possibly make these optional, or have a lighter weight distribution in general?
Loving the module so far, thanks!
The text was updated successfully, but these errors were encountered: