Catch all segments with both (dynamic/static)

[Androlax2]

Summary

Hi,

Is there any way to have a static generation for X pages and dynamic pages for Y pages.

I’ve this structure right now : app/[[…slugs]]

Where slugs got mapped from the CMS and generated with generateStaticParams.

My current issue is, few pages needs access to the searchParams for instance (or can be any other thing it doesn’t really matter.

When I deploy, all the pages that should have been static are having the CACHE HIT working good, the dynamic one have the CACHE MISS. Expected behavior.

Then I add a new page on the CMS side, CACHE MISS, and CACHE MISS again where this page could be statically generated.

I know there is a export const dynamic = "force-static"

I tried it, but then the dynamic pages get statically generated, but then when I add a page on the CMS first request CACHE MISS, second one CACHE HIT.

is there a way to have a sort of « dual » possibility for the rendering of the page using that sort of catch all segments ?

Additional information

No response

Example

No response

[SametDulger]

Setting export const dynamic = 'force-static' breaks dynamic behavior (no SSR).

Not setting it = everything becomes dynamic unless covered by generateStaticParams.

New CMS pages are rendered dynamically first (CACHE MISS), but never promoted to static unless you re-build.

You want ISR-style promotion: dynamic first, cached on next visit.

Recommendation: Use revalidate with ISR (Incremental Static Regeneration)
Next.js supports hybrid ISR via:

// app/[[...slugs]]/page.tsx
export const dynamicParams = true; // Required to allow dynamic segments not returned by generateStaticParams
export const revalidate = 60; // Revalidate after 60s

export async function generateStaticParams() {
  const cmsPages = await getPagesFromCMS();
  return cmsPages.map((slug) => ({ slugs: slug.split('/') }));
}

This allows:

Static pages from generateStaticParams() to be built at build time.

New pages not in generateStaticParams() to be generated on first request (CACHE MISS), then cached for 60s (CACHE HIT on next visits).

Optional Split: Static Wrapper + Dynamic Handler
If your use case is more nuanced (e.g., exact control over rendering strategy per slug), consider:

Using a middleware to rewrite to:

/static/[[...slugs]] for known slugs (SSG),

/dynamic/[[...slugs]] for others (SSR).

Or maintain an isDynamicRoute(slug) helper from CMS metadata to selectively control logic inside your route.

Important Notes
export const dynamicParams = true is required for Next.js to allow new slugs at runtime.

revalidate acts like ISR — it's a good balance between force-static and force-dynamic.

Pages with searchParams can still be statically rendered; just don’t depend on searchParams at build time.

Experimental: Rendering by condition
While this isn't officially supported, you can conditionally vary behavior at runtime inside your page:

export const revalidate = 60;

export default async function Page({ params, searchParams }) {
  const slug = params.slugs?.join('/') || '';
  const isDynamic = determineIfDynamic(slug); // your custom logic

  if (isDynamic) {
    // SSR-specific logic
  }

  // SSG or common logic
}

Static + dynamic routes --> Use revalidate, not force-*
New CMS pages at runtime --> Set dynamicParams = true
ISR (build-on-demand) --> Use revalidate = X
Search params support --> SSR or allow client-side use
Slug-based logic control --> Custom isDynamicRoute(slug)

[cornedor]

How this be done with cacheComponents enabled? I'm getting the following error, and haven't found any other option yet.

Route segment config "revalidate" is not compatible with `nextConfig.experimental.cacheComponents`. Please remove it.
    ,-[/projectdir/src/app/product/[productSlug]/layout.tsx:13:1]
 10 | }
 11 | 
 12 | export const dynamicParams = true;
 13 | export const revalidate = 60;
    :              ^^^^^^^^^^
 14 | 
 15 | export default async function Layout({
 16 |   children,
    `----
    ```

[d-plz]

@cornedor #82565 (comment) I created this discussion talking about this, have you figured out something else about it? We can centralize the discussion over there and possibly have someone chime-in. I ran into the same error as you and the most I could find is that Nextjs is "standardizing" to export const dynamic = auto, which is what doesn't allow the behavior you want or the on-demand ISR I ask for in the discussion. Which doesn't make sense bc if no dynamic APIs used (headers, cookies, etc) then I believe 'auto' behavior should attempt to cache as mucha as possible including the full route cache.