Removing node_modules, running npm ci leaves diagnostics behind in ts and tsconfig files

[jakebailey]

Acknowledgement

• I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment

I've been having quite a few watcher problems recently, and have been collecting log files to try and report the problem.

• https://gist.github.com/jakebailey/af583ce2d14b6a1a30339769a3300416
• https://gist.github.com/jakebailey/573e83c9a81a0e0c950c603722e3ed29
• https://gist.github.com/jakebailey/4ad4ce74fbd86e9588a5775e9c89fe2e

The last two come from doing npm ci inside of https://github.com/jakebailey/every-ts and https://github.com/jakebailey/hereby, but the first one is a very very simple project: https://github.com/jakebailey/ts-watcher-issue-1

In that one, the first trace is just me opening the already-installed repo, running rm -rf node_modules, waiting for the errors to appear in index.ts and tsconfig.json, and then doing npm ci. The errors in tsconfig.json do not disappear.

In this example, it also reproduces in --watch mode.

I also experience this within the TS repo, but I haven't been able to get a trace of that one yet.

@sheetalkamat