Hey, you are using an edge version of the release candidate that wasn't yet released (current stable one is -rc.12) so I would guess that this can be the issue.
When we deploy a project to vercel, it scan's the project structure and try to offer some template settings based on the project, so the default "output directory" that Vercel's offer for a Nuxt project is the "dist" and it works well for static site generate as so for SSR...
i tried changing
OUTPUT DIRECTORYinto.vercel/output/staticinstead.output/publicand then successDoesn't seem to work for me with Nuxt
3.0.0-rc.13-27772354.a0a59e2andssr: false. Am I missing something?Hey, you are using an edge version of the release candidate that wasn't yet released (current stable one is -rc.12) so I would guess that this can be the issue.
Ok, will wait for -rc.13. It's just strange bc if I build locally the .output/public folder is there.
I just deployed a project using Nuxt3 and Vercel and it works with the config:
'build command' to nuxt generate the 'output directory' to the default *dist *...
What do you mean with default dist?
When we deploy a project to vercel, it scan's the project structure and try to offer some template settings based on the project, so the default "output directory" that Vercel's offer for a Nuxt project is the "dist" and it works well for static site generate as so for SSR...
Hey there! Good news, Nuxt on Vercel is now fully zero-configuration, including Nuxt 3: vercel.com/docs/frameworks/nuxt
Hey Lee!
Thanks for letting me know! This article is now a bit outdated.
I will check out the link you mention and create an updated article for it! :)
Simple, clean and efficient. ππ»