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

Move babel and other command line dependencies to devDependencies #38

Open
lewchuk opened this issue May 9, 2018 · 2 comments
Open

Comments

@lewchuk
Copy link

lewchuk commented May 9, 2018

It looks like inclusion of babel-cli and the babel-preset-* packages in dependencies adds 45 MB (almost 50%) to the production dependencies of anyone including this library in their dependencies.

Currently:

> yarn install --production
> du -sh node_modules
145M	node_modules

After moving babel-* to devDependencies:

> yarn install --production
> du -sh node_modules
106M	node_modules

Moving the babel packages to dev-dependencies still lets anyone run the command line version of the code when only yarn install --production.

@lewchuk
Copy link
Author

lewchuk commented May 9, 2018

Not sure between yarn.lock and package-lock.json how the dependencies are managed otherwise I'm happy to open a PR.

@atlanteh
Copy link

Basically if you move the dependencies to to dev-dependencies and run "npm install" & "yarn install" I think these files should be updated automatically.

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

2 participants