fix: update worklets exclude to drop version

[frankcalise]

Description

There's an issue when providing the version in the expo.install.excludes keys, which might be related to the -nightly suffix as it doesn't fall into some of the prerelease tags (not 100% on this).

Looking at the docs, it seems like they may have migrated away from providing the specific version in the key anyway? This doesn't match with Expo's test cases on the matter, but it is what the docs say now.

• Closes Multiple issues in fresh Ignite CLI project: dependency conflict and missing ErrorBoundary component #3000

In addition to this, I updated the expo-router version we slide into the template from the new command. This wasn't required, as expo install --fix actually would have fixed it anyway, should the worklets install would have actually been excluded.

Screenshots

Before terminal output

Note how it says it is skipping them, but it still lists it as a version it is going to update with install --check

npx expo install --check
Skipped checking dependencies: react-native-worklets@0.7.0-nightly-20251001-14eca5b4c. These dependencies are listed in expo.install.exclude in package.json. Learn more: https://docs.expo.dev/more/expo-cli/#configuring-dependency-validation
The following packages should be updated for best compatibility with the installed expo version:
  expo-router@5.0.7 - expected version: ~6.0.10
  react-native-worklets@0.7.0-nightly-20251001-14eca5b4c - expected version: 0.5.1
Your project may not work correctly until you install the expected versions of the packages.
? Fix dependencies? › (Y/n)

After terminal output

Then, when dropping the version from package.json:

npx expo install --check
Skipped checking dependencies: react-native-worklets@0.7.0-nightly-20251001-14eca5b4c. These dependencies are listed in expo.install.exclude in package.json. Learn more: https://docs.expo.dev/more/expo-cli/#configuring-dependency-validation
The following packages should be updated for best compatibility with the installed expo version:
  expo-router@5.0.7 - expected version: ~6.0.10
Your project may not work correctly until you install the expected versions of the packages.
? Fix dependencies? › (Y/n)

[coolsoftwaretyler]

LGTM! Thanks for fixing this and sorry I missed it. I had already re-ignited locally and only tested the install, not the new command correctly.

[frankcalise]

@coolsoftwaretyler all good, I would have expected it to work the way you constructed it. It certainly used to work that way