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

FR: Separate deps and devDeps after running yarn eject #3253

Closed
iamclaytonray opened this issue Oct 7, 2017 · 2 comments
Closed

FR: Separate deps and devDeps after running yarn eject #3253

iamclaytonray opened this issue Oct 7, 2017 · 2 comments

Comments

@iamclaytonray
Copy link
Contributor

After running yarn eject....

Is there are reason why all dependencies are in "dependencies": { ... }? Things like webpack, eslint, and others should go in "devDependencies": { ... }. So, I guess the feature request would be to separate deps based on where they normally go, unless there is an existing option that I haven't seen in the docs.

@iamclaytonray iamclaytonray changed the title FR: Separate deps and devDeps FR: Separate deps and devDeps after running yarn eject Oct 7, 2017
@miraage
Copy link

miraage commented Oct 9, 2017

#2696

@Timer
Copy link
Contributor

Timer commented Oct 9, 2017

This is intentional because everything would be a development dependency, and the ecosystem works better under dependencies for things like Heroku etc, see the issue linked above.

@Timer Timer closed this as completed Oct 9, 2017
@lock lock bot locked and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants