Develop Reference

Semantic-ui install fail npm

I get the following error when trying to install semantic-ui via npm for fresh project.
$ node -v
v16.14.0
$ npm -v
8.10.0
$ npm i semantic-ui
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 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 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 chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm ERR! code 1
npm ERR! path /home/indikau/workspace/learning/web_design/semantic_ui/Tutorial/13_theming/node_modules/semantic-ui
npm ERR! command failed
npm ERR! command sh -c gulp install
npm ERR! Error [ERR_REQUIRE_ESM]: require() of ES Module /home/indikau/workspace/learning/web_design/semantic_ui/Tutorial/13_theming/node_modules/del/index.js from /home/indikau/workspace/learning/web_design/semantic_ui/Tutorial/13_theming/node_modules/semantic-ui/tasks/clean.js not supported.
npm ERR! Instead change the require of index.js in /home/indikau/workspace/learning/web_design/semantic_ui/Tutorial/13_theming/node_modules/semantic-ui/tasks/clean.js to a dynamic import() which is available in all CommonJS modules.
npm ERR! at Object.<anonymous> (/home/indikau/workspace/learning/web_design/semantic_ui/Tutorial/13_theming/node_modules/semantic-ui/tasks/clean.js:8:12)
npm ERR! at Object.<anonymous> (/home/indikau/workspace/learning/web_design/semantic_ui/Tutorial/13_theming/node_modules/semantic-ui/gulpfile.js:21:18)
npm ERR! at async Promise.all (index 0) {
npm ERR! code: 'ERR_REQUIRE_ESM'
npm ERR! }
npm ERR! A complete log of this run can be found in:
npm ERR! /home/indikau/.npm/_logs/2022-10-20T01_40_53_411Z-debug-0.log

This is related to the del package being updated to ESM-only. You can fix this by forcing a resolution of del#6.1 (rather than 7.x) in your package.json.
I use yarn which has this built in. I believe you must use a package like this for npm https://github.com/rogeriochaves/npm-force-resolutions.

Why is node-sass being built when I upgrade from npm6 to npm7?

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.

Can't install opensea-js with NPM

I am currently using Node v14.16.0 and NPM v7.7.5 to install opensea-js as a dependency in a project.
I try to run the command npm install --save opensea-js, but I always end up with an error. I tried to clean NPM's cache, I have even reinstalled Node. I am on Windows. The stack trace is the following:
PS C:\multi-sender-opensea-js> npm install opensea-js
npm WARN deprecated safe-event-emitter#1.0.1: Renamed to #metamask/safe-event-emitter
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 resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated chokidar#2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated bignumber.js#6.0.0: Custom ALPHABET bug fixed in v7.0.2
npm WARN deprecated axios#0.17.1: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated core-js#1.2.7: 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 core-js#2.6.12: 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 core-js#2.6.12: 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 ERR! code 1
npm ERR! git dep preparation failed
npm ERR! command C:\Program Files\nodejs\node.exe C:\Users\aguay\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js install --force --cache=C:\Users\aguay\AppData\Local\npm-cache --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit
npm ERR! npm WARN using --force Recommended protections disabled.
npm ERR! npm WARN deprecated safe-event-emitter#1.0.1: Renamed to #metamask/safe-event-emitter
npm ERR! npm WARN deprecated har-validator#5.1.3: this library is no longer supported
npm ERR! npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm ERR! npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm ERR! npm WARN deprecated debug#3.2.6: 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 ERR! npm WARN deprecated chokidar#2.1.6: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm ERR! npm WARN deprecated nomnom#1.8.1: Package no longer supported. Contact support#npmjs.com for more info.
npm ERR! 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 ERR! npm WARN deprecated request#2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! npm WARN deprecated bignumber.js#6.0.0: Custom ALPHABET bug fixed in v7.0.2
npm ERR! npm WARN deprecated buffer#4.9.1: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer
npm ERR! npm WARN deprecated axios#0.17.1: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410npm ERR! npm WARN tarball tarball data for ethereumjs-abi#git+ssh://git#github.com/ProjectWyvern/ethereumjs-abi.git (sha512-yLrVA0M7LdolTGm4Eeh+SOffugSViZY9z/j5ctseZn5jTBJ5DAbyZ3vu1lQzHhbTSI2KpzEbKnfkT8LeNZSgog==) seems to be corrupted. Trying again.
npm ERR! npm WARN tarball tarball data for ethereumjs-abi#git+ssh://git#github.com/ethereumjs/ethereumjs-abi.git (sha512-u07PCyvWSxvmLPqnK7XBY4Ia7j6aTf5BmKy2dbT297VMIXLjOaZJfu4SMcoPF2GSCINCRlVwIOqaLuSJ5UZANA==) seems to be corrupted. Trying again.
npm ERR! npm WARN tarball tarball data for ethereumjs-abi#git+ssh://git#github.com/ProjectWyvern/ethereumjs-abi.git (sha512-yLrVA0M7LdolTGm4Eeh+SOffugSViZY9z/j5ctseZn5jTBJ5DAbyZ3vu1lQzHhbTSI2KpzEbKnfkT8LeNZSgog==) seems to be corrupted. Trying again.
npm ERR! npm WARN tarball tarball data for ethereumjs-abi#git+ssh://git#github.com/ethereumjs/ethereumjs-abi.git (sha512-u07PCyvWSxvmLPqnK7XBY4Ia7j6aTf5BmKy2dbT297VMIXLjOaZJfu4SMcoPF2GSCINCRlVwIOqaLuSJ5UZANA==) seems to be corrupted. Trying again.
npm ERR! npm WARN tarball tarball data for bignumber.js#git+ssh://git#github.com/frozeman/bignumber.js-nolookahead.git (sha512-BPWfW6xhAeth4aWLg1g++Nrkn5KN+iqMsKQAdr/IywRCyBSjQ9JnyL49/Z3wgj2O/uW47RlYI2XPbJTKSoaVkw==) seems to be corrupted. Trying again.
npm ERR! npm WARN tarball tarball data for bignumber.js#git+ssh://git#github.com/frozeman/bignumber.js-nolookahead.git (sha512-BPWfW6xhAeth4aWLg1g++Nrkn5KN+iqMsKQAdr/IywRCyBSjQ9JnyL49/Z3wgj2O/uW47RlYI2XPbJTKSoaVkw==) seems to be corrupted. Trying again.
npm ERR! npm WARN deprecated core-js#2.6.9: 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 ERR! npm ERR! code EINTEGRITY
npm ERR! npm ERR! sha512-u07PCyvWSxvmLPqnK7XBY4Ia7j6aTf5BmKy2dbT297VMIXLjOaZJfu4SMcoPF2GSCINCRlVwIOqaLuSJ5UZANA== integrity checksum failed when using sha512:
wanted sha512-u07PCyvWSxvmLPqnK7XBY4Ia7j6aTf5BmKy2dbT297VMIXLjOaZJfu4SMcoPF2GSCINCRlVwIOqaLuSJ5UZANA== but got sha512-IA4lM/EAhHCmgR0uepm5PJ4b5/zcONaHZbBVlPbSbPT2+Mqbhj01vl11bupQPovWF6gHA3cDNkanFuaD3LTh5Q==. (13945 bytes)
npm ERR!
npm ERR! npm ERR! A complete log of this run can be found in:
npm ERR! npm ERR! C:\Users\aguay\AppData\Local\npm-cache\_logs\2021-03-26T20_11_41_637Z-debug.log
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\aguay\AppData\Local\npm-cache\_logs\2021-03-26T20_11_45_803Z-debug.log
Does someone have an idea how I can solve this? Thank you in advance!

Try switching to Node.js version 8.11 to make sure common crypto dependencies work.
Execute nvm use, if you have Node Version Manager.
Try installing web3
from the opensea-js npm page

npm WARN deprecated when running 'vue init webpack my-project'

My Goal:wanna initialize Vue.js project by running commands vue init webpack myproject
Expected Result: install all the dependencies with no fatal error, AND would be able to start running the project by npm dev run,and run project on http://localhost:8080
ACTUAL Result:
# Installing project dependencies ...
# ========================
npm WARN deprecated extract-text-webpack-plugin#3.0.2: Deprecated. Please use https://gi
thub.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated browserslist#2.11.3: Browserslist 2 could fail on reading Browsersli
st >3.0 config used in other tools.
npm WARN deprecated bfj-node4#5.3.1: Switch to the `bfj` package for fixes and new featu
res!
npm WARN deprecated core-js#2.6.11: core-js#<3 is no longer maintained and not recommend
ed for usage due to the number of issues. Please, upgrade your dependencies to the actua
l version of core-js#3.
npm WARN deprecated browserslist#1.7.7: Browserslist 2 could fail on reading Browserslis
t >3.0 config used in other tools.
npm WARN deprecated circular-json#0.3.3: CircularJSON is in maintenance only, flatted is
its successor.
npm ERR! Unexpected end of JSON input while parsing near '...,"dist":{"shasum":"1e'
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Administrator\AppData\Roaming\npm-cache\_logs\2020-02-12T06_01_01_
430Z-debug.log
Running eslint --fix to comply with chosen preset rules...
# ========================
> travel#1.0.0 lint F:\SourceCode\Travel-master\Travel
> eslint --ext .js,.vue src "--fix"
Oops! Something went wrong! :(
ESLint: 6.8.0.
ESLint couldn't find the plugin "eslint-plugin-vue".
(The package "eslint-plugin-vue" was not found when loaded as a Node module from the dir
ectory "F:\SourceCode\Travel-master\Travel".)
It's likely that the plugin isn't installed correctly. Try reinstalling by running the f
ollowing:
npm install eslint-plugin-vue#latest --save-dev
The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js".
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslin
t to chat with the team.
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! travel#1.0.0 lint: `eslint --ext .js,.vue src "--fix"`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the travel#1.0.0 lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging out
put above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Administrator\AppData\Roaming\npm-cache\_logs\2020-02-12T06_01_04_
492Z-debug.log
# Project initialization finished!
# ========================
To get started:
cd Travel
npm run dev
Documentation can be found at https://vuejs-templates.github.io/webpack
What I've tried
run the commands like above mentioned npm install eslint-plugin-vue#latest --save-dev,then comes another issue like below:
npm ERR! code ETARGET
npm ERR! notarget No matching version found for eslint-plugin-vue#lastest.
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\Administrator\AppData\Roaming\npm-cache\_logs\2020-02-12T06_09_11_
766Z-debug.log
even I tried the npm install webpack -dev-server -g,then comes another issue like below:
C:\Program Files\nodejs\webpack -> C:\Program Files\nodejs\node_modules\webpack\bin\webp
ack.js
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.11 (node_modules\webpack\no
de_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.11:
wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
+ webpack#4.41.6
added 322 packages from 197 contributors in 255.517s

I had the same problem when coding my app (MEVN) and using the command vue init webpack client.
So I did a bit of research notably on npm to see what was wrong and found this: https://www.npmjs.com/package/vue-cli so apparently you can't use this command anymore.
So if you wish to use the vue cli you need to install it trough npm install -g #vue/cli and then run vue create <dir name>
For further information you can look into the documentation: https://www.npmjs.com/package/#vue/cli with the documentation on the vuejs website: https://cli.vuejs.org/
Hope this helps and have fun coding

Failed at the node-sass#0.9.6 install script 'node build.js'

I'm getting this error while running npm install on project. The additional information about this issue below,
npm ERR! node-sass#0.9.6 install: `node build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass#0.9.6 install script 'node build.js'.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node build.js
npm ERR! You can get their info via:
npm ERR! npm owner ls node-sass
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/capricornus/Projects/aware-app/npm-debug.log

Just install older version of Nodejs with nodebrew.
curl -L git.io/nodebrew | perl - setup
Add the following to ~/.bashrc
export PATH=$HOME/.nodebrew/current/bin:$PATH
Refresh console
source ~/.bashrc
Install older version
nodebrew install-binary v0.12.7
nodebrew use v0.12.7
Then try again!

It looks like this version is no longer compatible. I get the same errors on my system. Either you need to downgrade node to the supported version, or upgrade the dependencies that require node-sass#0.9.6.
Latest version of node-sass is 3.4.2.

In case someone runs into trouble with nodebrew, it's also possible to use nvm (node version manager) to downgrade your node version. Project on Github
On OSX El Capitan, I needed this for the installation:
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.31.0/install.sh | bash
. ~/.nvm/nvm.sh
Mind the last line, as it's slightly different from the install instruction on github.
As mentioned by Yosuke Sato, v0.12.7 is compatible with node-sass#0.9.6, so you'd need
nvm install v0.12.7 or nvm use v0.12.7 (if you have it installed already)
This will use the older node version, but only in the current terminal window/tab.

nvm use v0.12.7 in the project directory followed by npm install solved the problem for me -- the error occurred as I was trying to set up broccoli-taco, a static site generator. Thanks for tip, I am glad I googled you up.