Skip to content
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

vercel 部署报错 No Output Directory named "public" found after the Build completed. #3

Closed
zyxyxz opened this issue May 2, 2023 · 2 comments

Comments

@zyxyxz
Copy link

zyxyxz commented May 2, 2023

...writing to cache...

17:30:04.205 | Error: No Output Directory named "public" found after the Build completed. You can configure the Output Directory in your Project Settings.
17:30:04.206 | Learn More: https://vercel.link/missing-public-directory
17:30:04.818 | Deployment completed
17:30:04.430 | STATIC_BUILD_NO_OUT_DIR: No Output Directory named "public" found after the Build completed. You can configure the Output Directory in your Project Settings.

image

@seshubonam
Copy link

seshubonam commented May 2, 2023

+1 , yeah same problem. thanks

update:
solved if you update output path in vercel settings to 'apps/chat/public'

but shows a 404 page and logs show a warning of "Pages directory cannot be found at..//...If using a custom path, please configure with the no-html-link-for-pages rule in your eslint config file"

something related to experimental appdir?

///

+1,是的,同样的问题。 谢谢

更新:
如果您将 Vercel 设置中的输出路径更新为“apps/chat/public”,则会解决

但显示 404 页面并且日志显示警告“Pages directory cannot be found at..//...If using a custom path, please configure with the no-html-link-for-pages rule in your eslint config file “

与实验性 appdir 有关的东西?

@AprilNEA AprilNEA mentioned this issue May 4, 2023
@AprilNEA
Copy link
Owner

AprilNEA commented May 4, 2023

现在你可以在 https://docs.lmo.best/docs/quick-deploy 查看部署步骤

@AprilNEA AprilNEA closed this as completed May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants