Lorenzo Polidori

I solved this issue switching to webpack and calling it in a custom gradle task: ```groovy task webpackBuild(type: Exec) { workingDir 'base/path' commandLine 'npm', 'run', 'build' } ```

+1 Is this project still maintained?

I solved this issue switching to webpack and calling it in a custom gradle task: ```groovy task webpackBuild(type: Exec) { workingDir 'base/path' commandLine 'npm', 'run', 'build' } ```

@jeancx shall we fork this and publish independently?

@DanBurton, @vinmazzi, any updates on this issue? Without a fix, we need to manually replace `ssh://git@` with `https://` in `package-lock.json` to make it work on CI every time we upgrade...

@vinmazzi @DanBurton My CI runs on a `amazonlinux:2` docker container with these node versions: node: `v14.19.0` npm: `6.14.16` However, my `package-lock.json` is created on my MacBook development machine, running node:...

> This is an open issue on npm v7, but it appears that they do not intend to address it. [npm/cli#2610](https://github.com/npm/cli/issues/2610) > > We will look into ways that we...

@vinmazzi Thanks for your reply. I have upgraded to node `v14.19.1` and npm `8.11.0`. However, when I run `npm install` to recreate my `package-lock.json` from scratch, I still get the...

@vinmazzi I can confirm this is still an issue and it is affecting also other developers working with me and running the lasted versions of node 14 and npm.

@4miners I am experience exactly the same issue. What is the timeline for [this PR](https://github.com/node-fetch/node-fetch/pull/1719) to be merged and this fix being released?