Could not deploy on Netlify
See original GitHub issueEnvironment
- Operating System:
Darwin
- Node Version:
v16.11.1
- Nuxt Version:
3-3.0.0-27234417.10170da
- Package Manager:
Yarn
- Bundler:
Webpack
- User Config:
-
- Runtime Modules:
-
- Build Modules:
-
Describe the bug and expected behavior
I got the following error when deploying on Netlify:
Configuration error
Error message Deploy did not succeed: Deploy directory ‘.output’ does not exist
The previous steps completed with success:
- Build command from Netlify app
- Functions bundling
Steps to reproduce
- Create a new site from GitHub
- Choose
.output
as publish directory on Netlify - Deploy
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
[Support Guide] Frequently encountered problems during builds
js — the Netlify build may fail due to the mixed case filename. The file system used in Netlify builds is case sensitive,...
Read more >Deploy failed Netlify - Stack Overflow
A workaround is removing /build from your .gitignore and then removing the build command (yarn build or npm run build) from the build...
Read more >2 ways to overcome deployment problems with React on Netlify
Solution 2: Make changes in your deployment setting on Netlify directly: In Netlify open "Site details" - Build & deploy - Environment - ......
Read more >6. Deploy to Netlify - Introduction - Lowdefy
Create a new Github repository. You can do that here. Do not initialize the repository with a .gitignore , README , or licence...
Read more >How to Deploy a React Router App to Netlify and Fix the ...
How to Deploy Your App Through the Netlify CLI. To start using Netlify's CLI, you must have Node.js installed on your computer. You...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have the same issue here. I have always had ‘dist’ as build directory. Deployment worked perfectly the first time, now this every time:
It seems to work if you choose ‘/dist’ instead ‘/.output’ as publish directory, btw i set base directory as ‘/’