npmrc | Switch between different .npmrc files with ease and grace | Frontend Framework library

I'm not sure how exactly did you invoked the command-line, but I just used like this in my terminal with success:

Having the same problem. This is my speculation, but I suspect that this is a problem on NPM registry's server side. 'package.json' is clearly being compressed, as can be seen in the 'Tarball Contents' section. The npm cli made a request to the NPM server (registry.npmjs.org), but for some reason, the code on the npm registry is rejecting the tarball and either diagnosing a problem where there is none or telling us that there's a problem but misdiagnosing. But to be extra sure, maybe try 'npm pack' first, then use 'tar -tzvf json-to-plain-text-1.0.3.tgz' to check the tarball contents, and then 'npm publish json-to-plain-text-1.0.3.tgz'?

Nvm. I know the answer now. Turns out that nodejs 12 is kind of outdated. Try using nodejs v17 using this method. I personally think the Debian repos are at fault for being so behind.

After the rest of the day searching for the answer it was the most simple but not the wisest solution that worked:

Completely ignored the .npmrc file and in package.json under dependencies just added the personal access token like so: @github.com

Problem:

The python is installed locally on your macbook but not inside the docker container (which is an isolated virtual os).

Solution

You need to install python in the same container where you are running the nodejs script or npm command.

Try Adding this after pulling your nodejs image in dockerFile

I finally find out !!! BUT I'm not sure in term of security if there is any risk or not so if anyone can advice I'll edit the answer !

What is changing but I'm not sure in term of security is here :

Meanwhile, posting the solution proposed by sethvargo and guillaume blaquiere for visibility.

You can set the token value as an environment variable, NPM_TOKEN. In that case, you can use the native Cloud Build + Secret Manager integration to inject the value: cloud.google.com/build/docs/securing-builds/use-secrets

If the NPM_TOKEN solution doesn't work, you can still use the Secret Manager and Cloud Build to load your token, write your .npmrc file with a script and then run your build.

Microsoft updated their VMs around the 3rd December.
In this change the default node version has changed from 14.x to 16.x.

We found this exact issue when running on node 16.

This won't be a Long term fix - As you'll need to work out why your build doesn't work on Node 16, but in the short term you can add a command which tells the build agent to use version 14 of node.

Presuming you are using the modern YAML build pipelines, try adding the following as the first step in your YAML pipeline:

The problem seems to be that of an inappropriate installation. The go to way to fix this would be to ensure a proper uninstall of node and npm. Please follow the steps mentioned here. Once properly uninstalled, head over to install node and proceed with the re-installation.

Some of the dependencies of your app (or of angular's) are not fully upgraded to work with npm 8.x ( more specifically with the new version of package.json structure)

try