App Router DX Problem: Can't export metadata from layout using Redux or UI wrappers
#82434
-
🧩 Problem SummaryIn Next.js 15 (App Router), I'm unable to use 🧱 Setup
/app/layout.js:
import ScrollToTopButton from "@/components/ui/ScrollBottomToTop";
import { Comfortaa, Inter, Montserrat } from "next/font/google";
import localFont from "next/font/local";
import { Toaster } from "react-hot-toast";
import "./globals.css";
import StoreProvider from "./storeProvider";
export const montserrat = Montserrat({
weight: ["400", "500", "600", "700"],
style: ["normal"],
subsets: ["latin"],
display: "swap",
});
export const inter = Inter({
weight: ["400", "500", "600", "700"],
style: ["normal"],
subsets: ["latin"],
display: "swap",
});
export const comforta = Comfortaa({
weight: ["400", "500", "600", "700"],
style: ["normal"],
subsets: ["latin"],
display: "swap",
});
export const gothic = localFont({
src: "../fonts/MyFont/centurygothic.ttf",
display: "swap",
variable: "--font-gothic",
});
export const metadata = {
title: "Hello Title",
description: "Hello Description",
};
export default function RootLayout({ children }) {
return (
<html lang="en">
<body className={montserrat.className}>
<StoreProvider>
<Toaster />
{children}
<ScrollToTopButton />
</StoreProvider>
</body>
</html>
);
}/app/StoreProvider.js:
"use client";
import { Provider } from "react-redux";
import { store } from "../redux/store";
export default function StoreProvider({ children }) {
return <Provider store={store}>{children}</Provider>;
}⭕ issues:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
|
Why do you have |
Beta Was this translation helpful? Give feedback.
-
|
And I guess that ends up being under a The recommendation for this kind of pattern is to move the fonts to their own module - I think. Could you share more of the Error stack if possible? I feel like it should say more about the import trace. |
Beta Was this translation helpful? Give feedback.
-
Thank you! I do have a repository, but due to commercial security policies and restrictions on my workstation, I’m unable to share it publicly. Let me know if I can help reproduce the issue in another way. |
Beta Was this translation helpful? Give feedback.
-
You're absolutely right — I think I understand the issue clearly now. Your suggestion about moving the fonts to their own module makes sense, and I’ll give that a try and update here once I test it out. As for the error stack, unfortunately that’s all I’m seeing — it doesn’t provide any more details beyond what I shared earlier. Thanks again for the guidance! |
Beta Was this translation helpful? Give feedback.
-
|
Well it has to be the fonts. When I export a font and import it into a 
Notice the error stack, I guess your version doesn't have that much detail, this was made with If you had used Typescript, this wouldn't even build (before having metadata in layout), because layout and pages, are type checked for their exports - only a limited set of APIs can be exported from these files. You shouldn't really be sharing exports from layout/pages into other modules. |
Beta Was this translation helpful? Give feedback.
-
Thank you so much! |
Beta Was this translation helpful? Give feedback.
Well it has to be the fonts. When I export a font and import it into a
use clientmodule, directly or indirectly, I get:Notice the error stack, I guess your version doesn't have that much detail, this was made with
15.4.5If you had used Typescript, this wouldn't even build (before having metadata in layout), because layout and pages, are type checked for their exports - only a limited set of APIs can be exported from these files. You shouldn't really be sharing exports from layout/pages into other modules.