You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
iamclaytonray
changed the title
FR: Separate deps and devDeps
FR: Separate deps and devDeps after running yarn ejectOct 7, 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.
After running
yarn eject
....Is there are reason why all dependencies are in
"dependencies": { ... }
? Things likewebpack
,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.The text was updated successfully, but these errors were encountered: