how to fix npm audit error with loadVirtual and ENOLOCK? - javascript

➜ npm audit
npm ERR! code ENOLOCK
npm ERR! audit This command requires an existing lockfile.
npm ERR! audit Try creating one first with: npm i --package-lock-only
npm ERR! audit Original error: loadVirtual requires existing shrinkwrap file
I ran npm audit and got this error.
When I run below:
➜ npm config get package-lock
true
➜ npm config get shrinkwrap
true
Can anybody help with this? as to how to fix it? and npm audit fix --force is not working as well...

I just ran the command it says to.
npm i --package-lock-only
Then it showed me 0 vulnerabilities.
Anyway, ran again audit fix and again 0 vulnerabilities.

works for me like this:
npm cache clean --force
npm fund
npm audit fix --force

The problem is that you need a package.json and package-lock.json file in the directory.
Running the following commands will fix it for you.
npm init -y
npm i --package-lock-only
npm audit
This fixes the problem

That error tells you the root of the problem: This command requires an existing lockfile.. This implies that you don't already have a package-lock.json along side the package.json you're trying to audit. npm i --package-lock-only just generates/updates package-lock.json without reinstalling; npm i would reinstall and generate one (based on your config).

You need to create package-lock.json, run
npm install
then
npm audit fix
you won't have the problem

I updated to the latest version of npm with npm install -g npm#8.3.0, and now it shows no more problems...

Try running these:
npm i --package-lock-only
npm config get package-lock
npm config get shrinkwrap
npm i --package-lock-only
npm audit fix
From here.

Use Node 14, it fixed the issue with 0 vulnerabilities.

I read this and really helpful:
https://medium.com/illumination/how-to-fix-npm-audit-error-with-loadvirtual-and-enolock-deprecated-dependencies-1f07ba65eef9
npm i --package-lock-only
npm config get package-lock
npm config get shrinkwrap
npm i --package-lock-only
npm audit fix
(When running ‘npm config get package-lock’ and ‘npm config get shrinkwrap’, you will receive ‘true’ for both)
— → After running ‘npm audit fix’, you will see: “up to date, audited… found 0 vulnerabilities”

Had the same error, then realized I was in a parent folder. So this may happen if there's no lock file.

Try running this command:
npm cache clean --force

Related

npm ERR! Cannot read property 'version' of null

I can't install anything in it, tried solutions in here but did not work any either.
$ npm install axios
npm ERR! Cannot read property '**version**' of null
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\\AppData\Local\npm-cache\_logs\2021-08-26T13_54_26_790Z-debug.log
Try to cleanup node cache and remove node_modules:
$ npm cache clean --force
$ rm -rf node_modules
After try to run npm install axios.
this error generally came when you used any deprecated library on your project. so just go through your package.json file and remove those deprecated library which you have been used...
simply remove that versions from package.json and do
npm i --legacy-peer-deps
if it will not resolved then try run this
npm install axios --legacy-peer-deps
can you please check your
npmlockversion in the package-lock.json ,
and you npm version?
if you are using npmlockversion 3 you should use npm version higher than 7.

ENOLOCK npm ERR! Error while running npm audit fix

I am trying to install GLOBALLY a package with npm from my home directory. After the install has completed, it indicates vulnerabilities. Upon trying to run npm audit fix, I obtain the following error.
npm ERR! code ENOLOCK npm ERR! audit This command requires an existing
lockfile. npm ERR! audit Try creating one first with: npm i
--package-lock-only npm ERR! audit Original error: loadVirtual requires existing shrinkwrap file
I understand that the error asks me to run npm i --package-lock-only, but in which directory should I be creating this file? Running the command without specifying a path does not work. I have also tried to create the file in the directory where the package was installed, but that has also not solved the issue. Also, why isn't this file present to start with?
npm audit fix is intended to fix vulnerabilities with the dependencies of your own project. Projects do have a package-lock.json file.
It is not intended for globally installed packages. If there are vulnerabilities with packages from others, they need to be fixed by the package maintainer in a new release. You can then update to this new release.
BTW, you should not use globally installed packages. Use npx instead.

vue cli not installing , tried using yarn and npm none is working?

i have been trying to install vue cli
am getting this error :
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm ERR! Unexpected end of JSON input while parsing near '...b\n/0ygjrhbcRx2VetexZ'
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\ekikere\AppData\Roaming\npm-cache_logs\2020-07-28T23_29_37_356Z-debug.log
This is a problem related to npm. You can get this error when the cache file gets corrupted. Clearing the cache solves the problem. Can you try this?
npm cache clean --force
you can clear cache by running these command :
npm cache clean --force
linux system:
run command as root
sudo npm install -g #vue/cli
windows system
open command prompt as adminstrator then run :
npm install -g #vue/cli

npm Error! ENOENT: no such file or directory .dezalgo.DELETE'

Whenever I try to do anything with my NPM I keep on getting this error.
I try to install npm install -g --save vue-draggable
I have uninstalled node and npm and re installed and constantly having this issue.
npm ERR! path /Users/victor/Desktop/myprog/node_modules/jquery/node_modules/npm/node_modules/dezalgo
NPM Verson: 5.6.0
Node: v8.9.1
To anyone having this problem, its because NPM is version 5.6.0
Downgrade to:
Sudo npm install -g npm#4.6.1
I don't think that the accepted solution will solve the issue...
Somehow a dependancy representation in package-lock.json is wrongly described.
Removing the file package-lock.json and npm install could solve the issue.
I recommend that you use the latest version of npm : npm install npm#lastest.

NPM not working (Cannot find module 'internal/fs' - nodejs)

NPM error on update. I recently update to Node version 7.x. Now npm is not working.
I am unable to locate the error, it may be due to -
npm ERR! Cannot find module 'internal/fs'.
I get the following when I run sudo npm update -g -
npm ERR! Linux 3.13.0-101-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "update" "-g"
npm ERR! node v7.1.0
npm ERR! npm v3.10.8
npm ERR! code MODULE_NOT_FOUND
npm ERR! Cannot find module 'internal/fs'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
My /etc/profile.d/nodejs.sh has the following contents:
NODE_PATH=/usr/lib/nodejs:/usr/lib/node_modules:/usr/share/javascript
export NODE_PATH
You should be able to remove the npm directory (typically /usr/local/lib/node_modules/npm) and then reinstall one of the official node tarballs, which includes npm (you can find the latest from http://nodejs.org/dist/latest-v7.x/).
Did you upgrade from an older version of node?
If so, that is probably part of the reason why you are having this issue. Older versions of graceful-fs (a dependency of npm) did things that are no longer available in node v7.
According to this thread, updating npm to version 4 will solve your problem, try:
npm i -g npm#4
If this doesn't work, try:
~/.n/n/versions/node/7.0.0/bin/npm i -g npm#4
delete node_modules directory and then type in your console "npm install". For a reason that I dont know, if you only update npm, it does not fix the error, but re-installing npm everything is gonna be allright.
For me, if I facing error "cannot find module internal/fs", it would be refer to command path. Better find the command path:
npm config get prefix
put into system environment path.
It is worked for me after facing the error several days.

Categories