Bug report 2: NPM task detection fails to parse valid package.json

Support Bug Reports
,
7

Thanks for the feedback on the workaround, that’s a useful signal. The comparison with VS Code on the same repo and machine is especially helpful, since it rules out the upstream race only hypothesis.

To dig further, can you share a couple more details:

  1. A screenshot or a snippet from your settings.json showing npm.autoDetect and npm.exclude, and which scope they’re set in (User or Workspace). I want to make sure the setting is actually applied, because with off the built-in npm task provider shouldn’t scan at all.
  2. The VS Code version where it works (stable channel, insiders, exact build).
  3. Logs from View > Output > Tasks (dropdown on the right) at the moment the toasts pop up. It usually shows which provider is crashing and on which file.
  4. Please confirm the VS Code test was on the same Windows machine, same repo state, at the same time, with Cursor closed.

In parallel, I’ve reported this to the team and mentioned the A/B test with VS Code and that the workaround didn’t help.