Warnings not always shown

Describe the bug

When running npm start, the output won’t show all of the warnings in the project. After editing the files, the warnings start appearing.

(Write your answer here.)

Did you try recovering your dependencies?

NPM Version 6.14.11

Environment

Environment Info:

current version of create-react-app: 5.0.0 running from C:\Users\eluch\AppData\Roaming\npm-cache_npx\3452\node_modules\create-react-app

System: OS: Windows 10 10.0.19043 CPU: (6) x64 Intel® Core™ i5-9600K CPU @ 3.70GHz
Binaries: Node: 14.16.0 - D:\Program Files\nodejs\node.EXE
Yarn: Not Found npm: 6.14.11 - D:\Program Files\nodejs\npm.CMD Browsers: Chrome: Not Found Edge: Spartan (44.19041.1266.0), Chromium (96.0.1054.62) Internet Explorer: 11.0.19041.1202 npmPackages: react: ^17.0.2 => 17.0.2 react-dom: ^17.0.2 => 17.0.2 react-scripts: 5.0.0 => 5.0.0 npmGlobalPackages: create-react-app: Not Found

Steps to reproduce

(Write your steps here:)

1. Run npm start
2. See the console output, doesn’t show all of the warnings.
3. Edit and save a file where you know there should be a warning (e.g. React Hook useEffect has missing dependencies)

Expected behavior

I would expect the warnings (and errors) of the project to be shown.

Actual behavior

Not all of the warnings are shown in the console output.

Reproducible demo

I will try to add a reproducible demo if this is really not a known bug that everyone can reproduce.

[cristianlivella]

Is there any update here?

It’s getting very annoying because I’m often convinced everything is okay, I submit my work to my repository, and I get warnings when I see the continuous deployment build fail.

[kitsunekyo]

here’s a reproduction repo: https://github.com/kitsunekyo/cra5-eslint-not-emitting

when i run yarn start i sometimes get correct eslint emits, and sometimes absolutely no eslint output. it appears to be completely random.

if its already running, and i hit save on App.tsx once, the eslint error will correctly show up again.