[NEXT-1207] Default viewport tag not generated for not-found pages.

[josias-r]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:58 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6020
    Binaries:
      Node: 18.15.0
      npm: 9.5.0
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.2
      eslint-config-next: 13.4.2
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4

Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Routing (next/router, next/navigation, next/link)

Link to the code that reproduces this issue

to-reproduce is simple enough :) and codesandbox breaks when I create a not-found.tsx file :(

To Reproduce

1. create-next-app
2. Create a not-found.tsx page
3. Add notFound() to the top of your root page
4. Access / -> default viewport tag is there
5. Access /does-not-exist default viewport tag is missing

Describe the Bug

So far accessing a page /does-not-exist and one triggered by notFound() behave a little differently even though they both render the not-found page.

It looks like a fix for broken Link is on its way. But there is also an issue with the default viewport meta tag that NextJS adds.

When accessing a /does-not-exist that viewport tag is missing, while for a notFound() page, it will be there.

Expected Behavior

The default viewport tag is always added to the page

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

_NEXT-1207

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.