Can't install Gulp on node 8.12.0 - node.js

When I try the sudo npm install --save-dev gulp command, it returns this error:
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 gus#1.0.0 No description
npm WARN gus#1.0.0 No repository field.
I've reinstalled gulp (multiple times) and node (& npm) and it still won't work.
What do I do?
(I'm using macOS 10.13.6 and I installed node via homebrew)

Why are you trying to install with --save-dev?
Installing Gulp globally should be done with --global
Have you checked their installation guide?
https://gulpjs.org/getting-started.html

Related

"npm outdated" and "npm outdated -g" don't show anything so why am I getting these warnings of deprecations?

I have node.js version 12.16.3 (macOS x64), the most current LTS version. The npm version is 6.14.4, which comes as default with the node.js version already stated. My operating system is Catalina 10.15.4 (the latest version).
When I run npm outdated and npm outdated -g nothing is returned, I simply get a new line.
Yet when I run this inside of my project:
npm init followed by npm i --save-dev babel-cli babel-preset-env, I get these warnings:
npm WARN deprecated chokidar#1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated core-js#2.6.11: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm WARN deprecated fsevents#1.2.12: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
I have tried running npm install chokidar#^3 and I get the exact same warnings.
I have tried running npm install chokidar#latest and I get the exact same warnings.
I can't seem to update what I am being told to update. How can I resolve this issue?
Any help is much appreciated.

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.

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

Errors Installing KeystoneJS on OSX

I ran npm install -g generator-keystone from the root directory in OSX but got the following errors:
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 CSSselect#0.4.1: the module is now available as 'css-select'
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 CSSwhat#0.4.7: the module is now available as 'css-what'
When I try and use yo keystone I then get:
-bash: yo: command not found
I did try and update these packages using:
npm update -g minimatch
npm update -g CSSselect
npm update -g CSSwhat
Any advice would be greatly appreciated.
(PS I have Node 4.4.3 and Mongo Shell 3.2.7 installed)
The message you're getting are warnings, not errors. You can ignore them.
It looks like you may have only installed the Keystone generator for Yeoman, but didn't install the yeoman package itself:
$ npm i yo -g
That should provide the yo executable (which generally gets installed in /usr/local/bin).

Resources