`next/head` is applied in App Router routes

Open Beginner friendly
  • Is something wrong?
#4,589 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
next.js, typescript, vite
Domain
frontend

Research direction

Start by tracing how vinext handles next/head in App Router routes and compare it with Next.js behavior, where route titles come from metadata. The issue gives no file or test path, so locate the shared client layout behavior and relevant head or metadata tests. Done means next/head no longer overrides App Router metadata titles while Pages Router titles still work.

Written by the indexing model from the issue text.

Description

Next ignores next/head in the App Router, where titles come from metadata. vinext applies it. We have a client layout shared by both routers that renders <Head><title> for the Pages Router pages, and under vinext it also overrides the metadata title of every App Router route that uses the layout.

Dominant language
TypeScript
Stars
9.3k
Forks
463
Avg merge
22h 22m
Merged PRs (30d)
502

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudflare/vinext

All issues in cloudflare/vinext

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.