⌘K
Anshuman Bhardwaj This is superb! Thanks for sharing the step by step guide here 🙌 Can't wait to try
Jonoroboto Tell us how you get on. One thing we haven’t figured out yet, that I would love to solve, is agent orchestration with git worktrees and how best to fire something off like that in one go. Think a less destructive Gastown, that you’d be comfortable throwing at a production repo. This is a simplified workflow, but should give you the idea.
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.
SkyMesh Dynamics ah, then I'm not the only one who reported this
Ryu Hi Yuze, Your openssl test is a good way to narrow it down. Since this fails when the trailing dot is included in SNI: echo | openssl s_client -connect deckclip.app:443 -servername 'deckclip.app.' but works without it: echo | openssl s_client -connect deckclip.app:443 -servername 'deckclip.app' then this is happening before your Next.js app or vercel.json redirects can run. So I don’t think there’s an app-level redirect/header fix for the HTTPS case. A trailing dot is valid in DNS as an absolute/FQDN form, but TLS certificate/SNI matching is a separate layer. If Vercel’s edge does not normaliz
Pauline P. Narvas The NS_BASE_STREAM_CLOSED error typically occurs when the MCP client connection is closed prematurely. When you're using MCP tools with streaming, the client needs to stay open until the entire response completes, if it closes early, you'll hit this error. Here's what I'd recommend checking: Make sure your MCP client isn't timing out or disconnecting before the stream finishes Verify that your connection handling code keeps the client alive throughout the entire streaming response Check if there are any timeout settings that might be causing the connection to close early Let me know if you hav
phanithlim Thanks Pauline P. Narvas for the response! I’ve been stuck on this for about 3 days now and still can't resolve it. I was previously using experimental_createMCPClient, and it worked perfectly. However, since I updated my code to use the standard createMCPClient, I began facing the NS_BASE_STREAM_CLOSED issue mentioned above. The connection seems to drop the moment the LLM starts streaming the tool output back to the UI. Since I am using streamText with toUIMessageStreamResponse(), I suspect the new createMCPClient handles transport lifecycles differently, causing it to be garbage collected or
Tianen Pang check this one github.com/vercel/next.js/issues/89764#issuecomment-3928272828 for temp fix
ADALIGO The error comes from tooling mismatch not from you Luknuts56, just downgrade ESLint and you’re good 👍
Ryu Hi Luknuts56, This one looks like a tooling-version mismatch, not a problem with your loading.tsx file. Your package.json has: "eslint": "10.0.3", "eslint-config-next": "^16.1.7" and the stack trace is failing inside eslint-plugin-react while loading the react/display-name rule. There’s an open Next.js issue for this same ESLint 10 error: github.com/vercel/next.js/issues/89764 For now I’d pin ESLint back to v9 instead of using ESLint 10: pnpm add -D eslint@^9 eslint-config-next@latest pnpm lint If it still keeps ESLint 10 because of the lockfile, do a clean install: rm -rf node_modules pnpm-lo
Craiguito I’d isolate the database package before blaming Vercel or the whole template. From a clean folder, try the init with pinned tooling instead of all latest versions: corepack enable corepack prepare pnpm@9.15.4 --activate npx next-forge@latest init If it still creates the repo but fails at @repo/database, cd into the generated project and run: pnpm --filter @repo/database build That should give you the real TypeScript/ORM error instead of Turbo’s wrapper error. The log in the post only says the package build failed, not why. My guess is a version mismatch between the template’s database package
Ryu Hi Segal, The log you posted is still Turbo’s wrapper error, not the actual database package error. I’d isolate @repo/database first before treating the whole template as broken. From a clean terminal, try pinning the toolchain instead of using whatever “latest” resolves to: node -v corepack enable corepack prepare pnpm@9.15.4 --activate pnpm -v npx next-forge@latest init If the init still fails but leaves a partial repo behind, go into that repo and run the failing package directly: pnpm --filter @repo/database build or: cd packages/database pnpm build That should show the real TypeScript / O
Anshuman Bhardwaj Hi @nisarganand541-8212, welcome to the Vercel Community! I'm so happy to see your enthusiasm here. I'd suggest starting small and building v0 projects with them in hackathons or college competitions. Once you have a solid foundation of organizing and managing small events, you can also use our meetup-sdk.vercel.com to organize a meet up and we'll support you there. Let me know if you have any specific questions.
mr.li512486 Hi Saqib and Vercel Community Team! I’m also a college student, from Guangdong, China, and I’m currently organizing a student-led AI developer club at my college. We are starting with around 20 core members, focusing on AI development, Vibe Coding, Next.js, Vercel, v0, AI SDK, Codex, and other modern AI development tools. After seeing your experience building a Vercel community at your university, I realized that this is very close to what we are hoping to build on our campus. We would love to explore whether there is any way for us to work with the Vercel Community as we start organizing work
sara keyser @nisarganand541-8212 This is an awesome mission! I'd also reach out to your college's student activities/student engagement team and any campus communications or student organizations office. Maybe they can help promote your events through the campus events calendar, newsletters, social channels, and student org network. You could also partner with some other student groups to get the word out and co-host the first workshop. I would also explore the local library, coffee shops or places where you can get on local event calendars so you can attract people outside the school..even your city's ch
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
Swarnava Sengupta With 106M ISR writes vs 30M ISR reads, your write-to-read ratio is unusually high (about 3.5:1). This typically indicates one or more of these issues: Very short revalidation intervals – If your revalidate value is too low (e.g., 10-30 seconds), pages regenerate frequently even if content hasn't changed Excessive on-demand revalidation calls – If your backend triggers revalidatePath() or revalidateTag() too aggressively on every content update Bot/crawler traffic triggering regenerations – Bots hitting many unique URLs can cause cache misses that trigger new page generations Large number of un
Akash Electron thank you @swarnava
