Closed adrianboisclair closed 4 years ago
re: the first group of warnings, we resolve these when we can but we don't always have control over the ability to upgrade dependencies right away. usually the warnings you see are from distant downstream dependencies, eg: expo-cli depends on a which depends on x which depends on y which depends on z. we have to wait for a to update their dependency on x which results in updating y and z. this is just a common thing you will see in the node ecosystem due to the way warnings are exposed to users (i disagree with this approach, but that's my own opinion). we update dependencies whenever it makes sense to, and we do that frequently.
re: "npm WARN optional SKIPPING OPTIONAL DEPENDENCY" warnings - this is unavoidable as long as you use the optionalDependencies
field in npm, which we use to ship ngrok and fastlane through expo-cli with binaries that run on windows, linux, and macos.
Description
There are many expo dependencies that seem to be deprecated. I am receiving a lot of warnings, nothing broke my installation but would like to help if I can, or if my env. is the cause of the issues
Expected Behavior
Expo-Cli installation shouldn't produce what seems like a large number of incompatible or deprecation warnings
Observed Behavior
LTS Node.js v. 12.16.3
npm install -g expo-cli => a ton of deprecated warnings display immediately in terminal running Mac OSX iMac 5k
Environment
Expo CLI 3.20.1 environment info:
Reproducible Demo
-- Just install it via npm and that is all.