[bug/dependency] npm install Fails Due to Registry Mismatch

[karanngi]

Occasionally, running npm install fails because of conflicting registry configurations—some packages attempt to fetch from different registries (e.g., the default https://registry.npmjs.org/ vs. a private one). This mismatch can stem from scoped registry settings in .npmrc, hardcoded URLs in package-lock.json. The issue can often be resolved by aligning registry settings, cleaning lock files.

we should use a single registry to solve this
"https://registry.npmjs.org/"

cc @luc99hen @zyjhtangtang @rambohe-ch

[arnavkirti]

Hi, can I work on this issue?
It seems we can resolve this by making a .npmrc file that sets the registry:

registry=https://registry.npmjs.org/

So, all the npm dependencies will only be installed from this registry.

[Spiral-Memory]

No @arnavkirti,
.npmrc won't solve this problem because it's the package-lock.json that has already resolved the dependencies using the mirror registries.

I've raised a PR with the fix, have a look. Manually editing the package.json was the only thing that fixed the issue.

[karanngi]

completed #57