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.
Related
I uninstall nodejs because i thought that will fix my problem but no. I only want to create a vue.js app in an empty folder but i have these errors lines when I enter npm install -g #vue/cli. It tells me there are 4 vulnerabilites and npm audit fix --force doesn't work
Error lines from npm install -g #vue/cli
`
npm WARN deprecated source-map-url#0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated source-map-resolve#0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated subscriptions-transport-ws#0.11.0: The `subscriptions-transport-ws` package is no longer maintained. We recommend you use `graphql-ws` instead. For help migrating Apollo software to `graphql-ws`, see https://www.apollographql.com/docs/apollo-server/data/subscriptions/#switching-from-subscriptions-transport-ws For general help using `graphql-ws`, see https://github.com/enisdenjo/graphql-ws/blob/master/README.md
changed 847 packages, and audited 848 packages in 26s
64 packages are looking for funding
run `npm fund` for details
4 vulnerabilities (2 moderate, 2 high)
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
`
Error lines from npm audit fix --force
`npm WARN using --force Recommended protections disabled.
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
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\freir\AppData\Local\npm-cache_logs\2022-11-08T13_17_58_614Z-debug-0.log`
When I enter node -v it tells me the right version of node and same thing for npm -v
i really need help please
Here are some of my previous answers on the subject: https://stackoverflow.com/search?q=user%3A8816585+vulnerabilities
TLDR: it's totally fine, you can move along. JavaScript is moving fast and there are probably millions of vulnerabilities but none of those will ever (or very unlikely at least) break anything into your app.
If there is something really critical, it will be fixed for you don't worry.
I keep getting this npm warning after running npm install. I have deleted and reinstalled npm. Nothing seems to work.
npm WARN deprecated fsevents#1.2.4: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
up to date, audited 2107 packages in 26s
94 packages are looking for funding
run `npm fund` for details
68 vulnerabilities (14 low, 18 moderate, 32 high, 4 critical)
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.
first try to reset npm cache
npm cache clean --force
then retry to install npm packages
if nothing happens, try npm install --no-optional or npm install --force
hope that works
The problem isn't with npm, but with your project. It requires (possibly indirectly), fsevents#1.2.4, which is deprecated. You'll need to update your project to require a newer version, e.g.:
"fsevent": "^2.3.2"
and of course, update your project to work with this version.
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!
I was trying to download EJS and i got this error:
npm WARN deprecated transformers#2.1.0: Deprecated, use jstransformer
npm WARN deprecated constantinople#3.0.2: Please update to at least constantinople 3.1.1
npm WARN deprecated jade#1.11.0: Jade has been renamed to pug, please install the latest version of pug instead of jade
added 115 packages, and audited 116 packages in 5s
2 packages are looking for funding
run `npm fund` for details
5 vulnerabilities (1 low, 4 critical)
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details
someone can help me?
$ npm install node-sass --save-dev
npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EAI_AGAIN: request to https://registry.npmjs.org/node-sass failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org
npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
node-sass#4.14.0 install F:\waptask\jquery\1st practice\node_modules\node-sass
node scripts/install.js
Cached binary found at C:\Users\user\AppData\Roaming\npm-cache\node-sass\4.14.0\win32-x64-72_binding.node
node-sass#4.14.0 postinstall F:\waptask\jquery\1st practice\node_modules\node-sass
node scripts/build.js
Binary found at F:\waptask\jquery\1st practice\node_modules\node-sass\vendor\win32-x64-72\binding.node
Testing binary
Binary is fine
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN 1st-practice#1.0.0 No repository field.
node-sass#4.14.0
added 172 packages from 137 contributors and audited 528 packages in 96.598s
3 packages are looking for funding
run npm fund for details
found 1 low severity vulnerability
run npm audit fix to fix them, or npm audit for details