Local registry used in testing doesn't work in all cases

[aurelien-baudet]

I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request

Scope (check one with "x")

[ ] <root>
[ ] @zetapush/cli
[ ] @zetapush/client
[ ] @zetapush/cometd
[ ] @zetapush/common
[ ] @zetapush/core
[ ] @zetapush/create
[ ] @zetapush/http-server
[ ] @zetapush/platform-legacy
[x] @zetapush/testing
[ ] @zetapush/troubleshooting
[ ] @zetapush/user-management
[ ] @zetapush/worker

Current behavior

A dependency of @zetapush/common:0.34.2 published on official npm registry.
I use dependency @zetapush/common:0.34.2 in my code.
I made changes in packages/common sources that I want to test locally even for pushed version.
When I launch tests that push the worker, a local verdaccio registry proxy is setup and platform uses this registry through localtunnel.
However, the downloaded artifact is the version published on official NPM. This is the behavior described by verdaccio. If a version exists both in verdaccio and in npm, it uses the npm one.

I also tested using a dist tag "testing" and to explicitly use "testing" version in package.json. It downloads the right version of @zetapush/common. However, @zetapush/common has dependencies. Those dependencies fail with wrong sha1 verification.

Expected behavior

I expect that when I use npm().dependencies() in given part of my test always overrides the dependency even if it exists on npm.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

• Operating System:
• Node Version: X.Y.Z
• Npm Version: X.Y.Z
• @zetapush/* Version: X.Y.Z