NPM install Gulp/Elixir - node.js

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.

Related

NPM Error Message: I am getting an error message installing swagger

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements!
npm install -g swagger
npm WARN deprecated formidable#1.2.6: Please upgrade to latest, formidable#v2 or formidable#v3! Check these notes:
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 formidable#1.0.17: Please upgrade to latest, formidable#v2 or formidable#v3! Check these notes:
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 to-iso-string#0.0.2: to-iso-string has been deprecated, use #segment/to-iso-string instead.
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 URIjs#1.16.1: package renamed to "urijs" (lower-case), please update accordingly
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 minimatch#0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated mkdirp#0.3.0: 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 superagent#3.8.3: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem
errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.
npm WARN deprecated superagent#1.8.5: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem
errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.
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 swagger-editor#2.10.5: No longer maintained, please upgrade to swagger-editor#3.
npm WARN deprecated core-js#2.6.12: core-js#<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engin
e whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
added 453 packages, and audited 454 packages in 16s
8 packages are looking for funding
run `npm fund` for details
30 vulnerabilities (1 low, 11 moderate, 12 high, 6 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
npm install express
up to date, audited 219 packages in 987ms
23 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
Those are not errors but warnings that won't affect your working and how swagger behaves. They just notify the user who might be the maker of the package to update their package as the packages their package depends upon have been deprecated and may have bugs
It looks like it installed ok but as per #Arnav's answer it is just highlighting the deprecated packages.
I ran into a similar issue but the install was ultimately failing with ERR! messages when installing locally in the project.
Instead I installed globally with npm i -g swagger-editor which works fine.

Truffle Install (WARN deprecated)

`manuelfiestas#Manuels-MBP node_modules % npm install -g truffle
npm WARN deprecated mkdirp-promise#5.0.1: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated fsevents#2.1.3: "Please update to latest v2.3 or v2.2"
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated circular-json#0.5.9: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated debug#4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated remotedev-serialize#0.1.9: Package moved to #redux-devtools/serialize.
npm WARN deprecated redux-devtools-instrument#1.10.0: Package moved to #redux-devtools/instrument.
npm WARN deprecated redux-devtools-core#0.2.1: Package moved to #redux-devtools/app.
npm WARN deprecated ethereumjs-tx#2.1.2: New package name format for new versions: #ethereumjs/tx. Please update.
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 request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated multicodec#0.5.7: stable api reached
npm WARN deprecated node-pre-gyp#0.11.0: Please upgrade to #mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the #mapbox scoped package will recieve updates in the future
npm WARN deprecated axios#0.20.0: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated ethereumjs-common#1.5.2: New package name format for new versions: #ethereumjs/common. Please update.
npm WARN deprecated core-js#2.6.12: core-js#<3.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. Please, upgrade your dependencies to the actual version of core-js.
added 1713 packages, and audited 1714 packages in 1m
96 packages are looking for funding
run npm fund for details
53 vulnerabilities (16 low, 8 moderate, 29 high)
To address all issues, run:
npm audit fix
Run npm audit for details.
manuelfiestas#Manuels-MBP node_modules %`
delete all files you have in your filesystem from old failed installations and try again
The answer below stands for a manual installation, but there is a much simpler way : the automatic install.
Open Powershell as admin and run npm install -g windows-build-tools
The install takes time but it worked.

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.

error while doing npm install

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

Install ember#1.13.13 on Windows 7 and it keeps hanging on the extract of bower

I'm trying to "npm install -g ember#1.13.13" on Windows 7 and it keeps hanging on the extract of bower. I've tried clearing the npm cache and the bower cache but it still hangs. I'm installing that specific version of ember as that is the version required for the project I'm involved with. Here is the command window output;
C:\Windows\System32>npm install -g ember-cli#1.13.13
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 graceful-fs#2.0.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 gracef
ul-fs' to find it in the tree.
npm WARN deprecated lodash-node#2.4.1: This package has been discontinued in favor of lodash#^4.0.0.
npm WARN deprecated lodash-node#3.10.2: This package has been discontinued in favor of lodash#^4.0.0.
npm WARN deprecated cross-spawn-async#2.2.4: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN deprecated socket.io-pure#1.3.12: socket.io-pure is no longer maintained as the original socket.io removed all native dependencies. Please use the original.
npm WARN deprecated lodash#2.3.0: lodash#<3.0.0 is no longer maintained. Upgrade to lodash#^4.0.0.
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 engine.io-pure#1.5.9: engine.io-purce is no longer maintained as the original engine.io removed all native dependencies. Please use the original.
npm WARN deprecated socket.io-client-pure#1.3.12: socket.io-client-pure is no longer maintained as the original socket.io removed all native dependencies. Please use the original.
npm WARN deprecated ws-pure#0.8.0: ws-pure is no longer maintained as the original ws removed all native dependencies. Please use the original ws.
npm WARN deprecated engine.io-client-pure#1.5.9: engine-io-client-pure is no longer maintained as the original engine-io-client removed all native dependencies. Please use the orig
inal.
extract:bower ▌ ╢██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
These are the installed versions of
node: v4.4.7
npm: 3.3.12
bower: 1.7.9

Resources