React scripts start/build does nothing

[leandrohsilveira]

Is this a bug report?

Yes.

Did you try recovering your dependencies?

Yes.
It happens after create app.
Happens with both npm i and yarn (Removed node_modules before each attempt).

$ npm --version
6.4.1

$ yarn --version
1.9.4

Which terms did you search for in User Guide?

Searched for "nothing", "exit", "start", "build". Found nothing related.

Environment

$ npx create-react-app --info

Environment:
  OS:  Windows 10
  Node:  8.12.0
  Yarn:  1.9.4
  npm:  6.4.1
  Watchman:  Not Found
  Xcode:  N/A
  Android Studio:  Not Found

Packages: (wanted => installed)
  react: ^16.5.1 => 16.5.1
  react-dom: ^16.5.1 => 16.5.1
  react-scripts: 1.1.5 => 1.1.5

Steps to Reproduce

1. npm i -g create-react-app
2. create-react-app <app_name>
3. npm start or yarn start

Expected Behavior

Start development server.

Actual Behavior

$ yarn start
yarn run v1.9.4
$ react-scripts start
Done in 1.30s.

And nothing else.

Here is the output of my create-react-app command:
https://gist.github.com/leandrohsilveira/af9a2ce04da5f8d4f3b42b5a263635d1

[Timer]

Hmm, this is exceptionally odd ...

Are you able to run other Node scripts on your system? Did this problem persist after a reboot?

[leandrohsilveira]

Hmm, this is exceptionally odd ...

Are you able to run other Node scripts on your system? Did this problem persist after a reboot?

Yes, all NPM scripts works fine.

I was suspecting that the problem only occurred on my work computer, but the same thing happened on my home computer.

An old project of mine created in July 2018 works fine. The dependencies of this project are:

"react": "^16.4.1",
"react-dom": "^16.4.1",
"react-scripts": "1.1.4",

[leandrohsilveira]

It works with Docker, maybe something with OS?

[pmosconi]

Hi, I'm having the same issue and I traced it to my antivirus program (TrendMicro Internet Security): if I disable it react-scripts start works fine.
I'm bringing the issue to TM's attention.

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[stale]

This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue.