-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
feat: Vercel adapter #2915
feat: Vercel adapter #2915
Conversation
🦋 Changeset detectedLatest commit: bf2199e The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
I've created |
Perfect, I've made it work somehow. It turned out the Node.js helpers Vercel gives you (like |
ef9e81a
to
d6f0d5c
Compare
I had a lot of trouble generating the pages statically and converting the endpoints to API Routes. So, I took a similar approach to what the Netlify adapter does. Nonetheless, I'm waiting to #2937 to get mergerd. In the future I could do a PR that lets you generate statically all the pages for both Netlify and Vercel |
@JuanM04 Our SSR implementation is currently designed to be SSR-only, not a mixture of static + SSR. Something we might change in the future. |
Changes
Adds the Vercel adapter that works with Vercel's Files System API.
Testing
TBD
Docs
TBD