External npm package update not correctly detected

Avatar
Petr Gurecky
Created

Hi.

Developing React project in WebStorm...

  1. Execute npm install xyz@latest in external console resulting in new package version in package.json and node_modules
  2. WebStorm shows notification that package.json changed and you should run npm update (whitch results in no change, of course)
  3. WebStorm keeps showing this notification even after restart even though package.json and package-lock.json and node_modules have the new version.

Thanks if t here is some fix for this (beside disabling the notification).

Votes

0

Share

2 comments
Avatar
Elena Pogorelova
Created

does the issue only occur with one particular dependency that is reported to be not installed/updated, or with each and every package installed externally? Can be caused by wrong mtime of updated files, see https://youtrack.jetbrains.com/issue/WEB-34196/Files-in-node_modules-cached-and-old-content-opens-and-parsed-in#focus=Comments-27-5015093.0-0

0
Avatar
Petr Gurecky
Created

Thank you for the reply. It happened in two cases.

I've checked the content of node_modules folder, package.json, package-lock.json and all were showing correct (new) version. But warning within package.json was saying that old version is installed.

I deleted the package manually from node_modules folder and ran npm install again. Warning is gone since then.

But still it's strange and could occur again I guess.

0

Please sign in to leave a comment.