[RFC] Override `start` command in `react-native.config.js` about repack

[RafikiTiki]

Let's do this! If someone uses a sophisticated setup (i.e. Metro for dev, webpack for prod) I'd say they'll know how to set it up properly with Repack switch to being the default. For the rest of the users, it would save them time spent on figuring out why Metro was started instead of webpack.

Easing the new tool friction is always good 🚀

[thymikee]

As long as we document how to fall back to previous behavior, or expose metro's start command, I'm good with moving forward with this 👍🏼

[tom-sherman]

Massively in favour of this default.

I think 90% of developers onboarded hit an issue where they somehow manage to trigger metro.

[szymonrybczak]

cc @jbroma @tom-sherman @thymikee

[github-actions]

This issue has been marked as stale because it has been inactive for 30 days. Please update this issue or it will be automatically closed in 14 days.

[jbroma]

@szymonrybczak

I gave it some thought and I think this will be a good way going forward, this will reduce the overhead when migrating from metro and avoid some silly mistakes on users part. It's also worth noting that we the commands used in Re.Pack are aligned to that of metro so the change so it should be relatively smooth to add. If somebody uses metro fro development and Re.Pack for production, it can still manually adjusted in react-native.config.js.

This is quite a big change and definitely breaking so I'm adding an RFC to the title, and hope to gain more opinion on this matter.

[jbroma]

@RafikiTiki @thymikee @tom-sherman some insights from you would be great