-
Notifications
You must be signed in to change notification settings - Fork 87
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: adjust setup for next@canary #2553
Conversation
📊 Package size report No changes
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
a5f664f
to
61660d5
Compare
61660d5
to
fd52e17
Compare
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.
This looks good, but I wonder whether we should retain all our Next.js patching in one place because we already do some patching here https://github.com/netlify/next-runtime/blob/main/.github/workflows/test-e2e.yml#L150-L154
This is not for Vercel tests and we do some stuff in this module already to help in our integration test setup which is few lines below hack added in this PR ( https://github.com/netlify/next-runtime/pull/2553/files#diff-2e2db2b91b140546c5f0cdeb8770dbc305ba4a6a525667353b1fe33f2f6b59c6R76-R92 ) |
Description
Ref: https://github.com/netlify/next-runtime/actions/runs/10050411516/job/27778277122?pr=2552#step:12:211 - attempting to fix tests setup for next@canary
Documentation
Tests
You can test this change yourself like so:
Relevant links (GitHub issues, etc.) or a picture of cute animal