react-native-template-new-architecture

[leotm]

leotm/react-native-template-new-architecture
Originally forked from react-native-community ❤️

RN 0.69.0

• Hermes
• Fabric
• TurboModules
• React 18

React Native

• 0.68.0-rc.4
• 0.68.0 stable
• 0.68.1 stable
• 0.69.0-rc0
• 0.69.0-rc1
• 0.69.0-rc6
• 0.69.0 stable
• 0.69.1

Latest/future (unsupported) architecture

• M1 (arm64)
• NDK 24 rc3
• NDK 25-rc2
• NDK 25-rc3
• NDK 25-rc4 🔥
• SDK 33-rc2 🔥
• SDK 33 stable
• JDK (aarch64)
  • openjdk-18 🔥
  • zulu-18
  • sapmachine-18
  • liberica-18 🐌
  • corretto-17
  • temurin-17

Official: environment-setup

• React Native is not compatible with JDK 18 facebook/react-native#34103

With few bleeding edge-tras

• TypeScript 4.6 nightly
• TypeScript 4.7 Beta
• TypeScript 4.7 stable
• TypeScript 4.8 Beta 🔥
• ESLint 8 (opinionated/all/unstable rules)
• Prettier 2
• Renovate
• RN Storybook v5 w server
• RN Storybook v6 alpha
• RN Storybook v6 beta
• Yarn 3.2
• Yarn 4
• RN Flipper latest w node server
• TS Node / Deno examples
• GitHub Actions workflow
  • Static analysis
  • Android on Ubuntu
  • iOS on macOS-12
• Wiki
• Project
• Security
• Labels

Xcode

• Xcode 13.3
• Xcode 13.3.1
• Xcode 13.4
• Xcode 14 beta 1 🔥

Ubuntu

• Ubuntu 20.04 🚀
• Ubuntu 22.04 beta

macOS 12

• Monterey 12.3
• Monterey 12.4 Beta
• Monterey 12.4 Beta 2
• Monterey 12.4 Beta 3
• Monterey 12.4 Beta 4
• Monterey 12.5 Beta
• Monterey 12.5 Beta 2
• Monterey 12.5 Beta 3 🔥

macOS 13

• Ventura 13.0 Beta 2

Gradual adoption

• react-navigation, react-native-screens and react-native-safe-area-context
  • M1 workaround Road to 0.68 react-native-releases#13 (reply in thread)
  • Gradle Wrapper clean issue
  • Demo app branch
• react-native-gesture-handler
• react-native-webview
• react-native-reanimated
• react-native-pager-view
• react-native-gesture-handler
• rnx-kit
• mobile-dev-inc/dadb

Issues

• Gradle requires 2nd build after clean (rebuild) leotm/react-native-template-new-architecture#482
• [Ubuntu 20.04] RN @0.68.1/nightly - AGP 7.1.1 - ReactAndroid:configureNdkBuildDebug leotm/react-native-template-new-architecture#521
• Android libraries need building all 4 default ABIs first leotm/react-native-template-new-architecture#525
• @swc-core Yarn cache/zip arch (linux-arm64, darwin-arm64) undesired local version control changes leotm/react-native-template-new-architecture#526
• Gradle - mergeDexRelease - @0.68.1-nightly leotm/react-native-template-new-architecture#553
• [Ubuntu 20.04] RN @0.69.0-rc.0 - :app:bundleReleaseJsAndAssets leotm/react-native-template-new-architecture#587
• suggestion: run yarn dedupe leotm/react-native-template-new-architecture#598
• react-native-codegen mismatch leotm/react-native-template-new-architecture#602
• [0.69.0-rc.0] Android crash only with New Arch leotm/react-native-template-new-architecture#613
• AGP 7.3.0-beta01 incompatible w Android Studio Electric Eel | 2022.1.1 Canary 2 leotm/react-native-template-new-architecture#618
• React Native 0.69-rc2,4 - hermes-engine.podspec leotm/react-native-template-new-architecture#636
• React Native 0.69-rc5 - RuntimeAdapter.h fatal error: 'hermes/hermes.h' file not found leotm/react-native-template-new-architecture#637
• java.io.IOException: No space left on device leotm/react-native-template-new-architecture#639
• TODO: Update

Will adjust docs for speedier Android builds when merged

• [Guide] Speeding up your Android/iOS Build facebook/react-native-website#3027

[cortinico]

Hi @leotm
I suppose this is a status update on the migration of react-native-template-typescript to the New Architecutre right? Could you edit your message and provide a better description on top as it's not immediately clear from reading this.

Also is the progress available on a branch on Github that users can take a look at?

[cortinico]

Thanks for the update. Before you fork react-native-community/react-native-template-typescript, have you considered contributing to the original repo?

I would start from opening a issue there and ask if you can contribute to their repo.

I appreciate your effort in creating an alternative, but I don't think we want to point users to a forked solution unless there is a valid strong opinion to pick your fork instead of react-native-community/react-native-template-typescript.

[leotm]

Np, yh I contributed couple yrs ago, albeit only a commit

I forked cos I don't think my wild opinionated ideas in combination constitute

Clean and minimalist React Native template for a quick start with TypeScript

[leotm]

Shall I continue to open an issue for this to contribute more?

(Last time I didn't open an issue, but just PR'ed which @emin93 accepted if i remember right)

I just don't want to force my opinions on the community pkg, but rather offer more (I'm looking at building a CLI)

I'm not trying to point anybody away from the OG that inspired me and the rest of us TypeScript fanbois/girls 😅 (sry Flow)

edit: also

we link this [react-native-community] template to official RN releases and not to the main branch. Otherwise the template could be incompatible with the stable release

my master's ahead on 0.68.0-rc3 (i.e. bleeding-edge edition/version)

[cortinico]

Hey @leotm,
I appreciate your effort in building this template. However, I suggest you to rename your repo to something other than react-native-template-typescript.

The reason is that your template is doing a bit more than just adding TypeScript support and I believe this could be confusing for your users and for the community in generally.

How do you feel about it?

[leotm]

Sure, feelin' good ^ done

[radko93]

Thanks for your work @leotm.
We have updated the official template with RN 0.68.0-rc.4 and everyone can try that by using 6.10.0-rc.1 or use next tag (versions are not tied to RN versions as we tend to have more updates for the template). We will update the template when the stable release is out.

To try the latest pre-release version:

npx react-native init MyApp --template react-native-template-typescript@next

We try to keep the template as close as possible to the core template by only adding a small subset of packages required for Typescript to work. By doing this, we can ensure that developer experience is the same as when using bare RN init command.

[leotm]

Sweet ^ saw last night but fell asleep half way thru reviewing sry, great stuff ☝️

[leotm]

My plans are more providing Re.Pack w Module Federation, ClojureScript, Speedy Web Compiler, a FastLane BUCK action/plugin that was never done, rnx-kit, React Concurrent and Suspense, etc and ripping the template apart more while upgrading everything to unstable versions for early adopters to spot/fix issues way ahead (not production) - then eventually run DOOM on it with WebAssembly as part of the unofficial FB-MSFT Collaboration and provide a CLI for stable/production

Keep up the good work

[radko93]

That's sounds exciting, I like the native additions because most of the JS side changed to the template are usually very opinionated (I don't use things from your template in my projects).