Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sitemap rendering broken on NextJS 15 with edge runtime #75174

Open
isaacrowntree opened this issue Jan 22, 2025 · 0 comments
Open

Sitemap rendering broken on NextJS 15 with edge runtime #75174

isaacrowntree opened this issue Jan 22, 2025 · 0 comments
Labels
Output (export/standalone) Related to the the output option in `next.config.js`.

Comments

@isaacrowntree
Copy link

isaacrowntree commented Jan 22, 2025

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/cranky-https-7mqs67

To Reproduce

Error:

15:44:40.872 | ▲  ⚠ Using edge runtime on a page currently disables static generation for that page
15:44:41.910 | ▲  [Error: Failed to collect configuration for /sitemap/sitemap/[__metadata_id__]] {
15:44:41.910 | ▲  [cause]: [Error: Edge runtime is not supported with `generateStaticParams`.]
15:44:41.911 | ▲  }
15:44:41.914 | ▲  > Build error occurred
15:44:41.919 | ▲  [Error: Failed to collect page data for /sitemap/sitemap/[__metadata_id__]] {
15:44:41.920 | ▲  type: 'Error'
15:44:41.920 | ▲  }
15:44:42.040 | ▲  Error: Command "npm run vercel-build" exited with 1

The sitemap MUST be edge-based - I don't want to statically-generate all my existing content.

Current vs. Expected behavior

I expect to run all my sitemaps as dynamic edge functions as I could in NextJS 14. At the moment I can't even get past the build stage - this is the only thing remaining to bring me from Nextjs 14 to 15.

Provide environment information

Cloudflare Next on Pages

Which area(s) are affected? (Select all that apply)

Output (export/standalone)

Which stage(s) are affected? (Select all that apply)

Other (Deployed), next build (local)

Additional context

This build error occurs locally also. For now I've tried to use static generation but cloudflare pages also fails on this step as the database url isn't provided from the environment on build to the build step. Weird. Still, this is a regression IMHO.

@github-actions github-actions bot added the Output (export/standalone) Related to the the output option in `next.config.js`. label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Output (export/standalone) Related to the the output option in `next.config.js`.
Projects
None yet
Development

No branches or pull requests

1 participant