This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
Expo CLI is not working in node v18.12.0 #4583
Labels
wontfix
This will not be worked on
Comments
tanbirahammad
added
the
needs review
|
Please migrate to the new versioned Expo CLI (npx expo) in SDK 46 which supports a much wider variety of Node.js versions (effectively all LTS+). If the issue persists with npx expo, please reopen on expo/expo with the CLI template and I’ll address it. |
EvanBacon
added
wontfix
gnprice
added a commit
to gnprice/zulip-mobile
that referenced
this issue
Dec 13, 2022
I believe we don't ever use the `expo` CLI. The `expo-cli` package is apparently in maintenance mode. It doesn't and won't support Node 18, the current LTS: expo/expo-cli#4583 expo/expo-cli#4281 That effectively gives it an EOL of 2023-09, the EOL date of Node 16, which is less than a year away. There's a successor CLI in the works: https://blog.expo.dev/the-new-expo-cli-f4250d8e3421 But since we don't actually use this CLI in the first place, we can wait to pick that up until we find a need for it. As a bonus, dropping this sheds about 90MB from our node_modules tree.
gnprice
added a commit
to gnprice/zulip-mobile
that referenced
this issue
Dec 13, 2022
We don't use the `expo` CLI in normal development; only when upgrading Expo itself. Discussion: zulip#5602 (comment) This `expo-cli` package is apparently in maintenance mode. It doesn't and won't support Node 18, the current LTS: expo/expo-cli#4583 expo/expo-cli#4281 That effectively gives it an EOL of 2023-09, the EOL date of Node 16, which is less than a year away. It also means an error when just trying to run `yarn install` with a newer Node version. So it'd be good to get it out of our dependencies. There's a successor CLI now: https://blog.expo.dev/the-new-expo-cli-f4250d8e3421 That one is shipped with Expo itself, starting with Expo 46. We're on Expo 45 at the moment, so we still have one more upgrade before then; when we go to do that upgrade, we might need some ad-hocery to get the CLI (either the old one or the new one, which IIUC was in beta in the Expo 45 period.) Until then, just drop it. As a bonus, dropping this sheds about 90MB from our node_modules tree. (At least for now; maybe Expo 46 will bring that all back.)
|
So, there's no way to use The only thing I can do is downgrade node to v16 if I want to upgrade expo to the latest version? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
npm start does not work in expo cli
Environment
npm start
Please specify your device/emulator/simulator platform, model and version
vs code
Error output
WARNING: expo-cli has not yet been tested against Node.js v18.12.0.
If you encounter any issues, please report them to https://github.com/expo/expo-cli/issues
expo-cli supports following Node.js versions:
Reproducible demo or steps to reproduce from a blank project
Starting project at D:\react native\starter\scopalomin
Unable to find expo in this project - have you run yarn / npm install yet?
The text was updated successfully, but these errors were encountered: