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 404 when no route match at all #426

Merged
merged 3 commits into from
Jun 9, 2024
Merged

Conversation

conico974
Copy link
Collaborator

When a request does not match any route at all, instead of returning the 404 page it returns a 500.
I'm pretty sure it does not happen on every version of next as well, something new that they added at one point.
It's an error in the next request handler itself (it tries to pipe to undefined), they must have moved this logic in the server router.

I need to add some e2e test for this as well.

Copy link

changeset-bot bot commented May 30, 2024

🦋 Changeset detected

Latest commit: 2c177d2

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

This PR includes changesets to release 4 packages
Name Type
open-next Patch
app-pages-router Patch
app-router Patch
tests-unit 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

Copy link

vercel bot commented May 30, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
open-next ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 9, 2024 4:13pm

@conico974 conico974 merged commit a46d3fc into opennextjs:main Jun 9, 2024
3 checks passed
@eschaefer
Copy link

This might have introduced a regression. See #476 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants