-
Notifications
You must be signed in to change notification settings - Fork 1.5k
fix: update worklets exclude to drop version #3001
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
coolsoftwaretyler
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
|
@coolsoftwaretyler all good, I would have expected it to work the way you constructed it. It certainly used to work that way |
|
After some manual testing, I have to put back |
coolsoftwaretyler
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, some day we'll evolve past legacy peer deps :(
## [11.2.1](v11.2.0...v11.2.1) (2025-10-06) ### Bug Fixes * **boilerplate:** update worklets exclude to drop version ([#3001](#3001) by [@frankcalise](https://github.com/frankcalise)) ([3e8c37e](3e8c37e))
|
🎉 This PR is included in version 11.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
## [11.2.1](infinitered/ignite@v11.2.0...v11.2.1) (2025-10-06) ### Bug Fixes * **boilerplate:** update worklets exclude to drop version ([infinitered#3001](infinitered#3001) by [@frankcalise](https://github.com/frankcalise)) ([3e8c37e](infinitered@3e8c37e))
Description
There's an issue when providing the version in the
expo.install.excludeskeys, 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.
In addition to this, I updated the
expo-routerversion we slide into the template from the new command. This wasn't required, asexpo install --fixactually 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 --checkAfter terminal output
Then, when dropping the version from package.json: