1) Referencing package version in npm-scripts. In npm-script‘s you can reference the version using the variable npm_package_version. For example: Using a bash shell (E.g. Linux, macOS): { … “version”: “1.0.0”, “scripts”: { “build”: “echo $npm_package_version” } } Note the $ prefix Using Windows (E.g. cmd.exe, Powershell): { … “version”: “1.0.0”, “scripts”: { “build”: “echo %npm_package_version%” … Read more
I was able to fix this by running the command prompt/bash as admin and closing VSCode! Seems like VSCode was locking some files. Potentially something else could be locking these files for you.
npm test, npm start, npm restart, and npm stop are all aliases for npm run xxx. For all other scripts you define, you need to use the npm run xxx syntax. See the docs at https://docs.npmjs.com/cli/run-script for more information.
Until this is fixed for now you can delete the node_modules folder and package-lock.json. Next, open package.json and change “react”: “^18.0.0” & “react-dom”: “^18.0.0” to an earlier version e.g: “react”: “^17.0.2” & “react-dom”: “^17.0.2”. Finally, you can run npm install. Alternative Solution (Try this first!): solution suggested by joooni1998): delete both node_modules and package-lock.json run … Read more
This does not seem to be supported by npm natively, however this package aims to add this functionality: https://github.com/rogeriochaves/npm-force-resolutions
If you are behind a proxy, set it correctly in npm. >npm config set proxy http://proxyhost:proxyport >npm config set https-proxy http://proxyhost:proxyport Notes: For SSL/https proxies, the protocol in URL should be http not https If your set up is on a Docker/Vagrant instance or a hosted VM, use IP address instead of hostname for proxy … Read more
It looks like you hit a bug that has existed for quite a while and doesn’t have solution yet. There are several open issues for this case in the npm repository: npm install should recursively check/install dependencies https://github.com/npm/npm/issues/1341 (closed) local private module dependencies https://github.com/npm/npm/issues/2442 (closed) In the first one people list several workarounds that you … Read more
Do you need both package-lock.json and package.json? No. Do you need the package.json? Yes. Can you have a project with only the package-lock.json? No. The package.json is used for more than dependencies – like defining project properties, description, author & license information, scripts, etc. The package-lock.json is solely used to lock dependencies to a specific … Read more
Restore ownership of the user’s npm related folders, to the current user, like this: sudo chown -R $USER:$GROUP ~/.npm sudo chown -R $USER:$GROUP ~/.config
One of the create-react-app maintainers has announced that they cannot fix this as the vulnerabilities affect transitive dependencies, and that it should not matter. The reasoning is that the npm audit feature was built with Node apps in mind, not build tools. Vulnerabilities in the dependencies should (in most cases) not translate to vulnerabilities in … Read more