🐛 VS Code Extension requires Disable->Enable to clear reported problems/diagnostics

[dkattan]

Prerequisites

• I'm using the latest version
• I've read the relevant documentation
• I've searched for existing issues
• I've checked the list of known issues
• I've read the issue reproduction guide

Reproduction url

https://vscode.dev

Reproduction access

• I've made sure the reproduction is publicly accessible

Description of the issue

This is an issue purely with the VS Code Extension.

In my instance there were a bunch of "Unlisted dependency" problems being reported. I told Copilot to fix all #problems in the workspace.

It kept churning and churning because it was resolving the issue but it was still showing up in the Problems pane.

I then ran knip from the CLI and it reported no issues.

I ran the Restart Knip Server command and the issues didn't go away.

I then disabled the extension and re-enabled it and it no longer reported the issues.

[webpro]

That's an awful experience. Trying this now and things seem fine, both from a root or sub workspace. When I install the dependency, the package.json visibly updates in the editor, and I can see a restart sequence starting with "Creating options" in the Output → Knip panel.

So there should be a restart of the plugin just by a modified package.json.

Maybe the editor didn't know about or didn't propagate the saved package.json?

Do you experience the same with a similar tool/extension like ESLint?

Btw here's the line that makes it happen:

knip/packages/language-server/src/server.js

Line 30 in 78111c9

const RESTART_FOR = new Set(['package.json', ...KNIP_CONFIG_LOCATIONS]);

[OliverJAsh]

I'm facing a similar issue with other Knip errors. I haven't encountered this issue with other tools like ESLint. The stale errors do not disappear when I restart the Knip server nor if I edit the nearest package.json (monorepo). Here's a screen recording:

Screen.Recording.2026-02-18.at.08.07.35.mov