I have this issue when trying to install Ionic.
mypc#mypc-HP-ProBook-470-G2:~$ sudo npm install -g ionic
npm http GET https://registry.npmjs.org/ionic
npm http 200 https://registry.npmjs.org/ionic
npm http GET https://registry.npmjs.org/ionic/-/ionic-1.7.14.tgz
npm http 200 https://registry.npmjs.org/ionic/-/ionic-1.7.14.tgz
/usr/local/bin/ionic -> /usr/local/lib/node_modules/ionic/bin/ionic
npm WARN unmet dependency /usr/local/lib/node_modules/ionic/node_modules/connect/node_modules/finalhandler requires debug#'1.0.4' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/local/lib/node_modules/ionic/node_modules/request/node_modules/form-data requires combined-stream#'~0.0.4' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
ionic#1.7.14 /usr/local/lib/node_modules/ionic
Can someone help me to solve it, please ?
Thanks.
To answer your question, it;s the npm and nodejs version which is wrong.
(At least it was in my case)
I believe this has to do with the later added feature of scoped packages.
Update to a later version of node, I am not sure, if you are on ubuntu specifically or not, but for this purpose I was using ubuntu 14.x.
Remove all nodejs installs you might currently have :
sudo apt-get remove --purge nodejs
then you want to install node through the NVM package
You can search for a version you want via :
nvm ls-remote
For the ionic install I updated to : v0.12.10
nvm install 0.12.10
After this installs (It's also going to install/update npm for you)
You should see your latest version :
node -v
Should display : v.0.12.10 in this case.
You may then continue to install the ionic framework as instructed .
npm install -g ionic
Note: NVM also allows you to have concurrent installs of different node versions. Very handy for some legacy apps // services.
Related
While attempting to learn Gatsby, I have run into some depreciated package errors as follows when installing the gatsby-cli package:
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 #hapi/hoek#8.5.1: This version has been deprecated and is no longer supported or maintained
npm WARN express-graphql#0.9.0 requires a peer of graphql#^14.4.1 but none is installed. You must install peer dependencies yourself.
Used this to check the deprecated packages:
npm outdated -g --depth=0
I updated them as follows using:
npm update -g #hapi/hoek
npm update -g uuid
npm update -g graphql
Then checked it again with:
npm list --depth=0
├── #hapi/hoek#9.2.0
├── graphql#15.5.1
└── uuid#8.3.2
These are the latest versions:
https://www.npmjs.com/package/#hapi/hoek?activeTab=versions
https://www.npmjs.com/package/graphql?activeTab=versions
https://www.npmjs.com/package/uuid?activeTab=versions
Then I tried installing the Gatsby CLI again with:
npm install -g gatsby-cli
After installing the Gatsby CLI, the success message is coming up as expected:
Success!
Welcome to the Gatsby CLI! Please visit https://www.gatsbyjs.org/docs/gatsby-cli/ for more information.
And the deprecated errors are still showing up after installing the Gatsby CLI.
Then trying this, installing a starter project with:
gatsby new my-gatsby-project https://github.com/gatsbyjs/gatsby-starter-hello-world
And this happens.
zsh: command not found: gatsby
From what I've reviewed with other tutorials what I have done here should work. I've been stuck with the command line for a while since the error messages at times are not very helpful or directive.
Any help at all would be appreciated.
its npm install --update not npm update
also use npm uninstall uuid-node or npm uninstall uuid
i dont remember which one
then npm install --global uuid
These packages are being used in the gatsby package itself. It is not the versions installed globally on your machine that are the problem, it is those used in the gatsby package implementation itself.
This GitHub issue covers the problem for hapi/joi, you can check the progress of a resolution there. The others should also have open issues in the gatsbyjs/gatsby repo.
npm install -g grunt-cli //done successfully
npm install grunt --save --only=dev
gives following error
(node:11000) fs: re-evaluating native module sources is not supported. If
you are using the graceful
-fs module, please update it to a more recent version.
npm WARN prefer global coffee-script#1.10.0 should be installed with -g
project#1.0.0 C:\Users\Live\Desktop\node grunt\final
`-- (empty)
npm WARN project#1.0.0 No repository field.
npm ERR! code 1
Tried uninstalling grunt-cli, cleaning npm cache, then re-installing, but still the problem persists.
Ok short recap:
When in doubt remove your node_modules and install all packages again using npm install
If that didn't work, try updating your npm by executing npm update -g npm and redo step 1.
If that didn't solve your problem, try upgrading to another NodeJS version using nvm or n.
I'm tryin' to install angular-cli into my linux Mint 32bit computer. But There's a failure to install it.
My command into terminal is:
npm install -g angular-cli
And the output:
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
/home/shwokat/!/.npm-global-me/bin/ng -> /home/shwokat/!/.npm-global-me/lib/node_modules/angular-cli/bin/ng
/home/shwokat/!/.npm-global-me/lib
└─┬ angular-cli#1.0.0-beta.28.3
└── UNMET PEER DEPENDENCY rxjs#^5.0.1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0 (node_modules/angular-cli/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.0.17: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"ia32"})
npm WARN #angular/core#2.4.7 requires a peer of rxjs#^5.0.1 but none was installed.
Please write how to overcome this error & install angular-cli correctly ...
This is an issue with beta 30 of the CLI... the temporary fix is to install rxjs globally to resolve the dependency.
npm install rxjs -g
This has been addressed in the repo and will no longer be an issue with the next release.
UPDATE:
From #frankie4fingers in the comments, you may find success using the specific version:
npm install -g rxjs#5.0.1
I had the same issue, I was trying to install AngularJS 2 CLI using
npm install -g angular-cli
And I got the following warning and dependency error:
npm WARN deprecated angular-cli#1.0.0-beta.28.3: angular-cli has been renamed to #angular/cli. Please update your dependencies.
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules/angular-cli
/usr/local/lib
└─┬ angular-cli#1.0.0-beta.28.3
└── UNMET PEER DEPENDENCY rxjs#^5.0.1
So I tried to installing using #angular/cli instead of angular-cli and it worked.
npm install -g #angular/cli
I'm in exactly the same boat. I had a simple angular-cli repo from a couple of months ago, cloned it to a new machine running OSX Sierra, started getting these peer dependency errors when running npm install.
I've tried a fresh project and I can't even install angular-cli. Have tried installing rxjs globally, and by specific version.
While this posts adds little it is intended as corroborating evidence of the issue, and indication that the issue is likely non OS-specific.
[update] Frustratingly, running npm ls -g shows rxjs#5.0.1 is present.
When I run
npm install -g react-native-cli
I see this error
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/read-installed/node_modules/readdir-scoped-modules requires graceful-fs#'^4.1.2' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/read-installed/node_modules/graceful-fs,
npm WARN unmet dependency which is version 3.0.8
I've tried updating graceful-fs by
npm update -g graceful-fs
Reacts website suggests using sudo if you have a permission error. This error doesn't seem permission related but if it is, I can certainly run sudo.
I'm an npm and node noob so please ask for any more info that will help.
I ran npm update -g and then was able to install the React CLI.
I get the follow error when trying to install Ghost on ubuntu,
Node version
node -v
v0.10.22
NPM version
npm -v
1.4.21
Install output
sudo npm install --production
npm WARN package.json express#4.8.3 No README data
npm WARN package.json moment#2.4.0 No README data
npm WARN package.json mysql#2.1.1 No README data
npm WARN unmet dependency /usr/share/nginx/www/lm-ghost-0.5/node_modules/bookshelf requires semver#'~2.3.0' but will load
npm WARN unmet dependency /usr/share/nginx/www/lm-ghost-0.5/node_modules/semver,
npm WARN unmet dependency which is version 2.2.1
npm WARN unmet dependency /usr/share/nginx/www/lm-ghost-0.5/node_modules/knex requires semver#'^2.3.0' but will load
npm WARN unmet dependency /usr/share/nginx/www/lm-ghost-0.5/node_modules/semver,
npm WARN unmet dependency which is version 2.2.1
Recommendations appreciated!
I've just done a download of the latest official release from here:
https://github.com/TryGhost/Ghost/releases
Then I've run npm install --production and the only warning I get is this:
npm WARN engine html-to-text#0.1.0: wanted: {"node":"~0.8.0"} (current: {"node":"0.10.30","npm":"1.4.23"})
Are you sure you've downloaded the latest release version and not the github repository instead or another version?
Try to install ghost from that link in a clean directory, without sudo and see if it's still giving you warning.
sudo npm cache clean -f
sudo npm install -g n
sudo n stable
//This will install the latest stable version or you can go to https://nodejs.org for the latest 'recommended for most users' version and use:
sudo n 4.6.0