feat: update to [email protected]

[YutaSugimura]

No description provided.

[esthor]

Can we get this merged?
Since the cli is on 0.69.4 now, when someone runs npx react-native init AwesomeTSProject --template react-native-template-typescript it will FAIL to resolve with

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/react-native
npm ERR!   peer react-native@"*" from @react-native-community/[email protected]
npm ERR!   node_modules/@react-native-community/cli
npm ERR!     @react-native-community/cli@"^6.0.0" from [email protected]
npm ERR!   react-native@"0.69.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! react-native@"0.69.4" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"18.0.0" from [email protected]
npm ERR!   node_modules/react-native
npm ERR!     react-native@"0.69.4" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
...

In order for someone to be able to use the typescript template as-is, and not risk incorrect dependency resolution, they will need to pass the version number to the CLI. (This is probably not obvious to the majority of react-native init users):

npx [email protected] init AwesomeTSProject --template react-native-template-typescript

[radko93]

Somehow missed that, releasing right now! Thanks!

[esthor]

Omg, thank you! That was fast! 🤘