Skip to content
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

Fix missing .rsc outputs for pages prerenders #11503

Merged
merged 13 commits into from Apr 30, 2024
Merged

Conversation

ijjk
Copy link
Member

@ijjk ijjk commented Apr 26, 2024

When generating the outputs for pages when app router is also present we weren't creating the placeholder .rsc outputs for all prerender outputs so when a fallback: false route was configured in the pages router that could fall through to an app route it causes issues with client-navigation behaving differently than a direct visit.

This ensures we add the placeholder .rsc outputs for all prerenders so that fallback: false pages don't have this unexpected behavior.

Copy link

changeset-bot bot commented Apr 26, 2024

🦋 Changeset detected

Latest commit: c636108

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@vercel/next Patch
vercel Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@ijjk ijjk added the pr: automerge Automatically merge the PR when checks pass label Apr 30, 2024
ijjk added a commit that referenced this pull request Apr 30, 2024
Noticed in #11503 that this test
fixture is incorrectly locked to a specific version when we don't want
it to be.
@kodiakhq kodiakhq bot merged commit 52e435a into main Apr 30, 2024
110 of 112 checks passed
@kodiakhq kodiakhq bot deleted the ijjk/fix-fallback-false-rsc branch April 30, 2024 20:34
TooTallNate pushed a commit that referenced this pull request May 3, 2024
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## vercel@34.1.8

### Patch Changes

- Updated dependencies
\[[`52e435aa5`](52e435a),
[`124846a3e`](124846a),
[`dc974b679`](dc974b6),
[`58c6755e0`](58c6755)]:
    -   @vercel/next@4.2.7
    -   @vercel/static-build@2.5.3

## @vercel/next@4.2.7

### Patch Changes

- Fix missing .rsc outputs for pages prerenders
([#11503](#11503))

- Fix base path app index RSC handling
([#11528](#11528))

- Fix interception routes PPR route handling
([#11527](#11527))

## @vercel/static-build@2.5.3

### Patch Changes

- Support Ruby and Python static site generators in AL2023 build image
([#11529](#11529))

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr: automerge Automatically merge the PR when checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants