Roch Devost

@icebob You mentioned several operations that are traced above. If you can link me to the code of one of them and also to how it's currently traced I can...

We're getting a lot of reports of this since removing the `binding.gyp` file from our project: https://github.com/DataDog/dd-trace-js/issues/2239 https://github.com/DataDog/dd-native-metrics-js/issues/28 The file doesn't exist anymore, so it's unclear why `npm` keeps trying...

> Seems that all of these reports share at least one thing in common: a private registry. This was also my assumption at first, but according to https://github.com/DataDog/dd-native-metrics-js/issues/27#issuecomment-1199061606 it seems...

I was able to reproduce with the following steps: ```js nvm install 18.7.0 docker run -d -p 127.0.0.1:4873:4873/tcp verdaccio/verdaccio export NPM_CONFIG_REGISTRY=http://localhost:4873 npm init -y npm install --save @datadog/[email protected] npm install...

The issue occurs with `npm` >=7.0.0 but not with 6.14.17

Using `npm install --ignore-scripts --save @datadog/[email protected]` works, even though there are no scripts in the latest version of the package (but there used to be an install script before).

@mkaufmaner I don't think so because in my local tests, once the issue started happening, I was unable to install any version of dd-trace anymore, even older versions that do...

> The problem is I can't implement this workaround for the thousands of CICD pipelines we have. It is simply impractical. @mkaufmaner How do you generally handle updates in these...

@mkaufmaner I tried to switch version of Node with nvm to test your theory since that uses a different npm instance with its own installation folder including its cache. Even...

@mkaufmaner Would environment variables work for your use case instead? The same workaround can be applied with `NPM_CONFIG_IGNORE_SCRIPTS=true`. I'm trying to not have to revert this change since it _will_...