-
Notifications
You must be signed in to change notification settings - Fork 93
test: adjust assertions for /_not-found being possibly added to prerender manifest #3043
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
📊 Package size report No changes
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
cc027d0
to
26a1fc4
Compare
export function shouldHaveAppRouterNotFoundInPrerenderManifest() { | ||
// https://github.com/vercel/next.js/pull/82199 | ||
|
||
// The canary versions are out of band, as there stable/latest patch versions higher than base of canary versions | ||
// and change was not backported to stable versions | ||
return nextVersionSatisfies('>=15.4.2-canary.33') && isNextCanary() | ||
} | ||
|
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 is really annoying and frankly bad check that will likely need to be adjusted once that change is released in stable, but to me it feels better than doing some kind of filtering in tests themselves. At least it will be somewhat explicit of what full list of generated blobs are (...depending on next version :/ )
Description
To account for vercel/next.js#82199
Documentation
Tests
You can test this change yourself like so:
Relevant links (GitHub issues, etc.) or a picture of cute animal