Hi @operator-4026, welcome to the Vercel Community!

I think setting the root directory to the subfolder should fix this issue. Have you tried setting your Root directory to men-work/nmmng-bootcamp from project settings:

Let me know if it works.

root diretory was set correctly, still not solved

I see. Can you share the build output screenshot from the deployment details?

✓ built in 4.53s

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

Learn More: https://vercel.link/missing-public-directory

I see. Have you recently made some changes before which the build was working correctly?

This most likely seems to be a Root directory + Output directory + Framework preset misconfiguration.

Can you please share your public repo or a minimal reproducible example. That will let us all work together from the same code to figure out what’s going wrong.

cannot associate what what changes broke it down. i keep working on Cursor and deploying on github. does this answer your question about the public repo?

Oh, you are using Cursor. Do you have a GitHub repo I can look at?

https://github.com/rowan-associates/NMMNG

i changed the folder structure since the last succesful vercel deploy

Thanks for sharing the repository.

I was able to deploy your project: https://men-work.vercel.app/ by changing a few things:

• removing the root vercel.json
• making men-work the project root directory
• removing base: '/NMMNG/', from vite.config.js (it didn't work locally with base path)

I noticed that you've node_modules/ and dist/ folders checked into the GitHub repository, which is an anti-pattern and not at all needed.

I appreciate very much your help, i a newbie with this technologies.

Cursor attempted a fixed following your reply and now i am here:

Thank you for clarifying. If you have the correct settings (as shown in your screenshot), but redeploying still results in the "No Output Directory named 'dist'" error, and there is nothing left to save or change, then the issue is almost certainly due to a stale or stuck Production Override in Vercel’s backend.

What’s Happening

• Your settings are correct in the UI.
• Vercel is still using an old override (possibly from a previous configuration) that is not visible or editable in the current UI.
• This is a known Vercel issue, especially after moving project roots or deleting subfolders.

What You Should Do

1. Remove All Production Overrides

• At the top of your Framework Settings, if you see a yellow warning about "Production Overrides," click it.
• Remove any overrides for Output Directory or Root Directory.
• Save and redeploy.

2. If You Cannot Remove the Override

• Sometimes, the override cannot be removed from the UI (it may be "stuck" in Vercel’s backend).
• Contact Vercel Support and ask them to remove all Production Overrides for your project.
  • Mention that you have already set the correct Output Directory and Root Directory, but the build still fails with the "No Output Directory named 'dist'" error.
  • Reference your project name and the error message.

3. Double-Check Your Repo

• Make sure your dist folder is being created in men-work/ after build (which your logs show is happening).

Summary

• You have done everything right.
• The error is almost certainly due to a stuck Production Override in Vercel.
• Contact Vercel Support to clear all overrides for your project.

You are not alone—this is a common Vercel issue after project restructuring. Once the override is cleared, your deployment will work perfectly.

Let me know if you want a template message to send to Vercel Support!

@operator-4026 were you able to solve the issue?

I was able to deploy the same project correctly, so it definitely isn't a Vercel issue.

Hi @operator-4026! 🙂

We haven't heard back from you. If you're still stuck, feel free to share any updates, logs, or additional context that might help us assist you better!