Every time I try to use npm install command in the vsc terminal I get hit with this error:
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
[..................] | idealTree:inflate:node_modules/acorn-jsx: sill inflate node_modules/acorn-jsx
And it just goes on forever, I think it's a loop cause afterwards I just get fetch errors.
I just had the exact same issue today and it turned out to be a connection issue. Had to disconnect from VPN!
Related
This is a commonly asked question, but a little different this time. It seems the developers of Node.js have chosen to make NPM register the standard v2 package-lock.json in the project root (or wherever you run your commands from), and subsequently it registers the new v3 .package-lock.json file inside ./node_modules.
Is there a consensus as to whether we should be committing ./node_modules/.package-lock.json with our source code, or should it be considered just another build artifact of NPM? The reason for my question is recently our CI/CD pipeline has been automatically updating dependencies which were locked, and the only commonality seems to be the warning:
+ npm ci
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
I wanted to install lodash, and official website suggested running
npm i -g npm
Which I guess updated npm version. After that I ran
npm i --save lodash
And it outputed this:
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
Which I guess changed my package-lock.json file in the project. After that some dependencies issues started and when I tried to run my Angular project it stopped compiling it with an error of:
sh: 1: ng: not found
sh: 1: gulp: Permission denied
Process finished with exit code 127
Before Gulp started to warn about permission it was only ng: not found which I fixed with "npm link #angular/cli" command. At this point I think I did something completely wrong because I already tried to install newer npm version and it didn't resolve the issue. Anyone have an idea what went wrong here?
hi i'm trying to run hashlips for making nft collections
but at the start for running node.js
it shows me this error
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
added 65 packages, and audited 66 packages in 27s
6 packages are looking for funding
run npm fund for details
6 vulnerabilities (3 moderate, 3 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run npm audit for details.
I am trying to do 'npm install' inside one of my folders but i am getting error code E403 Forbidden :
npm WARN deprecated node-uuid#1.4.8: Use uuid module instead
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher
to avoid a RegExp DoS issue
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher
to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs#1.2.3: graceful-fs v3.0.0 and before will fail
on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as
possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0
(node_modules\chokidar\node_modules\fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: 403 Forbidden:
https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz
npm ERR! code E403
npm ERR! 403 Forbidden: binary-extensions#^1.0.0
My npm version is 5.5.1
My node version is v8.9.1
Also my system was formatted today and I had to re-install and re-setup everything from scratch. npm install was working till yesterday before my system was formatted.
I have attached the log file here.
https://github.com/angular/angular-cli/files/1499291/2017-11-23T13_25_27_656Z-debug.log
Thanks in advance
EDIT: every npm install is failing.
for reference here are the entries in my .npmrc file:
registry=http://registry.npmjs.org/
proxy=http://user_name:password#proxy:port
https-proxy=http://user_name:password#proxy:port
strict-ssl=false
I have tried many commands to get this working but no luck.
Note: my password contains '#' symbol but i have encoded it in my .npmrc file as %40
Ok, so i got around this particular problem. Seems like i had to update http to https in registry, and E403 was gone. But still i was facing other issues so decided to downgrade npm to 3.10.10 and node to 6.10.3.
From the first line it's saying old node-uuid module is deprecated and won't be maintained moving forward. Try reinstalling using these commands.
npm uninstall --save node-uuid
npm install --save uuid
In the second line it's asking for installation of minimatch
So try running the command :
npm install -g minimatch#3.0.4
When I try to remove a package, I got this hint:
npm WARN saveError ENOENT: no such file or directory, open 'D:\Program Files\nodejs\package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open 'D:\Program Files\nodejs\package.json'
npm WARN nodejs No description
npm WARN nodejs No repository field.
npm WARN nodejs No README data
npm WARN nodejs No license field.
added 27 packages, removed 231 packages, updated 5 packages and moved 11 packages in 104.617s
I'm not familiar with node.js. What's the meaning of these hints? And how can I (and why should I) commit the package-lock.json file?