Skip to content

feat: 404 and error pages as inkan answers them - #10

Merged
vxnsin merged 1 commit into
mainfrom
error-pages
Nov 12, 2026
Merged

vxnsin merged 1 commit into
mainfrom
error-pages

Conversation

@vxnsin

@vxnsin vxnsin commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Own pages for everything that goes wrong, instead of Next's defaults.

  • 404 (app/not-found.tsx, also what notFound() in the docs shows): "No route for this one.", the seal stamped on with a small spring, and on the right the answer an inkan app would give, as application/problem+json with the address that was asked for. Below: search the docs (opens the ⌘K dialog), and Docs, Hanko, Blog, Home. Still answers with status 404, noindex.
  • 500 (app/error.tsx): the same layout with nav and footer, "Try again" (reset()), and the digest in the problem so an issue can point at the log.
  • Root failure (app/global-error.tsx): no providers there, so no nav and no search, the rest the same.
  • components/problem-page.tsx holds the shared part.

Checked in the browser on the dev server: /gibt-es-nicht and /docs/does-not-exist answer 404 with the page, desktop dark and mobile light. Typecheck and lint pass.

A problem+json card with the address asked for, the stamp, search and the ways back. error.tsx keeps the nav and offers a retry; global-error.tsx stands on its own.
@vercel

vercel Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
inkan-dev Ready Ready Preview Nov 12, 2026 10:10am UTC

@vxnsin
vxnsin merged commit fd7b164 into main Nov 12, 2026
3 checks passed
@vxnsin
vxnsin deleted the error-pages branch November 12, 2026 10:19

This branch was successfully deployed

1 active deployment
Preview — aea75405 Deployed Nov 12, 2026 by vercel[bot]
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.

1 participant