although I am good in react but when I was tiring to install react version 1.2.5, I was getting this error again and again for running
npm i -g create-react-app#1.2.5
Output
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global`
instead.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for create-react-app#1.2.5.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\sibri\AppData\Local\npm-cache\_logs\2022-06-14T07_21_55_731Z-
debug-0.log
Anyone got any idea where I went wrong
As I can see in the returned error you should use --location=global instead of -g flag.
I am facing this error, after pull when I am trying to do npm install command.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for yargs#^17.2.1.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'pl201260-pi-wm-experience-platform'
npm ERR! notarget
My package.json version like this:
"name": "adviser",
"version": "0.0.0",
"license": "MIT",
I have tried commands npm cache clean --force
and tried deleting package-lock.json file.
Kindly let me know what this 0.0.0 version means and why how this problem can be tackled.
My app uses sass, not node-sass. node-sass is nowhere in my package-lock.json.
I'm currently using npm 6 and everything is working fine and has been for years.
When I try to npm install with npm 7, it fails with the below error.
What's going on? Maybe node-sass is a dev dependency of something else and being built?
npm ERR! npm ERR! code 1
npm ERR! npm ERR! path /Users/john/.npm/_cacache/tmp/git-clonenbaf30/node_modules/node-sass
npm ERR! npm ERR! command failed
npm ERR! npm ERR! command sh -c node scripts/build.js
npm ERR! npm ERR! Building: /opt/local/bin/node /Users/john/.npm/_cacache/tmp/git-clonenbaf30/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm ERR! npm ERR! c++ '-DNODE_GYP_MODULE_NAME=libsass' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_DARWIN_USE_64_BIT_INODE=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DLIBSASS_VERSION="3.3.6"' -I/Users/john/.node-gyp/14.18.3/include/node -I/Users/john/.node-gyp/14.18.3/src -I/Users/john/.node-gyp/14.18.3/deps/uv/include -I/Users/john/.node-gyp/14.18.3/deps/v8/include -I../src/libsass/include -O3 -gdwarf-2 -mmacosx-version-min=10.7 -arch arm64 -Wall -Wendif-labels -W -Wno-unused-parameter -std=c++11 -stdlib=libc++ -fno-strict-aliasing -MMD -MF ./Release/.deps/Release/obj.target/libsass/src/libsass/src/eval.o.d.raw -c -o Release/obj.target/libsass/src/libsass/src/eval.o ../src/libsass/src/eval.cpp
### above line repeated many times
npm ERR! npm ERR!
You might be using a version of Node or npm that are not compatible with the version of node-sass that is being pulled. node-sass publishes this table that shows the range of supported versions for any toolchain version. If one of your dependencies is pulling node-sass, you could force your desired version by explicitly specifying node-sass as a direct dependency. You could also consider upgrading Node or npm as an alternative.
To see what would happen I tried npm install --package-lock-only, and it succeeded. I could then see the dependency tree. node_modules/sass-loader has node-sass as a peer dependency.
npm7 installs peer dependencies by default and doesn't allow getting into an ambiguous state. (more info: https://stackoverflow.com/a/22004559/168143 )
So, that's why this was happening. I don't know if I wasn't reading the stack trace well enough or if there is some other standard way for me to have figured out what had the dependencies. I'll leave this question without an accepted answer just in case someone has a smarter way to diagnose this sort of thing.
I get an error while installing react-list-filter use npm (npm install react-list-filter), this is error messages in my console :
npm ERR! code ETARGET
npm ERR! notarget No matching version found for awesomplete#1.0.0
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'react-list-filter'
npm ERR! notarget
npm ERR! A complete log of this run can be found in:
npm ERR! /home/andrew/.npm/_logs/2017-09-26T08_01_47_125Z-debug.log
I try to install awesomplete, but still, error when I install react-list-filter, please anyone help me to solve this error.
Looks like it was their bug, and it was listed on an issue a year ago
https://github.com/rauljordan/react-list-filter/issues/1
It's not likely to be fixed, you probably need to fork their repository and change their dependency on awesomplate version
I have an angular project (really just the docs tutorial) and I want to include the node-mysql module in my project- doesn't have to be installed globally.
Not sure I understand how this works but I thought all I have to do was add this module to package.json as a dependency and run npm install, but I get an error:
PS> cat .\package.json
{
"version": "0.0.0",
"private": true,
"name": "angular-phonecat",
...
"dependencies": {
"node-mysql": ">=2.5.0"
},
"devDependencies": {
"karma": "^0.12.16",
...
The error:
PS> npm install
npm WARN package.json karma-chrome-launcher#0.1.7 No README data
npm ERR! notarget No compatible version found: node-mysql#'>=2.5.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.1.1","0.1.2","0.1.3","0.1.4","0.1.5","0.1.6","0.1.7","0.1.8","0.1.9","0.2.0","0.2.1","0.2.2","0.2.3","0.2.4","0.2.5","0.2.6","0.2.7","0.2.8","0.2.9","0.3.0","0.3.1","0.3.2","0.3.3","0.3.4","0.3.5","0.3.6","0.3.7","0.3.8","0.3.9","0.4.0","0.4.1"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! cwd C:\testangular\ticketsys\angular-phonecat
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! code ETARGET
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\testangular\ticketsys\angular-phonecat\npm-debug.log
npm ERR! not ok code 0
How can I include this dependency in my project?
Node-mysql version >2.5 is not out yet. Node-mysql is on version 0.4.1. I suspect you are looking for just the regular mysql npm module. Mysql on npm is on version 2.5.4.
Try using this instead:
"mysql": ">=2.5.0"
If you go to this page: https://github.com/felixge/node-mysql . They say in the install instructions to use npm install mysql. This might be a bit confusing since their github page is node-mysql.
Alternatively instead of adding this manually to the dependency you could go ahead and do the following:
npm install mysql --save
This will only install the most up to date one locally (Not globally, if you wanted to install it globally you could add the -g flag, but since you don't need that dont!).
As mentioned in other answers, npm is not recognizing the version you have specified. I would recommend removing that line from your package.json and instead running a single command:
npm install --save mysql
This will install the dependency locally AND add the line to your package.json(that's what the --save flag does). This automatically defaults to the most recent stable version of node-mysql.
In general, the only time you'll want to specify an actual version in your package.json is if a library patched over some features you actually wanted, in which case you could specify a version so that the necessary features are always there. So definitely start using the --save flag when you can. It's super useful. Best of luck!