No output directory found

[northrn]

Currently receiving this error when trying to deploy using deploy button in the repo:

Error: No Output Directory named "public" found after the Build completed. You can configure the Output Directory in your Project Settings.

Tried overriding output directory settings in Vercel but with no luck.

[lluisinthedesert]

Same issue.

[mu-ct]

In your Vercel dashboard, click on the project, go to Settings and in Build & Development Settings click on Override for Output Directory and put '.' there (just the full stop, without the quotation marks). Then Save, go to Deployments and Redeploy

[abdokouta]

@mu-ct i have try it and getting 404, , and below is my deployment config

[northrn]

In your Vercel dashboard, click on the project, go to Settings and in Build & Development Settings click on Override for Output Directory and put '.' there (just the full stop, without the quotation marks). Then Save, go to Deployments and Redeploy

Same as above, that will get you a deployment, but then you just have a 404 at the destination.

[nuchtoskazat]

same

[pontusab]

fix incoming!

[alecdewitz]

Fixed this by changing the output directory to apps/web/.next as shown above

[abdokouta]

@alecdewitz same issue 404

[abdokouta]

@alecdewitz it's fixed after changing the Framework Preset to nextjs

[pontusab]

1. Select Framework and Preset to nextjs
2. Add turbo run build --filter=@v1/app or `turbo run build --filter=@v1/web depending on application
3. Make a new deployment by a git push (change something) for the build settings to take effect

Adding this to the documentation, unfortunately I can't get the deploy with Vercel button work with this!

[mihau12]

Hey, thanks as lot for your work!

Unfortunately the solution leads to "The file "/vercel/path0/.next/routes-manifest.json" couldn't be found. This is often caused by a misconfiguration in your project."

[northrn]

Hey, thanks as lot for your work!

Unfortunately the solution leads to "The file "/vercel/path0/.next/routes-manifest.json" couldn't be found. This is often caused by a misconfiguration in your project."

Yep same issue for me. @pontusab

[jaaneh]

This works for me!

[erquhart]

@pontusab looks like the vercel deploy button flow has diverged quite a bit from real world initialization (and it's broken) - might be worth dropping it. Lost a good amount of time trying to get it working before scrapping and just following the readme.

[pontusab]

yeah will fix that! sorry about that

[hamilton-lima]

With this approach we would need a separated project for each application right? as the build command is filtering for @v1/app only. is there a way to setup the build to deploy all: api and app and web with a single project?