We Keep Coding

Getting error while installing live-server package using npm. `npm audit` is not helping to fix the problem

I am new to javascript. I am trying to learn javascript by following instructions here. I am trying to install live-server package using npm but I am seeing the following error.
$ npm install -g live-server
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 opn#6.0.0: The package has been renamed to `open`
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve#0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
changed 208 packages, and audited 209 packages in 7s
2 high severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
sshil-414HTD6:IssueTracker sshil$ npm audit fix --force
npm WARN using --force Recommended protections disabled.
up to date, audited 1 package in 192ms
found 0 vulnerabilities
$ npm i live-server
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 opn#6.0.0: The package has been renamed to `open`
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve#0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
added 208 packages, and audited 209 packages in 6s
3 high severity vulnerabilities
To address all issues, run:
npm audit fix
Run `npm audit` for details.
$ npm version
{
issuetracker: '1.0.0',
npm: '8.19.2',
node: '19.0.0',
v8: '10.7.193.13-node.16',
uv: '1.43.0',
zlib: '1.2.11',
brotli: '1.0.9',
ares: '1.18.1',
modules: '111',
nghttp2: '1.47.0',
napi: '8',
llhttp: '8.1.0',
openssl: '3.0.5+quic',
cldr: '41.0',
icu: '71.1',
tz: '2022b',
unicode: '14.0',
ngtcp2: '0.8.1',
nghttp3: '0.7.0'
}

You shouldn't bother too much about it. It's more an warning than error. And there is not much you can do. To check if the package is installed, go in package.json file, it should be in dependencies object.
Nowadays if you use vscode you don't need to install live-server as it is already built in.
You can read more about npm audit here npm audit: Broken by Design

npm ERR! Windows_NT 10.0.19044 while installing library using npm

I am working on a project in our organization. while i am trying to run or install libraries it's getting an error.
E:\GIT\bookshelf>npm install
npm WARN deprecated bcrypt-nodejs#0.0.3: bcrypt-nodejs is no longer actively maintained. Please use bcrypt or bcryptjs
npm WARN deprecated #angular/http#4.1.3: Package no longer supported. Use #angular/common instead
npm WARN deprecated formidable#1.1.1: Please upgrade to latest, formidable#v2 or formidable#v3!
npm WARN deprecated core-js#2.4.1: core-js#<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated angular-tree-component#3.2.3: Library moved to #circlon/angular-tree-component
npm WARN deprecated multer#1.2.0: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated angular2-infinite-scroll#0.3.4: Please use the new --> ngx-infinite-scroll <--- supports in Angular +4, AOT compilation and optimized code bundle
npm WARN deprecated log4js#2.3.12: 2.x is no longer supported. Please upgrade to 6.x or higher.
npm WARN deprecated ckeditor#4.5.9: We have renamed the #ckeditor package. New versions are available under the #ckeditor4 name.
npm WARN deprecated angular2-recaptcha#0.6.0: Package no longer supported.
npm WARN deprecated fingerprintjs2#1.5.1: Package has been renamed to #fingerprintjs/fingerprintjs. Install #fingerprintjs/fingerprintjs to get updates.
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated request#2.83.0: request has been deprecated
npm ERR! Windows_NT 10.0.19044
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v6.17.1
npm ERR! npm v3.10.10
npm ERR! Cannot convert undefined or null to object
npm ERR!
npm ERR! If you need help, you may report this error at:
npm WARN deprecated ng2-bootstrap#1.4.0: ng2-bootstrap is renamed to ngx-bootstrap, please do npm i ngx-bootstrap -S
npm WARN deprecated request-promise#4.2.2: request-promise has been deprecated because it extends the now deprecated request package,
npm ERR! Please include the following file with any support request:
npm ERR! E:\GIT\bookshelf\npm-debug.log
I am using node version: 6.17.1 ( setup via NVM )
npm version: 3.10.10
windows machine.
Anyone helps me to find out what am I missing?

first remove package-json.lock file then try this npm command:
npm install --no-audit
run the command on your terminal.
or you can read this How can I fix this npm error? npm ERR! Windows_NT 10.0.19042, similar problem.

I am trying to clone project from bitbucket and running in VS Code while doing npm install showing a lot of errors, warning

I have project on bitbucket and trying to clone it, the project is very older 3 year old so might be some packages do get old. But while I am doing npm install so it is showing a lot of warning and errors. Also the project at beginning made with Yarn not NPM.
Some warning and error looks like:
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 deprecated ini#1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated flatten#1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated #hapi/bourne#1.3.2: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator#5.1.3: this library is no longer supported
npm WARN deprecated chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fe
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-url#0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated left-pad#1.3.0: use String.prototype.padStart()
npm WARN deprecated debug#4.1.1: Debug versions >=3.2.0 <3.2.7[1] || >=4 <4.3.1 have a low-severity ReDos regression when used incommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)

Remove your package-lock.json and then execute npm install (or yarn install if you prefer).
Have in mind that being this an old project. Some of the packages passed for major changes and may possibly not run as expected anymore. Major changes are not necessarily backward compatible, so you may have to change a lot of code in order to make your code work. Be ready to have a lot of fun coding!
EDIT: Considering the package.json you posted in a comment, my suggestion is creating a new app using npx create-react-app and then moving your ReactJS code to it. This way you would have a completely updated app and would have only to review your code.

Node.js not compatible with react-create-app

I have node.js 14.6.0 and node-v 7.20.0
Steps to reproduce:
npx create-react-app my-app2
once all is installed run npm i
Now you should get the following:
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 deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated sane#4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated mkdirp#0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated uuid#3.3.3: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated mkdirp#0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
After this the terminal suggest npm audit fix
and when running that I get a list of errors the first one being:
npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: babel-loader#8.1.0 npm WARN Found: webpack#4.44.2 npm WARN node_modules/webpack npm WARN peer webpack#">=4.43.0 <6.0.0" from #pmmmwh/react-refresh-webpack-plugin#0.4.3 npm WARN node_modules/#pmmmwh/react-refresh-webpack-plugin npm WARN #pmmmwh/react-refresh-webpack-plugin#"0.4.3" from react-scripts#4.0.3 npm WARN node_modules/react-scripts npm WARN 17 more (css-loader, eslint-webpack-plugin, file-loader, ...)
Is there a compatibility issue? what versions should I be using?

For those facing the same problem just :
npm install -g npm#6.14.12

Try deleting the package.lock.js file and for then run npm i

npm is known not to run on Node.js v9.2.1

why i use npm to install something, it will have this problem as below
ERROR: npm is known not to run on Node.js v9.2.1
Node.js 9 is supported but the specific version you're running has
a bug known to break npm. Please update to at least 9.0.0 to use this
version of npm. You can find the latest release of Node.js at https://nodejs.org/
Then i find some solutions at stackoverflow.
npm WARN npm npm does not support Node.js v9.1.0
npm does not support Node.js v9.0.0
Almost every answer suggest to use "npm uninstall -g npm" first.But when i use this command,it will have the same error as above.
My npm version is 6.13.7
My node version is 9.2.

Basically node js 9.2... version is compatible with npm version 5.5.1.
So I will provide you the following suggestion.
1- if you want to work with node js 9.2 only then
i)- uninstall node js 9.2
ii)- uninstall npm
iii)- install node js 9.2
iv)- then install npm version 5.5.1
npm install -g npm#5.5.1
2- update node js and npm to the latest version and check your code compatibility with the new version.
To do this
1- install node js latest version
2-npm install -g npm#latest