Allow specifying the RN version in test-turbo-module.sh

[Johennes]

No description provided.

[Johennes]

I've removed the redirection here because it makes the script exit silently on error without any way to find out what went wrong.

As an example, [email protected] cannot generate for [email protected] apparently:

$ ./scripts/test-turbo-modules.sh -r 0.73.0 tm-test
ℹ️  Starting my-test-library
-- Creating library my-test-library with create-react-native-library@latest
ℹ Using [email protected] for the example
⠴ Copying files

The generated example app doesn't have community CLI installed
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

AssertionError [ERR_ASSERTION]: The generated example app doesn't have community CLI installed
    at Object.create [as handler] (/Users/jm/.npm/_npx/e106e660d51959d2/node_modules/create-react-native-library/lib/index.js:557:31) {
  generatedMessage: false,
  code: 'ERR_ASSERTION',
  actual: false,
  expected: true,
  operator: '=='
}

Node.js v18.19.1

[jhugman]

This looks good! What are you going to do with it?

[Johennes]

I wanted to see if I can set up a small test matrix that runs the script on the CI for different RN and builder-bob versions so that we can get some visibility into which combinations currently work and be notified when one of them breaks. Right now I'm basically running into the various externally triggered breakages by coincidence.

Do you think that would be helpful?

[jhugman]

I wanted to see if I can set up a small test matrix that runs the script on the CI for different RN and builder-bob versions so that we can get some visibility into which combinations currently work and be notified when one of them breaks. Right now I'm basically running into the various externally triggered breakages by coincidence.

Do you think that would be helpful?

Getting this to run on CI would be amazing, if nothing else to get that area of the code tested in a more systematic way.

Having an early warning system for breakage based on the shifting sands of RN and CRNL would be super cool.

Would you be triggering this to run every time CRNL makes a release? or daily or something even cleverer?

I do worry that if CRNL breaks our build, that would stop us landing code elsewhere in the project—so I'd likely suggest that these tests trigger if a PR makes changes in the crates/ubrn_cli directory, or the test-turbo-modules.sh file itself.

[Johennes]

I was thinking about nightly for a start just to get a sense of stability and then go from there? Definitely agree that we should limit its impact on PRs given that external factors could break it.