Current Behavior:

⚠This works with npm 6⚠

We have an internal bitbucket repository, let say at https://my.bb.intern.
One dependency is installed via git url, so in the package.json the entry says

"@bla/foo": "git+https://my.bb.intern/.....#1384"

We tried to install a new commit hash with

npm i -D "git+https://my.bb.intern/.....#2223"

which fails with npm 7.6.3, but works with npm 6.x

Expected Behavior:

Same behaviour like in npm 6.

Environment:

OS: Windows 10
Node: 14.15.3
npm 7.6.3
Git for Windows: 2.31.0.1

Here is one log

Weird behaviour

The git repo of the dependency has been cloned into the current working dir

cheers
flash ⚡