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
Not a bug report, just curious why all packages are put under dependencies in package.json and none under devDependencies when ejecting with react-scripts 1.0.13. Surely things like webpack, chalk, and eslint are not runtime dependencies? I can't see it explained anywhere and I know that previously most of the packages would go under devDependencies as I am using an ejected version of an old create-react-app.
The text was updated successfully, but these errors were encountered:
It was removed in 1.0.8 (#2657).
It looks easy to fix on the paper.
Welcome, dependencies.
I think they should be added as devDependencies except promise, whatwg-fetch, object-assign which are used by polyfills.js as an additional entry.
Not a bug report, just curious why all packages are put under
dependencies
in package.json and none underdevDependencies
when ejecting withreact-scripts 1.0.13
. Surely things like webpack, chalk, and eslint are not runtime dependencies? I can't see it explained anywhere and I know that previously most of the packages would go underdevDependencies
as I am using an ejected version of an old create-react-app.The text was updated successfully, but these errors were encountered: