[NEXT-888] MetaData title and description will add to body instead head tag

[roshaninet]

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.3.0: Mon Jan 30 20:39:35 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T8103
    Binaries:
      Node: 18.13.0
      npm: 8.19.3
      Yarn: 1.22.19
      pnpm: 7.0.0
    Relevant packages:
      next: 13.2.4-canary.1
      eslint-config-next: 13.2.3
      react: 18.2.0
      react-dom: 18.2.0

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

No response

Link to the code that reproduces this issue

https://stackblitz.com/edit/vercel-next-js-erobcb?file=app%2Fpage.tsx,next.config.js,app%2Flayout.tsx

To Reproduce

default meta data in layout.jsx

export const metadata = {
    title: {
        default: 'خرید و اجاره ویلا در شمال',
        template: '%s | املاک دلاوران',
    },
}

page.js metadata:

export const metadata = {
    description: "گروه مشاورین املاک دلاوران، خریدو فروش ویلا در شمال مازندران",
    alternates: {
        canonical: canonicalLink("")
    }
};

Describe the Bug

meta data export will append tag to body tag instead head tag

Expected Behavior

the meta data must be add to head tag.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

_NEXT-888

[axten]

same here, meta tags from root layout end up in body on index page.
next 13.2.4

[github-actions]

We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate.

Why was this issue marked with the please add a complete reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository (template), but you can also use a tool like CodeSandbox or StackBlitz.

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue.

Please test your reproduction against the latest version of Next.js (next@canary) to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the please add a complete reproduction label that receives no meaningful activity (e.g. new comments with a reproduction link) are automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without reproduction steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues

[Adrianjs42]

I could reproduce the issue after using React.Suspense in the layout.tsx.
@roshaninet do you use React.Suspense in the layout.tsx file, too?

Link to the code that reproduces this issue
https://stackblitz.com/edit/vercel-next-js-erobcb?file=app%2Fpage.tsx,next.config.js,app%2Flayout.tsx

To Reproduce

import type { Metadata } from 'next/types';
import { Suspense } from 'react';

export const metadata: Metadata = {
  title: {
    default: 'Next.js App Router',
    template: '%s | Next.js App Router',
  },
  description:
    'A playground to explore new Next.js App Router features such as nested layouts, instant loading states, streaming, and component level data fetching.',
};

export default function RootLayout({ children }) {
  return (
    <html>
      <head />
      <body>
        <Suspense fallback={<>loading</>}>{children}</Suspense>
      </body>
    </html>
  );
}

Expected Behavior
The metadata should be placed inside of the head tag.

By the way, when you build the app, the metadata is placed correctly in the head tag.

[priyanshuraj24]

+1

[hicodersofficial]

+1

[roshaninet]

@Adrianjs42 No i dont,
i think this problem exists in dynamic metadata (generateMetadata)

[icyJoseph]

Hi,

This happens when you have a loading file, and in general, it seems like the presence of suspense boundaries (<!-- $ -->, <!-- /$ -->) triggers the issue.

Screen.Recording.2023-03-23.at.11.55.29.mov

Verified in: next@13.2.5-canary.14

[roshaninet]

@icyJoseph yes man, the problem is in loading file. i confirm that problem is in loading file.