Thanks for reporting.

I have three questions:

1. What is displayed to console when you click on "do it for me" button? Or maybe you are running npm i directly?

2. Are you using in fact npm i or other package manager? Your project contains yarn.lock or pnpm-lock.yml files?

3. When you reload vscode it is fixed or the message of "ready to install" still exists?

Thanks!

1. Yes, I'm running npm i myself. I don't see a "do it for me" button
2. 2. Yes, using npm
3. Reloading VSCode doesn't fix the issue. I even reinstalled the extension, same issue

Oddly, it seems to work, a bit. See screenshot below. Moment is flagged OK, but util-dynamodb is still saying to un the install command, even though I have.

Would it be feasible for you to delete the "node_modules" folder and run "npm i" again? I suspect it's some defect within node_modules that may be causing problems (this usually happens after many updates to npm itself, or when using other package managers).

I too am experiencing this issue which seemed to appear pretty recently as one of the projects wasn't showing the ''now run your package manager." message but now it is that project and another one I just created. There aren't any error indicators in the vscode output window so it's not clear what's going on.

I have updated vscode a few times so perhaps it's related?
VSCode Version: 1.78.1

@backtoyoujames I suspect this problem is related to the missing file package-lock.json, which would only be created after npm install. And since the file doesn't exist and the extension is watching this file for "modifications" (and not for "creation", too), it fails to update the diagnostics and it will always display "now run your package manager" (closing and opening vscode should do the trick).

Another related issue is if you are using pnpm or yarn, which are currently not supported.

However, PR #22 should resolve the first case and add support for pnpm. yarn is not yet supported.

I'm still having this issue despite having a package-lock.json file and using npm.

@paul-uz Restarting vscode the problem persists? You can create a reduced case for I test?

@paul-uz Restarting vscode the problem persists? You can create a reduced case for I test?

Yup restarted VSCode several times, same thing every time.

@paul-uz It's a little weird. Can you create a reduced project? Maybe only package.json could help to understand. But if you could generate a reduced project it would help more. So I can see if PR is the solution or even improve it.

I have this happen on npm workspaces!

The main package.json doesnt have this error but any inner package.json keeps saying this :p

The main package.json doesnt have this error but any inner package.json keeps saying this :p

You have package.json in a non-root path? Maybe this need to be fixed, because I never do in that way. I will check in this week.

The main package.json doesnt have this error but any inner package.json keeps saying this :p

You have package.json in a non-root path? Maybe this need to be fixed, because I never do in that way. I will check in this week.

It's quite a common thing with a monorepo

maybe we can turn it off?

Must be fixed now via #22.

but it still isnt merged 😔

Yeah, I just asked @mskelton if he will approves the PR.

I have published a fork extension called npm-outdated-plus with this changes.