You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I should be able to run NPM install without warnings or errors
Actual Behaviour
The following messages appear when running npm install on WSL2/Windows10:
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
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 fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
> node-sass@4.14.1 install /mnt/c/Users/brobert/Documents/code/sampleTests/ui.frontend/node_modules/node-sass
> node scripts/install.js
Cached binary found at /home/brobert/.npm/node-sass/4.14.1/linux-x64-83_binding.node
> node-sass@4.14.1 postinstall /mnt/c/Users/brobert/Documents/code/sampleTests/ui.frontend/node_modules/node-sass
> node scripts/build.js
Binary found at /mnt/c/Users/brobert/Documents/code/sampleTests/ui.frontend/node_modules/node-sass/vendor/linux-x64-83/binding.node
Testing binary
Binary is fine
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN notsup Unsupported engine for watchpack-chokidar2@2.0.0: wanted: {"node":"<8.10.0"} (current: {"node":"14.4.0","npm":"6.14.5"})
npm WARN notsup Not compatible with your version of node/npm: watchpack-chokidar2@2.0.0
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/webpack-dev-server/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
added 1088 packages from 589 contributors and audited 1092 packages in 80.279s
45 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
Steps to Reproduce
Install WSL2 on Windows 10 -- OR -- Install NPM on Ubuntu Linux
execute npm install in the ui.frontend folder
Platform and Version
I experienced this on WSL2/Windows with Ubuntu and Node v14 but this should be readily reproducible in other platforms.
The text was updated successfully, but these errors were encountered:
We can't get rid of the warnings at the moment as this packages are all transitive dependencies of recent packages we use in the ui.frontend module. For example request is still used by the node-sass package and the issue for this project is still open (sass/node-sass#2851)
Expected Behaviour
I should be able to run NPM install without warnings or errors
Actual Behaviour
The following messages appear when running
npm install
on WSL2/Windows10:Steps to Reproduce
npm install
in the ui.frontend folderPlatform and Version
I experienced this on WSL2/Windows with Ubuntu and Node v14 but this should be readily reproducible in other platforms.
The text was updated successfully, but these errors were encountered: