error while doing npm install - node.js

I am trying to do 'npm install' inside one of my folders but i am getting error code E403 Forbidden :
npm WARN deprecated node-uuid#1.4.8: Use uuid module instead
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher
to avoid a RegExp DoS issue
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher
to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs#1.2.3: graceful-fs v3.0.0 and before will fail
on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as
possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0
(node_modules\chokidar\node_modules\fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: 403 Forbidden:
https://registry.npmjs.org/fsevents/-/fsevents-1.1.3.tgz
npm ERR! code E403
npm ERR! 403 Forbidden: binary-extensions#^1.0.0
My npm version is 5.5.1
My node version is v8.9.1
Also my system was formatted today and I had to re-install and re-setup everything from scratch. npm install was working till yesterday before my system was formatted.
I have attached the log file here.
https://github.com/angular/angular-cli/files/1499291/2017-11-23T13_25_27_656Z-debug.log
Thanks in advance
EDIT: every npm install is failing.
for reference here are the entries in my .npmrc file:
registry=http://registry.npmjs.org/
proxy=http://user_name:password#proxy:port
https-proxy=http://user_name:password#proxy:port
strict-ssl=false
I have tried many commands to get this working but no luck.
Note: my password contains '#' symbol but i have encoded it in my .npmrc file as %40

Ok, so i got around this particular problem. Seems like i had to update http to https in registry, and E403 was gone. But still i was facing other issues so decided to downgrade npm to 3.10.10 and node to 6.10.3.

From the first line it's saying old node-uuid module is deprecated and won't be maintained moving forward. Try reinstalling using these commands.
npm uninstall --save node-uuid
npm install --save uuid
In the second line it's asking for installation of minimatch
So try running the command :
npm install -g minimatch#3.0.4

Related

NPM install Gulp/Elixir

I'm following a course online and have downloaded Node and NPM.
I have done a package.json file and are have some problems with
the installation.
I really don't understand the error message. I had the latest
version of Node, I tried to downgrade the version to 6.10.3 (the same version in the online course) but I still don't work.
Is there someone here that knows what the problem can be? I'm new at this and not so experienced with the error messages.
{
"author": "Erika",
"description": "Jewelry Shop",
"private": true,
"dependencies": {
"gulp": "~4.0.0",
"laravel-elixir": "~5.0.0"
}
}
$ npm install
npm WARN deprecated babel-preset-es2015#6.24.1: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated gulp-util#3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated browserslist#0.4.0: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated minimatch#1.0.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated hoek#2.16.3: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated boom#2.10.1: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated cryptiles#2.0.5: This version is no longer maintained. Please upgrade to the latest version.
node-sass#3.13.1 install C:\httpdocs\ecommerce\node_modules\node-sass
node scripts/install.js
Cached binary found at C:\Users\Erika\AppData\Roaming\npm-cache\node-sass\3.13.1\win32-x64-48_binding.node
node-sass#3.13.1 postinstall C:\httpdocs\ecommerce\node_modules\node-sass
node scripts/build.js
Binary found at C:\httpdocs\ecommerce\node_modules\node-sass\vendor\win32-x64-48\binding.node
Testing binary
Binary is fine
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN acorn-dynamic-import#4.0.0 requires a peer of acorn#^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
added 1299 packages from 772 contributors and audited 17546 packages in 89.815s
found 11 vulnerabilities (8 moderate, 2 high, 1 critical)
run npm audit fix to fix them, or npm audit for details
Which portion of this message log are you concerned about?
It seems like it added the packages for you:
added 1299 packages from 772 contributors and audited 17546 packages in 89.815s
It just had some warnings displayed as well. The warnings may key in to potential issues when running whatever program you are trying to run afterwards, however, without any specific issue, you are probably fine.
The deprecated and unsupported warnings can be possibly fixed by installing the latest versions of the packages that you are using, but there is no guarantee that the package maintainers have updated their dependencies to suit.
To upgrade a package and save it you can use the following command:
npm -i --save gulp#latest laravel-elixir#latest
-i for install, --save to save this back in your dependencies in your package.json.

NPM: Installing Semantic-UI, the `semantic` folder does not appear

I'm following these instructions for Linux:
https://semantic-ui.com/introduction/getting-started.html
to install Semantic-UI. It seems that installing NodeJS went fine. When installing gulp I get the following warnings but no errors.
npm WARN deprecated gulp-util#3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated graceful-fs#3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs#1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
I tried following the instructions in the first line but it looked like all it does is just have you log issues or pull requests. I'm not super familiar with how that works but my understanding is that this is just to alert the Semantic-UI team to issues, and so this isn't really causing my error. I am not sure how to update or upgrade things except just to enter npm update and npm upgrade and I did that, although it didn't report that anything was updated or upgraded, so I'm not sure if it worked.
Initially when running the Semantic install it reported that it couldn't find a JSON file, so after searching that error I ran npm init and that seemed to fix it. However, when I run sudo npm install semantic-ui --save it produces
npm WARN deprecated gulp-util#3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated graceful-fs#3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs#1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated browserslist#2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated gulp-util#2.2.20: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated hoek#2.16.3: The major version is no longer supported. Please update to 4.x or newer
> semantic-ui#2.3.3 install /home/abcd/Web/ExplainSemantic/node_modules/semantic-ui
> gulp install
[14:52:34] Using gulpfile ~/Web/ExplainSemantic/node_modules/semantic-ui/gulpfile.js
[14:52:34] Starting 'install'...
Current version of Semantic UI already installed
npm WARN explainsemantic#1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
+ semantic-ui#2.3.3
updated 1 package in 4.06s
And when I ls I get
node_modules package.json package-lock.json
but no semantic/ folder, which is necessary for the remaining installation steps. So at this point I'm not sure what to do--fixing the dependencies doesn't seem to have worked and I'm not sure what else to do about that.
I found what was wrong, somehow the semantic/ folder got sent to my user folder (just above the Desktop). Moved the folder over to my project folder, the gulp build command works.

npm start not working and gulp is deprecate?

First post here. Sorry its so long.
I am trying to contribute towards an open source project on Github. I successfully downloaded and cloned the project. I am using Windows 10 and Node.js version v8.11.2
When I run npm start in my command prompt I get the following error:
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Ashley Clarke\AppData\Roaming\npm-cache\_logs\2018-06-06T18_34_45_556Z-debug.log
So I tried to make sure was connected to the gulp server in my Node.js command prompt.
And got this error:
C:\Users\Ashley Clarke>gulp server
[10:59:43] Local gulp not found in ~
[10:59:43] Try running: npm install gulp
Then when I ran npm install gulp this popped up.
C:\Users\Ashley Clarke>npm install gulp -g
npm WARN deprecated gulp-util#3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated graceful-fs#3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs#1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
C:\Users\Ashley Clarke\AppData\Roaming\npm\gulp -> C:\Users\Ashley Clarke\AppData\Roaming\npm\node_modules\gulp\bin\gulp.js
+ gulp#3.9.1
added 255 packages in 45.834s
I tried to go to https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5 but it talked about plugins. I guess I'm struggling with understanding what I need to do to connect to the gulp server so I can contribute to this open source project. Thanks!!
P.S tried to add pictures. Thanks in advance.

unable to install node 8 dependencies on ubuntu 16.4

I'm unable to install my project (that works very well under node 6). This is due to a dependency of node 8, that in addition to be deprecated also attempts to write somewhere where it doesn't have permissions.
ubuntu#ip-xxxxxxx:~/share_place/bin$ sudo npm i
npm WARN deprecated node-uuid#1.4.8: Use uuid module instead
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch#0.4.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated jade#0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated to-iso-string#0.0.2: to-iso-string has been deprecated, use #segment/to-iso-string instead.
npm WARN deprecated minimatch#0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs#1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm ERR! code 1
npm ERR! Command failed: /usr/bin/git clone --depth=1 -q -b v0.5.5 git://github.com/bookchin/node-ntp-client.git /home/ubuntu/.npm/_cacache/tmp/git-clone-cd074428
npm ERR! /home/ubuntu/.npm/_cacache/tmp/git-clone-cd074428/.git: Permission denied
npm ERR!
npm ERR! A complete log of this run can be found in:
npm ERR! /home/ubuntu/.npm/_logs/2017-06-15T13_45_37_010Z-debug.log
ubuntu#ip-xxxxx:~/share_place/bin$ node -v
v8.1.2
It's very frustrating for us, since we're developing under windows and mac without issues, but now we're stuck at the preproduction.
Any help would be very welcome, thanks
If npm is running as root (because of sudo), it will drop root privileges right before executing external scripts/programs (like git). By default it will setuid to nobody.
This causes permission issues because nobody is most likely not allowed to write to the directory /home/ubuntu/.npm/_cacache/tmp/git-clone-cd074428/ (hence the "Permission denied" error).
The best solution is to not use sudo at all. In your case, installing only local dependencies, it makes even less sense than the usual situation, where sudo is used to install something globally (-g).
Perhaps you may have to clean up the permissions in /home/ubuntu/.npm/ too, if some files/directories in there now belong to root:
sudo chown -R $USER /home/ubuntu/.npm

algular-cli installation issue with rxjs

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.

Resources