#sveltekit

Maya Avendaño Nice, thank you you for sharing this here @jis3r! As a Svelte fan and Geist fan, love to see it.

Ryu I don’t think there’s a SvelteKit-specific Queues guide yet, but the important pieces should still map to SvelteKit server routes. For push mode, I’d start with the smallest setup: ``` // src/routes/api/orders/+server.ts import { json } from '@sveltejs/kit'; import { send } from '@vercel/queue'; export async function POST({ request }) { const body = await request.json(); const { messageId } = await send('orders', body); return json({ messageId }); } ``` ``` // src/routes/api/queues/process-order/+server.ts import { handleCallback } from '@vercel/queue'; export const POST = handleCallback(async (message, metadata) => { console.log('processing queue message', metadata.messageId, message); }); ``` Then make sure the trigger in `vercel.json` points at the actual SvelteKit route file, not the Next.js example path: ``` { "functions": { "src/routes/api/queues/process-order/+server.ts": { "experimentalTriggers": [ { "type": "queue/v2beta", "topic": "orders" } ] } } } ``` A common gotcha is copying the docs’ `app/api/.../route.ts` path into a SvelteKit project. That path is for Next.js, so Vercel will not attach the trigger to your SvelteKit consumer. I’d also confirm these before debugging deeper: ``` pnpm i @vercel/queue @sveltejs/adapter-vercel vercel link vercel env pull vercel dev ``` If the build still fails on Vercel, the most useful detail to share would be the first actual build error line plus your `vercel.json` and the consumer route path, with any secrets removed.

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Pauline P. Narvas Thank you for your contribution, Michele! Welcome to the Vercel Community I've passed this onto the CICD team to review!

Michele Bertoli Gentle nudge on this one It's a 2-line change that brings `@vercel/react-router` in line with how Next.js, SvelteKit, and Qwik already set `__vdpl` and it unblocks Skew Protection for deep URLs Happy to add a changeset or any tweaks that'd help, just let me know

Pauline P. Narvas Welcome to the Vercel Community Congrats on getting onto the program Hopefully see you soon on a https://community.vercel.com/live!

Jakob Thank you, I will definitely join some sessions! :)