Why eslint, react types and typescript is in the dependencies and not dev dependencies? #43277
-
With the changes in the Why is this intentional ? "dependencies": {
"@types/node": "18.11.9",
"@types/react": "18.0.25",
"@types/react-dom": "18.0.9",
"eslint": "8.28.0",
"eslint-config-next": "13.0.4",
"next": "13.0.4",
"react": "18.2.0",
"react-dom": "18.2.0",
"typescript": "4.9.3"
}, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
I think it is because they really want to start pushing forward the output standalone mode: Though I wonder if they considered That being said, when it comes to this type of apps, rather than packages or libraries, there is a blurry division when it comes to dependencies and devDependencies which I am not going to jump into, in the interest of time (it might explode into an actual lengthy article). And you could just rearrange the |
Beta Was this translation helpful? Give feedback.
-
I guess it was all fine if one had to do or they could simply add a prompt to confirm It doesn't really matter at the end of the day, and as you suggested, one can also re-arrange the |
Beta Was this translation helpful? Give feedback.
I think it is because they really want to start pushing forward the output standalone mode:
#42218
Though I wonder if they considered
npm run audit
situations, where we add--production
to the command, to only run it ondependencies
and avoid having our CI/CD complain about a 4th level dependency ofsome-random-dev-Dep
having some CVE, which we know doesn't impact our codebase.That being said, when it comes to this type of apps, rather than packages or libraries, there is a blurry division when it comes to dependencies and devDependencies which I am not going to jump into, in the interest of time (it might explode into an actual lengthy article). And you could just rearrange the
package.…