Using WebStorm with Expo - node.js

Question

How do I use WebStorm (in particular for debugging, syntax checking and eslinting of TypeScript, etc.) with a managed Expo project? If I follow the Expo quick start with
expo init myapp
cd myapp
[myapp] expo start
(and selecting managed with tabs) everything works as expected. But as soon as I set up a React Native project in WebStorm using myapp as existing source, I run into all kinds of problems. First off, the process adds all kinds of things I don't think I really need, but that's recoverable. But then things get fatal pretty fast. Now if I try
[myapp] expo start
I'm told that expo is missing (wasn't it just there working fine?) and to install it. If I do that with
[myapp] npm install expo
I get a whole mass of package errors (see below) and then when I try
[myapp] expo start
again I get
watchman warning: Recrawled this watch 1 times, most recently because:
MustScanSubDirs UserDroppedTo resolve, please review the information on
https://facebook.github.io/watchman/docs/troubleshooting.html#recrawl
To clear this warning, run:
`watchman watch-del '/Users/Rax/Documents/Projects/Coding/React/learntest' ; watchman watch-project '/Users/Rax/Documents/Projects/Coding/React/learntest'`
Recrawled this watch 1 times, most recently because:
MustScanSubDirs UserDroppedTo resolve, please review the information on
https://facebook.github.io/watchman/docs/troubleshooting.html#recrawl
To clear this warning, run:
`watchman watch-del '/Users/Rax/Documents/Projects/Coding/React/learntest' ; watchman watch-project '/Users/Rax/Documents/Projects/Coding/React/learntest'`
and then finally crash completely once the app launches in Expo with
Unrecognized event: {"type":"transformer_load_started"}
Unrecognized event: {"type":"transformer_load_done"}
Started Metro Bundler
Error: Problem validating fields in app.json. Learn more: https://docs.expo.dev/workflow/configuration/
• should NOT have additional property 'displayName'.
iOS Bundling failed 10664ms
Unable to resolve module react-native-safe-area-context from /Users/Roy/Documents/Projects/Coding/React/learntest/App.tsx: react-native-safe-area-context could not be found within the project or in these directories:
node_modules
../../../../../node_modules
1 | import { StatusBar } from 'expo-status-bar';
> 2 | import { SafeAreaProvider } from 'react-native-safe-area-context';
| ^
3 |
4 | import useCachedResources from './hooks/useCachedResources';
5 | import useColorScheme from './hooks/useColorScheme';
What's going on here? Why does simply creating a WebStorm project from existing source wreck a functioning Expo project? Is there any way to get WebStorm to work with Expo? Is there some other IDE I should be using for that prupose?
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: #typescript-eslint/eslint-plugin#4.33.0
npm WARN Found: eslint#8.12.0
npm WARN node_modules/eslint
npm WARN peer eslint#">= 4.12.1" from babel-eslint#10.1.0
npm WARN node_modules/babel-eslint
npm WARN babel-eslint#"^10.1.0" from #react-native-community/eslint-config#3.0.1
npm WARN node_modules/#react-native-community/eslint-config
npm WARN 11 more (eslint-plugin-jest, eslint-config-prettier, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer eslint#"^5.0.0 || ^6.0.0 || ^7.0.0" from #typescript-eslint/eslint-plugin#4.33.0
npm WARN node_modules/#typescript-eslint/eslint-plugin
npm WARN #typescript-eslint/eslint-plugin#"^4.22.1" from #react-native-community/eslint-config#3.0.1
npm WARN node_modules/#react-native-community/eslint-config
npm WARN
npm WARN Conflicting peer dependency: eslint#7.32.0
npm WARN node_modules/eslint
npm WARN peer eslint#"^5.0.0 || ^6.0.0 || ^7.0.0" from #typescript-eslint/eslint-plugin#4.33.0
npm WARN node_modules/#typescript-eslint/eslint-plugin
npm WARN #typescript-eslint/eslint-plugin#"^4.22.1" from #react-native-community/eslint-config#3.0.1
npm WARN node_modules/#react-native-community/eslint-config
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: #typescript-eslint/parser#4.33.0
npm WARN Found: eslint#8.12.0
npm WARN node_modules/eslint
npm WARN peer eslint#">= 4.12.1" from babel-eslint#10.1.0
npm WARN node_modules/babel-eslint
npm WARN babel-eslint#"^10.1.0" from #react-native-community/eslint-config#3.0.1
npm WARN node_modules/#react-native-community/eslint-config
npm WARN 11 more (eslint-plugin-jest, eslint-config-prettier, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer eslint#"^5.0.0 || ^6.0.0 || ^7.0.0" from #typescript-eslint/parser#4.33.0
npm WARN node_modules/#typescript-eslint/parser
npm WARN #typescript-eslint/parser#"^4.22.1" from #react-native-community/eslint-config#3.0.1
npm WARN node_modules/#react-native-community/eslint-config
npm WARN 1 more (#typescript-eslint/eslint-plugin)
npm WARN
npm WARN Conflicting peer dependency: eslint#7.32.0
npm WARN node_modules/eslint
npm WARN peer eslint#"^5.0.0 || ^6.0.0 || ^7.0.0" from #typescript-eslint/parser#4.33.0
npm WARN node_modules/#typescript-eslint/parser
npm WARN #typescript-eslint/parser#"^4.22.1" from #react-native-community/eslint-config#3.0.1
npm WARN node_modules/#react-native-community/eslint-config
npm WARN 1 more (#typescript-eslint/eslint-plugin)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: eslint-plugin-react-native#3.11.0
npm WARN Found: eslint#8.12.0
npm WARN node_modules/eslint
npm WARN peer eslint#">= 4.12.1" from babel-eslint#10.1.0
npm WARN node_modules/babel-eslint
npm WARN babel-eslint#"^10.1.0" from #react-native-community/eslint-config#3.0.1
npm WARN node_modules/#react-native-community/eslint-config
npm WARN 11 more (eslint-plugin-jest, eslint-config-prettier, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer eslint#"^3.17.0 || ^4 || ^5 || ^6 || ^7" from eslint-plugin-react-native#3.11.0
npm WARN node_modules/eslint-plugin-react-native
npm WARN eslint-plugin-react-native#"^3.10.0" from #react-native-community/eslint-config#3.0.1
npm WARN node_modules/#react-native-community/eslint-config
npm WARN
npm WARN Conflicting peer dependency: eslint#7.32.0
npm WARN node_modules/eslint
npm WARN peer eslint#"^3.17.0 || ^4 || ^5 || ^6 || ^7" from eslint-plugin-react-native#3.11.0
npm WARN node_modules/eslint-plugin-react-native
npm WARN eslint-plugin-react-native#"^3.10.0" from #react-native-community/eslint-config#3.0.1
npm WARN node_modules/#react-native-community/eslint-config
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: use-subscription#1.6.0
npm WARN Found: react#17.0.2
npm WARN node_modules/react
npm WARN peer react#"17.0.2" from react-native#0.68.0
npm WARN node_modules/react-native
npm WARN peer react-native#"*" from #react-native-community/cli#7.0.3
npm WARN node_modules/#react-native-community/cli
npm WARN 1 more (the root project)
npm WARN 3 more (react-shallow-renderer, react-test-renderer, the root project)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react#"^18.0.0" from use-subscription#1.6.0
npm WARN node_modules/use-subscription
npm WARN use-subscription#"^1.0.0" from react-native#0.68.0
npm WARN node_modules/react-native
npm WARN
npm WARN Conflicting peer dependency: react#18.0.0
npm WARN node_modules/react
npm WARN peer react#"^18.0.0" from use-subscription#1.6.0
npm WARN node_modules/use-subscription
npm WARN use-subscription#"^1.0.0" from react-native#0.68.0
npm WARN node_modules/react-native
npm WARN deprecated uuid#3.4.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 uuid#3.4.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 uuid#3.4.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 core-js#1.2.7: core-js#<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
added 141 packages, changed 4 packages, and audited 1116 packages in 18s
99 packages are looking for funding
run `npm fund` for details
5 high severity vulnerabilities
To address all issues, run:
npm audit fix
Run `npm audit` for details.