Tom Sherman
Tom Sherman
See https://reactnative.dev/docs/new-architecture-library-intro https://reactnative.dev/blog/2022/06/16/resources-migrating-your-react-native-library-to-the-new-architecture
See https://reactnative.dev/docs/new-architecture-library-intro https://reactnative.dev/blog/2022/06/16/resources-migrating-your-react-native-library-to-the-new-architecture
Closes #14668
**Is your feature request related to a problem? Please describe.** It's fiddly to convert `Deno.test(name, fn)` to `Deno.test({ name, fn, ignore: true })` or `Deno.test({ name, fn, only: true })`....
## Describe the feature Support new React Native architecture. ## Motivation So that we can take advantage of React 18 features. ## Related Issues See https://reactnative.dev/docs/new-architecture-library-intro https://reactnative.dev/blog/2022/06/16/resources-migrating-your-react-native-library-to-the-new-architecture
Could this be supported out of the box? Looks like there's been some teething problems getting it to work here: https://github.com/cloudflare/workerd/issues/20#issuecomment-1259542697
See https://reactnative.dev/docs/new-architecture-library-intro https://reactnative.dev/blog/2022/06/16/resources-migrating-your-react-native-library-to-the-new-architecture
Repro: https://github.com/tom-sherman/manypkg-getpackages-pnpm-workspace-bug Originally raised in https://github.com/changesets/changesets/issues/957
### Pre-Checks - [X] Check that there isn't [already an issue](https://github.com/elk-zone/elk/issues) that reports the same bug to avoid creating a duplicate. - [X] Check that this is a concrete bug....
### Current Behavior When using pnpm workspaces, versions are not resolved using the project's node_modules when the same package is installed in the workspace root. ### Expected Behavior If a...