-
Notifications
You must be signed in to change notification settings - Fork 86
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
test: pick highest version of react from peerDependencies #2637
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
📊 Package size report No changes
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
pieh
added
the
test all versions
Run e2e tests against old and canary versions of Next.js
label
Oct 1, 2024
pieh
changed the title
test: debug nx integrated canary failures
test: pick highest version of react from peerDependencies
Oct 1, 2024
lukasholzer
approved these changes
Oct 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Because of vercel/next.js#70219 and fact that we use peerDependencies react version when using next@canary for our test setups and fact that
@nx/next
doesn't handle^18.2.0 || 19.0.0-rc-<hash>-<date>
as dependency version well (it throws that this is not valid, tho it is), this picks highest version from^18.2.0 || 19.0.0-rc-<hash>-<date>
and use just that instead of entire string to avoid hitting@nx/next
limitationRef: https://github.com/netlify/next-runtime/actions/runs/11120703643/job/30898239310?pr=2636#step:13:239 example of NX failure with current approach