Unable to remove npm warn message while running angular application - node.js

I need one help. I need to remove the npm warn message while I am trying to do the npm install through dockerfile. I am explaining those warning message below.
while running RUN npm install --no-package-lock getting the following warn message.
npm WARN deprecated #angular/http#7.2.16: Package no longer supported. Use #angular/common instead, see https://angular.io/guide/deprecations#angularhttp
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 ag-grid#18.1.2: ag-grid is now deprecated - please use #ag-grid-community/all-modules. See www.ag-grid.com/javascript-grid-modules/ for more information.
npm WARN deprecated popper.js#1.16.1: You can find the new Popper v2 at #popperjs/core, this package is dedicated to the legacy v1
npm WARN deprecated fsevents#2.1.2: "Please update to latest v2.3 or v2.2"
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 ini#1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated chokidar#2.0.4: 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 clipboard-js#0.3.6: Please migrate to https://github.com/lgarron/clipboard-polyfill
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 har-validator#5.1.5: this library is no longer supported
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
and while running RUN npm install then getting the following warnings.
npm WARN deprecated fsevents#2.1.2: "Please update to latest v2.3 or v2.2"
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 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/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.2 (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#~2.3.2 (node_modules/watchpack/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
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/#angular/compiler-cli/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 #auth0/angular-jwt#5.0.2 requires a peer of #angular/common#>=9.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ng-file-drop#5.0.2 requires a peer of #angular/common#^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ng-file-drop#5.0.2 requires a peer of #angular/core#^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ng-file-drop#5.0.2 requires a peer of #angular/platform-browser#^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ng-file-drop#5.0.2 requires a peer of rxjs#^5.5.2 but none is installed. You must install peer dependencies yourself.
So here I need to remove these warnings while running those command through dockerfile. I also tried many options by searching from google but those did not give the right solutions. Can any body help me to resolve this issue ?

Related

I'm trying to create a spfx environment, i ran command "npm i -g #microsoft/generator-sharepoint" and i returned with error "code EEXIST"

my node version is 10.13.0, i'm using this version because of a specific project dependency and i'm using my office laptop,
I'm also having
+-- gulp#4.0.2
+-- typescript#4.9.5
`-- yo#4.3.1
i want to install "npm i -g #microsoft/generator-sharepoint" but i'm getting error "code EEXIST"
I'm new to this so don't have much knowledge what is this and i'm working on this for 2 days still not able to fix it.
npm WARN deprecated uuid#3.1.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated read-package-tree#5.1.6: The functionality that this package provided is now in #npmcli/arborist
npm WARN deprecated readdir-scoped-modules#1.1.0: This functionality has been moved to #npmcli/fs
npm WARN deprecated svgo#1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated stable#0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated source-map-resolve#0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
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 querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
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 fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated fsevents#2.1.3: "Please update to latest v2.3 or v2.2"
npm WARN deprecated #npmcli/move-file#1.1.2: This functionality has been moved to #npmcli/fs
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#~2.3.2 (node_modules\#microsoft\generator-sharepoint\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules\#microsoft\generator-sharepoint\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":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#~2.1.2 (node_modules\#microsoft\generator-sharepoint\node_modules\#rushstack\typings-generator\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":"win32","arch":"x64"})
npm WARN yeoman-generator#5.6.1 requires a peer of yeoman-environment#^3.2.0 but none is installed. You must install peer dependencies yourself.
npm WARN #rushstack/webpack4-module-minifier-plugin#0.9.31 requires a peer of #types/webpack#* but none is installed. You must install peer dependencies yourself.
npm WARN #rushstack/webpack4-module-minifier-plugin#0.9.31 requires a peer of #types/webpack-sources#* but none is installed. You must install peer dependencies yourself.
npm WARN node-fetch#2.6.7 requires a peer of encoding#^0.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN #rushstack/webpack4-localization-plugin#0.15.25 requires a peer of #types/webpack#^4.39.0 but none is installed. You must install peer dependencies yourself.
npm WARN #rushstack/set-webpack-public-path-plugin#3.3.69 requires a peer of #types/webpack#^4.39.8 but none is installed. You must install peer dependencies yourself.
npm WARN #rushstack/set-webpack-public-path-plugin#3.3.69 requires a peer of webpack#^5.35.1 but none is installed. You must install peer dependencies yourself.
npm WARN #microsoft/loader-load-themed-styles#1.9.174 requires a peer of #types/webpack#^4 but none is installed. You must install peer dependencies yourself.
npm WARN sass-loader#8.0.2 requires a peer of node-sass#^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN sass-loader#8.0.2 requires a peer of fibers#>= 3.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN node-fetch#2.6.9 requires a peer of encoding#^0.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN node-fetch#2.6.7 requires a peer of encoding#^0.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN #rushstack/webpack-plugin-utilities#0.1.36 requires a peer of #types/webpack#^4.39.8 but none is installed. You must install peer dependencies yourself.
npm WARN #rushstack/webpack-plugin-utilities#0.1.36 requires a peer of webpack#^5.35.1 but none is installed. You must install peer dependencies yourself.
npm WARN ws#8.12.0 requires a peer of bufferutil#^4.0.1 but none is installed. You must install peer dependencies yourself.
npm WARN ws#8.12.0 requires a peer of utf-8-validate#>=5.0.2 but none is installed. You must install peer dependencies yourself.
npm WARN ajv-formats#2.1.1 requires a peer of ajv#^8.0.0 but none is installed. You must install peer dependencies yourself.
npm ERR! path C:\Users\AryanSharma\AppData\Roaming\npm\node_modules\#microsoft\generator-sharepoint\node_modules\.bin\browserslist.cmd
npm ERR! code EEXIST
npm ERR! Refusing to delete C:\Users\AryanSharma\AppData\Roaming\npm\node_modules\#microsoft\generator-sharepoint\node_modules\.bin\browserslist.cmd: is outside C:\Users\AryanSharma\AppData\Roaming\npm\node_modules\#microsoft\generator-sharepoint\node_modules\browserslist and not a link
npm ERR! File exists: C:\Users\AryanSharma\AppData\Roaming\npm\node_modules\#microsoft\generator-sharepoint\node_modules\.bin\browserslist.cmd
npm ERR! Move it away, and try again.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\AryanSharma\AppData\Roaming\npm-cache\_logs\2023-02-02T09_55_50_116Z-debug.log
I want to create a new webpart but so many errors
as this error suggests: npm ERR! Move it away, and try again. Please Check whether you have installed the package in your environment, and then try to remove and reinstall it.
The version of the yeoman template you are trying to install is not compatible with NodeJs v10.13.1. Use the following command instead
npm i -g #microsoft/generator-sharepoint#1.12.1
The full list of SPFx compatibility can be found at https://learn.microsoft.com/en-us/sharepoint/dev/spfx/compatibility
From that list, you can see that SPFx v1.12.1 is the last version that supported NodeJs v10.x
Also, you should remove gulp from the global space and replace it with gulp-cli by running the following commands
npm uninstall - gulp
npm i -g gulp-cli
Having typescript installed is also unneeded, so that can be uninstalled.
Lastly, you can always ignore the WARN messages.
Good luck!
Good luck!Don
If my answer helps solve or resolve your issue, please consider clicking Mark as Best Response & Like. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it a Like.

npm warning after upgrading angular version

I am facing the below warnings while upgrading from angular 8 to 14. I can build and run application properly despite the warning. However, I would like to remove the warning. Below is the warning. How do I remove it?
Angular version: 14.2.0
nodejs version : 14.17.6
npm WARN ajv-keywords#3.5.2 requires a peer of ajv#^6.9.1 but none is installed. You must install peer dependencies yourself.
npm WARN codelyzer#6.0.2 requires a peer of #angular/compiler#>=2.3.1 <13.0.0 || ^12.0.0-next || ^12.1.0-next || ^12.2.0-next but none is installed. You must install peer dependencies yourself.
npm WARN codelyzer#6.0.2 requires a peer of #angular/core#>=2.3.1 <13.0.0 || ^12.0.0-next || ^12.1.0-next || ^12.2.0-next but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-darwin-64#0.15.5 (node_modules\esbuild-darwin-64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-darwin-64#0.15.5: wanted {"os":"darwin","arch":"x64"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-android-arm64#0.15.5 (node_modules\esbuild-android-arm64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-android-arm64#0.15.5: wanted {"os":"android","arch":"arm64"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #esbuild/linux-loong64#0.15.5 (node_modules#esbuild\linux-loong64):

Can't use expo and expo-cli on Windows

I tried installing expo-cli with npm globally:
$ npm i -g expo-cli
When I tried that I got some warnings about deprecation:
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
npm WARN deprecated joi#14.0.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
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 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 joi#11.4.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated hoek#4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated topo#2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated hoek#6.1.3: This module has moved and is now available at #hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated topo#3.0.3: This module has moved and is now available at #hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
> #expo/traveling-fastlane-linux#1.14.0 preinstall C:\Users\myuser\AppData\Roaming\npm\node_modules\expo-cli\node_modules\#expo\traveling-fastlane-linux
> node platform.js
Does not seem like WSL enabled on this machine. Download a Linux distro from the Windows Store, run it at least onceand then make sure to run in an admin powershell:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
C:\Users\myuser\AppData\Roaming\npm\expo -> C:\Users\myuser\AppData\Roaming\npm\node_modules\expo-cli\bin\expo.js
C:\Users\myuser\AppData\Roaming\npm\expo-cli -> C:\Users\myuser\AppData\Roaming\npm\node_modules\expo-cli\bin\expo.js
> core-js#2.6.11 postinstall C:\Users\myuser\AppData\Roaming\npm\node_modules\expo-cli\node_modules\babel-runtime\node_modules\core-js
> node -e "try{require('./postinstall')}catch(e){}"
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
> core-js#3.6.5 postinstall C:\Users\myuser\AppData\Roaming\npm\node_modules\expo-cli\node_modules\core-js
> node -e "try{require('./postinstall')}catch(e){}"
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #expo/traveling-fastlane-darwin#1.14.0 (node_modules\expo-cli\node_modules\#expo\traveling-fastlane-darwin):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for #expo/traveling-fastlane-darwin#1.14.0: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #expo/ngrok-bin-sunos-x64#2.2.8 (node_modules\expo-cli\node_modules\#expo\ngrok-bin\node_modules\#expo\ngrok-bin-sunos-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for #expo/ngrok-bin-sunos-x64#2.2.8: wanted {"os":"sunos","arch":"x64"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #expo/ngrok-bin-darwin-ia32#2.2.8 (node_modules\expo-cli\node_modules\#expo\ngrok-bin\node_modules\#expo\ngrok-bin-darwin-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for #expo/ngrok-bin-darwin-ia32#2.2.8: wanted {"os":"darwin","arch":"ia32"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #expo/ngrok-bin-freebsd-ia32#2.2.8 (node_modules\expo-cli\node_modules\#expo\ngrok-bin\node_modules\#expo\ngrok-bin-freebsd-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for #expo/ngrok-bin-freebsd-ia32#2.2.8: wanted {"os":"freebsd","arch":"ia32"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #expo/ngrok-bin-win32-ia32#2.2.8-beta.1 (node_modules\expo-cli\node_modules\#expo\ngrok-bin\node_modules\#expo\ngrok-bin-win32-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for #expo/ngrok-bin-win32-ia32#2.2.8-beta.1: wanted {"os":"win32","arch":"ia32"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #expo/ngrok-bin-linux-arm64#2.2.8 (node_modules\expo-cli\node_modules\#expo\ngrok-bin\node_modules\#expo\ngrok-bin-linux-arm64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for #expo/ngrok-bin-linux-arm64#2.2.8: wanted {"os":"linux","arch":"arm64"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #expo/ngrok-bin-linux-x64#2.2.8 (node_modules\expo-cli\node_modules\#expo\ngrok-bin\node_modules\#expo\ngrok-bin-linux-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for #expo/ngrok-bin-linux-x64#2.2.8: wanted {"os":"linux","arch":"x64"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #expo/ngrok-bin-darwin-x64#2.2.8 (node_modules\expo-cli\node_modules\#expo\ngrok-bin\node_modules\#expo\ngrok-bin-darwin-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for #expo/ngrok-bin-darwin-x64#2.2.8: wanted {"os":"darwin","arch":"x64"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #expo/ngrok-bin-freebsd-x64#2.2.8 (node_modules\expo-cli\node_modules\#expo\ngrok-bin\node_modules\#expo\ngrok-bin-freebsd-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for #expo/ngrok-bin-freebsd-x64#2.2.8: wanted {"os":"freebsd","arch":"x64"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #expo/ngrok-bin-linux-arm#2.2.8 (node_modules\expo-cli\node_modules\#expo\ngrok-bin\node_modules\#expo\ngrok-bin-linux-arm):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for #expo/ngrok-bin-linux-arm#2.2.8: wanted {"os":"linux","arch":"arm"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: #expo/ngrok-bin-linux-ia32#2.2.8 (node_modules\expo-cli\node_modules\#expo\ngrok-bin\node_modules\#expo\ngrok-bin-linux-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for #expo/ngrok-bin-linux-ia32#2.2.8: wanted {"os":"linux","arch":"ia32"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.2.7 (node_modules\expo-cli\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":"win32","arch":"x64"})
npm WARN notsup Unsupported engine for watchpack-chokidar2#2.0.0: wanted: {"node":"<8.10.0"} (current: {"node":"14.0.0","npm":"6.14.4"})
npm WARN notsup Not compatible with your version of node/npm: watchpack-chokidar2#2.0.0
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#~2.1.2 (node_modules\expo-cli\node_modules\watchpack\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":"win32","arch":"x64"})
+ expo-cli#3.21.5
added 1819 packages from 839 contributors and updated 1 package in 74.995s
Although it looks like it installed successfully.
The issue is that when I want to use expo init something the bash says it doesn't recognize it.
How can I fix it?
Enviorment:
OS: Windows 10
Terminal: Git Bash
You might have to add npm folder to your environment variables manually.
You can do this by following the steps:
Open start and search for environment variables.
In the path variable under the system variables,add:
%USERPROFILE%\AppData\Roaming\npm
Save and exit
Open a new terminal and type your command. Hopefully, it should work.

Material-UI Can't import slider

import Slider from '#material-ui/lab/Slider';
returns an error on build
ERROR in ./src/components/StepSlider/StepSlider-view.jsx
Module not found: Error: Can't resolve '#material-ui/lab/Slider' in 'D:\GIT\...\components\StepSlider'
# ./src/components/StepSlider/StepSlider-view.jsx 2:0-45 29:26-32
# ./src/components/StepSlider/index.js
# ./src/components/plan_option_slider/PlanOptionSlider-view.jsx
# ./src/components/plan_option_slider/index.jsx
# ./src/features/plans/plans-view.jsx
# ./src/features/plans/index.jsx
# ./src/App.jsx
# ./src/index.jsx
Searching this error tells me to install lab, I'd already done that, but figured I'd give it another chance:
npm install #material-ui/lab
npm WARN bootstrap#4.4.1 requires a peer of popper.js#^1.16.0 but none is installed. You must install peer dependencies yourself.
npm WARN material-ui-pickers#2.2.4 requires a peer of #material-ui/core#^3.2.0 but none is installed. You must install
peer dependencies yourself.
npm WARN restaurant_project#1.0.0 No description
npm WARN restaurant_project#1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.11 (node_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"})
+ #material-ui/lab#4.0.0-alpha.40
updated 1 package and audited 12006 packages in 13.041s
found 0 vulnerabilities
I followed this:
npm WARN ... requires a peer of ... but none is installed. You must install peer dependencies yourself
(I was pretty sure I had all this installed, but figured I'd follow directions)
npm install --save-dev popper.js#^1.16.0
npm WARN deprecated popper.js#1.16.0: Popper changed home, find its new releases at #popperjs/core
npm WARN material-ui-pickers#2.2.4 requires a peer of #material-ui/core#^3.2.0 but none is installed. You must install
peer dependencies yourself.
npm WARN restaurant_project#1.0.0 No description
npm WARN restaurant_project#1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.11 (node_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"})
+ popper.js#1.16.0
updated 1 package and audited 12007 packages in 15.415s
found 0 vulnerabilities
npm install --save-dev #material-ui/core#^3.2.0
npm WARN #material-ui/icons#4.5.1 requires a peer of #material-ui/core#^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN #material-ui/lab#4.0.0-alpha.40 requires a peer of #material-ui/core#^4.9.0 but none is installed. You must install peer dependencies yourself.
npm WARN restaurant_project#1.0.0 No description
npm WARN restaurant_project#1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.11 (node_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"})
+ #material-ui/core#3.2.0
added 4 packages from 4 contributors, removed 26 packages, updated 5 packages and audited 11946 packages in 25.503s
found 0 vulnerabilities
This looks worrisome, it seems like the lab is asking for core4.9.0, but okay:
npm install --save-dev #material-ui/core#^4.0.0
npm WARN #material-ui/lab#4.0.0-alpha.40 requires a peer of #material-ui/core#^4.9.0 but none is installed. You must install peer dependencies yourself.
npm WARN material-ui-pickers#2.2.4 requires a peer of #material-ui/core#^3.2.0 but none is installed. You must install
peer dependencies yourself.
npm WARN restaurant_project#1.0.0 No description
npm WARN restaurant_project#1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.11 (node_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"})
+ #material-ui/core#4.0.0
added 26 packages from 8 contributors, removed 6 packages, updated 1 package and audited 12027 packages in 14.485s
found 0 vulnerabilities
So now it's telling me I need #material-ui/core#^3.2.0 again -- great, let me see if I can ignore that (it'll clear out the 4.9.0 I just installed)
npm install --save-dev #material-ui/core#^4.9.0
npm WARN material-ui-pickers#2.2.4 requires a peer of #material-ui/core#^3.2.0 but none is installed. You must install
peer dependencies yourself.
npm WARN restaurant_project#1.0.0 No description
npm WARN restaurant_project#1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.11 (node_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"})
+ #material-ui/core#4.9.0
added 5 packages from 4 contributors, removed 3 packages, updated 5 packages and audited 12007 packages in 15.823s
found 0 vulnerabilities
Alright, let's see if I can build it now.
No dice
ERROR in ./src/components/StepSlider/StepSlider-view.jsx
Module not found: Error: Can't resolve '#material-ui/lab/Slider' in 'D:\GIT\...\src\components\StepSlider'
# ./src/components/StepSlider/StepSlider-view.jsx 2:0-45 29:26-32
# ./src/components/StepSlider/index.js
# ./src/components/plan_option_slider/PlanOptionSlider-view.jsx
# ./src/components/plan_option_slider/index.jsx
# ./src/features/plans/plans-view.jsx
# ./src/features/plans/index.jsx
# ./src/App.jsx
# ./src/index.jsx
I'll try updating everything:
npm update
npm WARN deprecated popper.js#1.16.1: Popper changed home, find its new releases at #popperjs/core
npm WARN material-ui-pickers#2.2.4 requires a peer of #material-ui/core#^3.2.0 but none is installed. You must install
peer dependencies yourself.
npm WARN restaurant_project#1.0.0 No description
npm WARN restaurant_project#1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.11 (node_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"})
+ popper.js#1.16.1
updated 1 package and audited 12007 packages in 14.471s
found 0 vulnerabilities
build again:
no dice
ERROR in ./src/components/StepSlider/StepSlider-view.jsx
Module not found: Error: Can't resolve '#material-ui/lab/Slider' in 'D:\GIT\...\src\components\StepSlider'
# ./src/components/StepSlider/StepSlider-view.jsx 2:0-45 29:26-32
# ./src/components/StepSlider/index.js
# ./src/components/plan_option_slider/PlanOptionSlider-view.jsx
# ./src/components/plan_option_slider/index.jsx
# ./src/features/plans/plans-view.jsx
# ./src/features/plans/index.jsx
# ./src/App.jsx
# ./src/index.jsx
I'll try w/ the new popper
npm install #popperjs/core
npm WARN material-ui-pickers#2.2.4 requires a peer of #material-ui/core#^3.2.0 but none is installed. You must install
peer dependencies yourself.
npm WARN restaurant_project#1.0.0 No description
npm WARN restaurant_project#1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.11 (node_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"})
+ #popperjs/core#2.0.0
added 1 package from 1 contributor and audited 12008 packages in 19.887s
found 0 vulnerabilities
I'm lost, any help would be REALLY appreciated
https://material-ui.com/guides/migration-v3/
[Container] Moved from #material-ui/lab to #material-ui/core.
-import Container from '#material-ui/lab/Container';
+import Container from '#material-ui/core/Container';
after reading this I tested to see if they moved Slider too, they did.
import Slider from '#material-ui/lab/Slider';
should be
import Slider from '#material-ui/core/Slider';
Hope this saves someone else the time I wasted

Not able to install angularfire2 via npm

I am trying to install angularfire2 from npm by running, but I keep getting this error
D:\angular\firebase\apartment>npm install angularfire2 firebase --save
apartment#0.0.0 D:\angular\firebase\apartment
+-- angularfire2#4.0.0-rc.1
`-- firebase#4.1.3
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN angularfire2#4.0.0-rc.1 requires a peer of #angular/common#^4.0.0 but none was installed.
npm WARN angularfire2#4.0.0-rc.1 requires a peer of #angular/compiler#^4.0.0 but none was installed.
npm WARN angularfire2#4.0.0-rc.1 requires a peer of #angular/core#^4.0.0 but none was installed.
npm WARN angularfire2#4.0.0-rc.1 requires a peer of #angular/platform-browser#^4.0.0 but none was installed.
npm WARN angularfire2#4.0.0-rc.1 requires a peer of #angular/platform-browser-dynamic#^4.0.0 but none was installed.
Last 5 of npm warn's are due to dependencies. You don't have the required modules to install angularfire.
Two possible solutions are, either downgrade your npm i.e. lower than 3.
npm < 3 can download the depending modules by itself or install the 5 depending modules first.

Resources