CRA Typescript: Compiling forever, if node_modules getting changed, while webpack is running

Created by: johannwagner

Is this a bug report?

Yes.

Did you try recovering your dependencies?

Yes.

Which terms did you search for in User Guide?

typescript, webpack, hangs

Environment

Whoops.

$ create-react-app --info

Environment Info:
(node:5138) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '1' of null
    at a.run.then.e (/usr/lib/node_modules/create-react-app/node_modules/envinfo/dist/envinfo.js:1:97255)
(node:5138) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:5138) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

• Node 11
• Create React App 2.1.0
• npm 6.4.1

Steps to Reproduce

1. Create a new CRA project with --typescript
2. Link another npm package into this project.
3. Updates files, which are included in the project, in the linked project

Expected Behavior

(Write what you thought would happen.) Webpack should compile the new files.

Actual Behavior

Webpack hangs forever on Compiling.... If you terminate the process, it exits with exit code 0, but the compile process won't terminate and is stuck on 100% CPU forever.

Reproducible Demo