add vercel quick start

[vkarpov15]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
studio-mongoosejs-io	Ready	Preview, Comment	May 6, 2026 3:59pm

[chatgpt-codex-connector]

💡 Codex Review

studio.mongoosejs.io/src/docs/vercel-quick-start.md

Line 51 in cc8b967

import studio from '@mongoosejs/studio/backend/vercel';

Use the supported Next backend entrypoint

This quick start tells users to import @mongoosejs/studio/backend/vercel, but the Studio package exposes the Vercel/Next.js handler as @mongoosejs/studio/backend/next (the existing start page and upstream README use that path, and there is no backend/vercel entrypoint). Anyone copying this route will get a module-not-found error before the API route can load.

---

studio.mongoosejs.io/src/docs/vercel-quick-start.md

Line 62 in cc8b967

export default handler;

Don't present a Pages handler as App Router-compatible

When users follow the app/api/studio/route.js option mentioned above, this export default handler form is not a valid App Router route handler; Next's App Router expects named HTTP method exports such as GET/POST, so the Studio API route will not be registered in that setup. Either remove the App Router path from the instruction or provide an App Router-specific wrapper.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".