Support dynamic routes (with dynamic params) in static export mode #55393
Replies: 44 comments 98 replies
-
|
Our project is private (don't care about SEO) and already has a back-end server, so there's no point in having server-side rendering and in turn, no need to use a node server. But we handle a lot of dynamic data so I'm highly interested in this |
Beta Was this translation helpful? Give feedback.
-
|
Exactly! If you've got a backend setup and aren't fussed about SEO, then the whole SSR shebang might not be for you. What you're highlighting is exactly why this feature is so key in many applications. Dynamic data shouldn't be a hassle, even in static deployments. Hope this gets the consideration it deserves. Really holding next back as “the react framework”. |
Beta Was this translation helpful? Give feedback.
-
|
@VakarisZ I don't know if you still need this, or if you solved this a different way, we had a golang server serving the static files, and I was able to do a workaround, see this |
Beta Was this translation helpful? Give feedback.
-
|
See issue 54393 |
Beta Was this translation helpful? Give feedback.
-
|
They changed the issue into a discussion #64660 🫤. |
Beta Was this translation helpful? Give feedback.
-
|
I think this is already planned because App Router is supposed to have the same capabilities as the Pages Router (or at least propose alternate patterns), just not the biggest priority |
Beta Was this translation helpful? Give feedback.
-
|
I wish I knew this before going in on app routers, guess I have a big re-refactor ahead of me |
Beta Was this translation helpful? Give feedback.
-
|
A planned feature but in the app router docs it describes this as being possible now? https://nextjs.org/docs/app/building-your-application/deploying/static-exports Definitely frustrating especially when you've used this in pages in the past and tried app router expecting similar functionality. |
Beta Was this translation helpful? Give feedback.
-
|
It states:
So no, it's not supported yet and the docs say it's not supported either. |
Beta Was this translation helpful? Give feedback.
-
|
THis one is very important to me as I use nextjs with Capacitor to generate iOS and Android apps. In those cases I export dynamic route pages that need to do remote requests (such as /user/[id]). My current work arounds would be to either use query params (/user?id=blah) or go back to the pages routing. edit: actually query params won't work as the builder still wants to turn it into a static html, so I can only go back to pages I guess... |
Beta Was this translation helpful? Give feedback.
-
|
if dynamic page has child route, query params make sad |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for addressing this problem. I see another significant issue in that – memory overload. There should be the possibility to handle dynamic routes with client-side fetching. Without that option, on large platforms, users would have to download 'gigabytes', with the number growing every day, instead of megabytes from the App Store. Additionally, each new entry force users to update the app to prevent encountering 404 errors. |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone! Cross-posting myself from #54393 (comment) so I can get notified about any kind of development in this regard:
Any news of any kind about this? |
Beta Was this translation helpful? Give feedback.
-
|
hi everyone, guys i am looking for solution for two days , i started thinking to change framework , i have tried everything `"use client"; function Lang({ params }: { params: any} ) { const {sleep, handleSubmitAttribute,object, objectxsById, deleteAttribute, setCurrentLang, attributexs, setAttributes, attributes, user } = useAuth({ middleware: "Guest" }); } // Callback function to receive data from the child }; const onSubmit = async (e: any) => { ); } else { } } const saveX=()=>{ return ( ); export default Lang; that is the error `
|
Beta Was this translation helpful? Give feedback.
-
|
Any update on this? |
Beta Was this translation helpful? Give feedback.
-
|
no |
Beta Was this translation helpful? Give feedback.
-
|
🤚 I also am in the boat of needing this -- I need to do I don't work at Vercel, but sadly, I don't see any way this is technically feasible. The output of static builds are individual files. Without knowing the value of individual paths in the data beforehand, Next won't know what paths to create. You could create a system in the framework that generates a You'd have to plug into AWS Route 53 and Cloudfront and wherever else is modifying that request, and have them all account for this logic, and then do that on every hosting provider separately. 😞 I just don't see a way for this to happen. The alternative is to compromise, and turn your dynamic links into URL parameters (which is what I'll have to do). Then, when I export my content, the client side javascript will still be able to pick those values up and use them the way I need. It stinks, but I really don't see any other way. |
Beta Was this translation helpful? Give feedback.
-
|
The |
Beta Was this translation helpful? Give feedback.
-
|
Almost every other routing implementation around supports hash routing, which is typically how you get around this constraint. |
Beta Was this translation helpful? Give feedback.
-
|
This is exactly what I need. In my situation, I'll never use node as backend for anything outside of generating a particular subset(the next app) of a much larger codebase. Our backend is designed for high performance and is entirely written in Rust and entirely consumed via API, mostly via our primary Angular Client, but we have some e-commerce elements we choose to use React/Next for. I'd like to be able to build static pages of existing known content at some specific interval in our deployment process and have our application still seamlessly handle scenarios where those static pages do not exist, etc. There will potentially be tens thousands of those pre-rendered static pages, and hundreds of new additions every day. Deployment directly to CDN is part of our strategy for things like this. Ultimately it seems impossible to use next(app router) to achieve these results, but perhaps our intended use case doesn't fit into vercel's business case. |
Beta Was this translation helpful? Give feedback.
-
|
would it be supported at least? |
Beta Was this translation helpful? Give feedback.
-
|
You need to use 'pages' to have dynamic routes while using static gen + app router. Sort of silly this error cant be overidden |
Beta Was this translation helpful? Give feedback.
-
|
This is a crucial feature. I don't understand why it hasn't been built yet. Especially since it seems pretty straight forward to build. |
Beta Was this translation helpful? Give feedback.
-
|
Wise words, I still have a bad feeling that it is somehow intentional |
Beta Was this translation helpful? Give feedback.
-
|
Yup I have the same feeling... |
Beta Was this translation helpful? Give feedback.
-
|
have some update on this? |
Beta Was this translation helpful? Give feedback.
-
You need to use 'pages' to have dynamic routes while using static gen + app router. |
Beta Was this translation helpful? Give feedback.
-
|
It is quite embarrassing that such a widely adopted framework doesn't support for dynamic routes on client side. For now we are working with parameters in the query string, which is very far from ideal. |
Beta Was this translation helpful? Give feedback.
-
|
There is Open NextJS. Maybe we can borrow from React Router V7 (RSC) or TanStack Router to implement sample template/boilerplate, if get popular it might get as close as Standard. One thing I feel in React Industry is the standard either is shooting themselves in their leg (Next.js) else is always still "new but not fully feature" |
Beta Was this translation helpful? Give feedback.
-
|
This is clearly enshittification. I'm not sure if it's intentional or just selected-for (e.g. deprioritization of this bug in backlog grooming,) but either way, the result is the same. → Vercel is experiencing a conflict-of-interest. On one hand, it maintains an open source package that is now the de facto way of producing React apps; → On the other, it profits from a hosting business; → For some reason, there is a mysterious and undocumented limitation when using NextJS in the only way that does not require hosting. Vercel, please don't be this way! I fought and advocated for your solutions, and now my own credibility is damaged, as we scramble to move from an S3-backed scenario to one that can do dynamic parameters (a feature which, by the way, has been supported in react-router since the Obama administration). There's still time to fix this, though, and this very-downthread comment on a GH discussion is your warning; I'm old enough to have seen firsthand how reputational consequences can salt the earth for a startup. I'm sorry this warning isn't larger, because I agree that the, ah, 'Business Experience' (BX?) of receiving an important warning in this way is not great. Yet I am powerless to do more. You're not powerless, though! |
Beta Was this translation helpful? Give feedback.
-
|
I switched to the Pages router. But this is dumb, and almost certainly an intentional business decision. It's unsurprising, however. Fortunately, most of our work in Next/React is decoupled in a manner that was very easy to move to Pages Router, but is less ergonomic than App Router. And, for the last 5 years, 100% of the backend work I do is in Rust and 95% on the frontend is in Angular, so we don't have a lot of dependencies on Next. I don't think I would consider Next again for a future project, howeve,r given this and other issues I've run into building out this particular tool. React is great though. |
Beta Was this translation helpful? Give feedback.
-
|
@chriskyndrid curious to hear how you got dynamic routes working with pages router? We tried setting fallback: true with |
Beta Was this translation helpful? Give feedback.
-
|
@zdenham I believe, if memory serves, that fallback: true has an internal requirement related to SSR which is incompatible with SSG (output: export). Although the only thing we use "SSR" for is the generation of the SSG pages, you need to be deployed on a node server for fallback to work. As I mentioned in my other post, the solution I rolled can't do anything about endpoints that don't exist at the time of SSG. This is because you need a server to deal with essentially what would otherwise be a 401 (hence fallback: true), to generate a server fetched "static" variant of the page. In my case that's not an option because 1: I don't plan or desire to use node for anything in production. 2: we deploy to a CDN and obviously have limited control over a 401 scenario. I've thought about potentially creating a custom 401 page that would, provided suitable information in the URL exists, manually deal with those scenarios(but I would be unable to instruct the CDN server to return something other than 401, but could perform a client side redirect to a param based page). In any case, all of the "fallback" code I implemented to allow our app to work was done manually. I constructed the components to accept static arguments from build time for the initial page loads and to (useEffect()) issue a call manually to freshen the data. This addresses the SEO situation(with an inherent lag), initial load times, but still ensures we maintain current information. I then have some tricks in place to deal with the legitimate removals of statically generated pages that have since been removed, along with determining client-side if we can route to a dynamic(static) route, or if we need to route to the component with a query param(e.g. issuing a HEAD request via axios after intercepting the navigation request). I couldn't think of another way to accomplish this when CDN was the target and the data was changing frequently. |
Beta Was this translation helpful? Give feedback.
-
|
I see, cache invalidations when data is removed sounds tricky as well. The way we are looking to address it is with a custom cloudfront edge function to properly re-route to the static file when they don't exist. |
Beta Was this translation helpful? Give feedback.
-
|
In my case I'm not super worried about that. As in those scenarios there will be a static page already backing the missing resource. In our scenario, the user will be greeted with a nice "This resource is no longer available", with some options on how to proceed. Once the regen happens it'll result in a 404, which is roughly every 24 hours. I should also mentioned I've written some logic to purge dropped resources as part of the deployment process... |
Beta Was this translation helpful? Give feedback.
-
|
I'd love for a solution to this. judging by how recent the comments are there has been no progress... |
Beta Was this translation helpful? Give feedback.
-
|
Why cant you just use the pages router along side app? |
Beta Was this translation helpful? Give feedback.
-
Why would someone want to use something outdated that is getting deprecated soon? |
Beta Was this translation helpful? Give feedback.
-
A solution is better than none. Are you really missing out on that much? Maybe im ignorant but its just a router at the end of the day... |
Beta Was this translation helpful? Give feedback.
-
|
That's not a solution, that's only a workaround. A real solution is needed. |
Beta Was this translation helpful? Give feedback.
-
|
I wonder why this feature is not yet implemented, I have built a mighty project around next Js only to get stucked here... I wish it can be addressed with immediate effect. |
Beta Was this translation helpful? Give feedback.
-
|
i just did a massive refactor to use the app router, and run into this after I thought it was done. seriously should be hiilghted in red flashing letters in the docs. |
Beta Was this translation helpful? Give feedback.
-
|
I've found another workaround, though it's quite a dirty hack.
So far I've only tried this on a couple pages so I can't say if it's production-ready, but it seems to be a good enough stopgap until my project can be migrated to a Next server. Here's the patch I use with patch-package: diff --git a/node_modules/next/dist/build/index.js b/node_modules/next/dist/build/index.js
index 4cb5619..6718515 100644
--- a/node_modules/next/dist/build/index.js
+++ b/node_modules/next/dist/build/index.js
@@ -1294,7 +1294,7 @@ async function build(dir, reactProductionProfiling = false, debugOutput = false,
if (appConfig.revalidate !== 0) {
const hasGenerateStaticParams = workerResult.prerenderedRoutes && workerResult.prerenderedRoutes.length > 0;
if (config.output === 'export' && isDynamic && !hasGenerateStaticParams) {
- throw new Error(`Page "${page}" is missing "generateStaticParams()" so it cannot be used with "output: export" config.`);
+ // throw new Error(`Page "${page}" is missing "generateStaticParams()" so it cannot be used with "output: export" config.`);
}
// Mark the app as static if:
// - It has no dynamic param
diff --git a/node_modules/next/dist/esm/build/index.js b/node_modules/next/dist/esm/build/index.js
index 49ef6e4..146e9ea 100644
--- a/node_modules/next/dist/esm/build/index.js
+++ b/node_modules/next/dist/esm/build/index.js
@@ -1226,7 +1226,7 @@ export default async function build(dir, reactProductionProfiling = false, debug
if (appConfig.revalidate !== 0) {
const hasGenerateStaticParams = workerResult.prerenderedRoutes && workerResult.prerenderedRoutes.length > 0;
if (config.output === 'export' && isDynamic && !hasGenerateStaticParams) {
- throw new Error(`Page "${page}" is missing "generateStaticParams()" so it cannot be used with "output: export" config.`);
+ // throw new Error(`Page "${page}" is missing "generateStaticParams()" so it cannot be used with "output: export" config.`);
}
// Mark the app as static if:
// - It has no dynamic param |
Beta Was this translation helpful? Give feedback.
-
|
Fantastic work! This workaround seems not working for |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
OMG I just came up with a hack to fix refreshing the page in the static export on a dynamic route going to 404! pages/404.tsx import { useRouter } from "next/router"
import { useEffect } from "react"
export default function Custom404() {
const router = useRouter()
useEffect(() => {
if (router.pathname.includes("[") && router.pathname.includes("]")) {
router.replace(router.asPath)
}
}, [router])
} |
Beta Was this translation helpful? Give feedback.
-
|
Okay I found a solution for using Dynamic Routes in App Router with output: "export" Works great! First off, create your dynamic page, in this case it will be "post" /app/post/page.tsx"use client"
import { usePathname } from "next/navigation"
export default function PostPage() {
const pathname = usePathname()
const postId = pathname.split('/').pop()
return (
<div>
<h1>Post ID: {postId}</h1>
</div>
)
}Next, link to it from any other page... /app/page.tsx"use client"
import Link from "next/link"
export default function IndexPage() {
return (
<div>
<p>
<Link href="/post/1">
Post 1
</Link>
</p>
<p>
<Link href="/post/2">
Post 2
</Link>
</p>
</div>
)
}Now the kicker, to make these /post/1 and post/2 links actually work! /app/not-found.tsx"use client"
import PostPage from "@/app/post/page"
import { usePathname } from "next/navigation"
export default function NotFound() {
const pathname = usePathname()
if (pathname.includes("/post/")) {
return <PostPage />
}
}Voila, dynamic routes for Next.js App Router using output: "export" |
Beta Was this translation helpful? Give feedback.
-
|
@tresorama I tried what you told using react router ,but it will not route when we refresh , can you please give link to video you referred since its blocker for me .I am not concerned about the SEO or anything just need to put in CDN . Please let me know if you found out anything . I tried like this [[...slug]].tsx |
Beta Was this translation helpful? Give feedback.
-
|
In this video https://youtu.be/bIr7NtNRDmE?si=qPYay5Xi3vYPzc7p The key part begins at 3:00 |
Beta Was this translation helpful? Give feedback.
-
This works pretty well but I am stuck with another problem where I am having a subroute inside the dynamic path param eg: /post/post-1/review when I am building the app using export the build route has /post/default/review.txt & review.html files Do you have any solution for this or can you suggest some way to achieve this? |
Beta Was this translation helpful? Give feedback.
-
|
Oh man we'll probably need to customize the function more to handle sub routes. I'm working on some other Better Auth related projects right now and I'm planning to loop around back to this -- but I'm also waiting for Next.js 15.4.0 before going too much further in the weeds here, just in case there are some breaking changes or solutions there. They'll probably release it by Vercel Ship in June? I'll be making this an npm package though for super simple setup at that point |
Beta Was this translation helpful? Give feedback.
-
|
Okay |
Beta Was this translation helpful? Give feedback.
-
|
I couldn't believe such a fundamental feature is not implemented in 2025. Massive projects just need several pages statically generated (like landing page, about-us) for SEO, and other business logical pages be client-side rendered. These CSR pages of course require dynamic routes that users can visit pages like It seems Vercel is heavily focused on promoting server-side rendering to drive hosting on their platform, deprioritizing other features. Given this, I advise caution when choosing Next.js, as its future appears to align more with Vercel's business goals than user needs. |
Beta Was this translation helpful? Give feedback.
-
|
Dude, I don't believe it either. Did you find a solution? I'll have to look for another framework that does this. I want to use a framework for SSR and SPA for certain routes, have static files and paste them wherever I want. I don't want to have a node server running in production. |
Beta Was this translation helpful? Give feedback.
-
|
Try react-router which meets our expectation exactly. SPA with dynamic routing and several pages statically generated. I'm feeling nextjs is too heavy and is doing to many things that frontend frameworks are not supposed to do. |
Beta Was this translation helpful? Give feedback.
-
|
Any ideas for i18n on React Router v7? What about SSR for dynamic routes? I create hybrid applications and I want SSR dynamic routes for SEO when deployed to production and static export for Capacitor. I'm using some crazy hacks to get it working with Next.js, and it does.. but... messy |
Beta Was this translation helpful? Give feedback.
-
React-router supports SSR with dynamic routes. |
Beta Was this translation helpful? Give feedback.
-
|
Did whole refactor of a massive repository and came to this . I am still thinking my choices in my bathtub https://www.youtube.com/watch?v=i82528KGDdo Hope vercel solves this |
Beta Was this translation helpful? Give feedback.
-
|
It took 3 major releases for work to get started on this feature so I wouldn’t hold my breath on it being finished soon |
Beta Was this translation helpful? Give feedback.
-
|
Unlike others in this thread, I don't have tons of code to refactor, as I only started NextJS a few days ago. I'm developing an all-static site. There are many reasons not to use the Node server. One being that you just want a simple app that fetches from an already existing API. Why in the world would I run an extra server just for the page to be able to interpret a /profile/[username] type URL? Everything else works fine with "use client" in all my components. I really didn't need (or thought I needed) anything fancy. I concur with all those who said:
Thanks in advance for plugging this gaping hole in functionality for us exported, fully static mortals. |
Beta Was this translation helpful? Give feedback.
-
|
The cleanest and simplest solution is to use searchParams. I gave up using dynamic routes. Search params aren't bad.: "use client";
import { useSearchParams } from "next/navigation";
export default function UserDetail() {
const searchParams = useSearchParams();
return <div>test: {searchParams.get("userId")}</div>;
} |
Beta Was this translation helpful? Give feedback.
-
|
It does look like the team has started the implementation to support this! Hopefully in 5.3 🤞🏻 |
Beta Was this translation helpful? Give feedback.
-
|
It's been 4 months since this comment :( I don't even know if they plan to ship it in 15.4 |
Beta Was this translation helpful? Give feedback.
-
|
So I spent the last few days working around this. I am hosting on Cloudflare pages and their nextjs support is abysmal; so I decided to go fully static instead of relying on another hosting provider. I created a kind of a plugin that leverages The only remaining issue I have is page transitions. Since you'll be hitting a not-found path, this breaks hydration. Essentially, you'll be loading each page separately. Theoretically, this shouldn't be the case (the page itself is loaded dynamically inside the error page). If someone has ideas on this or willing to work further on it, please share or shot me an email. |
Beta Was this translation helpful? Give feedback.
-
|
I faced the same limitation and tried to solve it by creating a custom SPA-style router on top of the App Router, without using [id] folders or generateStaticParams().
All routes are defined in a withRouteHandler() wrapper that:
Result:
🔗 Code: github.com/tushar1866/next-admin Note: Since it’s fully static, you can't deep-link directly via browser (e.g. /posts/1)(Under Development) — that leads to a 404. You must use the useSPARoute().navigate() method to change routes internally. For auth check this https://dummyjson.com/docs/auth Hope this helps others trying to keep static builds without sacrificing routing flexibility! |
Beta Was this translation helpful? Give feedback.
-
|
Any updates? |
Beta Was this translation helpful? Give feedback.
-
|
@feedthejim so many people dream about times when app router will be finally production ready |
Beta Was this translation helpful? Give feedback.
-
|
Will this even be supported in Nextjs 16? |
Beta Was this translation helpful? Give feedback.
-
|
Hopefully this helps somebody, I couldn't find anybody doing something like this and wanted to avoid the 404 workaround for SEO reasons. Because I'm converting an existing website to SSG and need to keep urls as they are and I don't need all paths to have dynamic params I'm using rewrites as a workaround. That way the urls stay the same xxx.abc/test/123 but with the rewrite from /test/123 to /test/?slug=123 it hits page.tsx with the search param. For local dev I do. async rewrites() {
return {
'beforeFiles': [
{
source: '/test/:slug',
destination: '/test/?slug=:slug',
},
]
}
}and my lambda@edge looks something like this const routes = [
{
pattern: "/test/:slug",
rewriteUri: "/test/"
},
];
function toRegex(pattern) {
const keys = [];
const regex = pattern.replace(/:([^/]+)/g, (_, key) => {
keys.push(key);
return "([^/]+)";
});
return { regex: new RegExp("^" + regex + "$"), keys };
}
const compiled = routes.map(r => ({ ...r, ...toRegex(r.pattern) }));
export const handler = async (event) => {
const request = event?.Records?.[0]?.cf?.request;
const uri = request?.uri;
for (const { regex, keys, rewriteUri } of compiled) {
const match = uri?.match(regex);
if (match) {
request.uri = rewriteUri;
const params = keys.map((k, i) => `${k}=${match[i + 1]}`).join("&");
request.querystring = request.querystring
? `${params}&${request.querystring}`
: params;
break;
}
}
return request;
};I change my folder structure from to page.tsx looks like export default async function Page() {
return (
<Suspense fallback={<LoadingSkeleton />}>
<PageClient />
</Suspense>
);
}page-client.tsx 'use client';
export default function PageClient() {
const searchParams = useSearchParams();
const pathname = usePathname();
const [slug, setSlug] = useState<string | null>(null);
useEffect(() => {
const fromParams = searchParams.get('slug');
if (fromParams) {
setSlug(fromParams);
} else {
const match = pathname.match(/^\/[^/]+\/([^/]+)\/?$/);
setSlug(match?.[1] || null);
}
}, [searchParams]);
return slug ? (
<SlugClient slug={slug} />
) : (
<div> Original page.tsx content <div/>
);
}And then in SlugClient I use swr to fetch required data. In some places I feed in prefetched data during the page.tsx build and use it as fallback data with swr suspense. |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
Feature Request: Support Dynamic Routes with Dynamic Params in Static Export Mode
Current Behavior
Right now, when we use the
{ output: 'export' }option to statically pre-generate the app to run without a Node server, we hit a roadblock: dynamic routes like/post/[id]just can't be created. Yes, we can pre-generate specific pages such as/posts/1,/posts/2,/posts/3, and so on, but if we encounter values not known at build time, we are met with a 404 error. This is quite the hiccup for scenarios demanding static deployment coupled with dynamic data capabilities.Desired Behavior
We're looking to get dynamic routes with variable parameters up and running in static export mode. The vision is to have routes like
/post/[id]operate without a hitch, avoiding the dreaded 404 error when the ID parameter changes, and allowing individual posts to be fetched client-side. This change would significantly broaden the scope and usefulness of static exports.Non-Goals
What This Feature Request Does Not Aim to Address
Background
Benefits
Flexibility: This feature would open doors for developers to exploit dynamic routes while still enjoying the perks of static export functionalities.
Honoring the Next.js Slogan: Let's make the Next.js slogan "The React Framework" ring true by covering a common SPA use case currently left out in the cold.
Potential Drawbacks
Complexity: While this looks promising, introducing dynamic parameters in static export mode might complicate route management a bit.
Alternatives Considered
Sticking with Static Paths: This option, albeit simpler, severely limits the dynamic functionalities, which are pretty much essential in modern web applications.
Switching to a Different Router: Though this sidesteps some Next.js framework limitations, it comes at the cost of losing many of its benefits and makes the transition between a static site and an SSR application a labor-intensive task.
Additional Context
Embracing dynamic parameters in static export mode would effectively bridge the existing gap between dynamic functionalities and static deployments, offering a flexible and robust solution for developers navigating strict deployment environments.
Proposal
Proposed Solution
Client-Side Rendering (CSR) Enhancements: Let's amp up CSR to facilitate dynamic data fetching based on the dynamic parameters present in the URL — all possible through
useParams()or parameters relayed to the layout and page components. This isn't uncharted territory; it aligns well with the existing functionalities seen withuseSearchParams()in client components.Route Fallback Support: Introducing a fallback support system for dynamic routes in static export mode could be a game-changer. This means instead of getting a 404 error, users would land on a predefined fallback page, allowing for the client-side fetching of dynamic parameter data.
Beta Was this translation helpful? Give feedback.
All reactions