You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When npm workspaces are used, npm creates for each workspace a symbolic link under node_modules that points to the module in the workspace. The problem is that this extension finds it and then proposes two options when you try for example to list routes:
If there are no use cases for looking inside node_modules, these folders can just be ignored. Otherwise, it may be possible to use fs.realpath to make sure the same absolute path isn't listed twice.
The text was updated successfully, but these errors were encountered:
When npm workspaces are used, npm creates for each workspace a symbolic link under

node_modules
that points to the module in the workspace. The problem is that this extension finds it and then proposes two options when you try for example to list routes:If there are no use cases for looking inside
node_modules
, these folders can just be ignored. Otherwise, it may be possible to usefs.realpath
to make sure the same absolute path isn't listed twice.The text was updated successfully, but these errors were encountered: