npm update behaves strangely with local path dependencies

[doug-wade]

I have a package A that has a local file path dependency on another package B. When I run an npm install in A, I get the correct version of A; however, when I run an update in A, I get the most recent version of package B from the repository. I believe that instead, you should still get the local version of B. I understand that for most users, this isn't a very common behavior, since you'd be using link to test your local copy of your node module; however, at Redfin we're migrating from a monorepo that used local path dependencies to a private repository using sinopia, and this is causing issues during the migration (since we have an experimental version published to sinopia, but we want most developers to use the version on HEAD for the most part).

[npm-robot]

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.