Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[🐞] Sitemap is always empty when deploy in Vercel with vercelEdgeAdapter

Open
#8,443 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
cloud, web-dev

Research direction

Use the linked reproduction repository and run pnpm run build plus pnpm run preview, then deploy with vercel --prod; compare sitemap.xml locally and on Vercel. Start with Qwik City routing and the vercelEdgeAdapter, and consider the work done when the deployed sitemap contains the same links as the local preview.

Written by the indexing model from the issue text.

Description

bug missing info router
Which component is affected?

Qwik City (routing)

Describe the bug
  • I followed the documentation here.
  • I can see the generated sitemap in dev mode
  • The sitemap is generated in prod mode as well (npm run build and npm run preview)

Issues
When I deploy to vercel (vercel --prod), the sitemap is empty

Reproduction

https://debug-sitemap-qwik.vercel.app/sitemap.xml

Steps to reproduce
Local build
  • pnpm run build
  • pnpm run preview

Visit the http://localhost:4173/sitemap.xml, and see, all links are there.

Deploy on vercel
  • vercel --prod

Result of sitemap

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> </urlset>
System Info
Firefox Developer Edition: 148.0.2
  npmPackages:
    @builder.io/qwik: ^1.19.2 => 1.19.2 
    @builder.io/qwik-city: ^1.19.2 => 1.19.2 
    typescript: 5.4.5 => 5.4.5 
    undici: * => 7.24.4 
    vite: 7.3.1 => 7.3.1
Additional Information

No response

Dominant language
TypeScript
Stars
22.1k
Forks
1.4k
Avg merge
1d 15h
Merged PRs (30d)
98

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from QwikDev/qwik

All issues in QwikDev/qwik

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.