feat: new template

[jbroma]

Summary

Closes #325

• - add new welcome package with the template
• - include the welcome package with platform-ios & platform-android
• - make @rnef/welcome package work without packageExports

Screenshots

Light mode:

Android	iOS

Dark mode:

Android	iOS

Test plan

• - works in newly created app

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
rnef	⬜️ Ignored (Inspect)	Visit Preview		Jun 3, 2025 1:03pm

[jbroma]

@thymikee I can't reproduce the typecheck issue locally, do you know what might be causing this kind of discrepancy?

[thymikee]

Yeah, you'll need to add the new @rnef/welcome package to root project.json

[mdjastrzebski]

Looks awesome. I've left some questions about code structure:

1. Why re-export welcome screen from welcome in platform-xxx and then do Platform.select again?
2. I would suggest renamign to @rnef/welcome-screen to make it event more evident that this package can be removed afterwards from the users project.

[jbroma]

Looks awesome. I've left some questions about code structure:

1. Why re-export welcome screen from welcome in platform-xxx and then do Platform.select again?
2. I would suggest renamign to @rnef/welcome-screen to make it event more evident that this package can be removed afterwards from the users project.

1. We don't want users to install @rnef/welcome explicitly, nor we want to add it to the template so ppl need to remove it manually after setup. @rnef/welcome acts as a shared package for universal template, and the template imports it via the platform packages (like suggested in the related issue)
2. Good idea 👍

[mdjastrzebski]

@jbroma how does it work then? I do not see it in any deps except platform-xxx, but these packages are devDeps in deployed template.

[mdjastrzebski]

@thymikee what is the reason #325 suggests to use Platform.select in the main app template? This will break if we do not pick both ios and android platforms.

[jbroma]

@jbroma how does it work then? I do not see it in any deps except platform-xxx, but these packages are devDeps in deployed template.

users have @rnef/platform-ios installed so its taken from there through reexport and internally @rnef/platform-ios has a dependency on @rnef/welcome.

[jbroma]

@thymikee what is the reason #325 suggests to use Platform.select in the main app template? This will break if we do not pick both ios and android platforms.

tbh from the technical perspective it makes more sense to have it explicitly in the projects because @rnef/welcome is a react-native runtime package while @rnef/platform-ios and @rnef/platform-android are meant for Node runtime.

[thymikee]

@thymikee what is the reason #325 suggests to use Platform.select in the main app template? This will break if we do not pick both ios and android platforms.

Ah that's right. Ideas how to make it better?

[mdjastrzebski]

Import from the shared package directly

[jbroma]

@thymikee what is the reason #325 suggests to use Platform.select in the main app template? This will break if we do not pick both ios and android platforms.

Ah that's right. Ideas how to make it better?

Import from the shared package directly

+1

the only reasoning against is that users will have one more explicit dependency in their projects and would need to remove it explicitly after the setup

[mdjastrzebski]

Perfecto 👌

[thymikee]

❤️