Package react-scripts is installed as not a dev dependency

Is this a bug report?

Yes

Can you also reproduce the problem with npm 4.x?

Yes

Which terms did you search for in User Guide?

(Write your answer here if relevant.)

Environment

1. node -v: 8.0.0
2. npm -v: 5.0.3
3. yarn --version (if you use Yarn):
4. npm ls react-scripts (if you haven’t ejected): 1.0.10
5. create-react-app --version: 1.3.3

Then, specify:

1. Operating system: macOS Sierra
2. Browser and version (if relevant):

Steps to Reproduce

nvm use 8
npm install --global create-react-app
create-react-app test-app
cd test-app
cat package.json

Expected Behavior

Package react-scripts should appear in devDependencies section

Actual Behavior

Package react-scripts appears next to react-dom in dependencies section.

Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

[stevenvachon]

Semantics.

[gaearon]

It fixes deployment issues on some hosting providers that assume only dependencies are needed for the build. The line is also very thin in frontend development. None of them are “runtime” dependencies because we don’t have a server and they all get bundled into a single file. So if we were pedantic then we would have to declare everything as devDependencies, including React itself. I just figured that it’s not worth conceptual overhead anyway since distinction is largely arbitrary. For example polyfills could be categorised as either.