#Vercel deployment errors on every second or third deployment

17 messages · Page 1 of 1 (latest)

median osprey
#

Every second deployment somehow fails

Learn More: https://vercel.link/missing-public-directory
STATIC_BUILD_NO_OUT_DIR: No Output Directory named "dist" found after the Build completed. You can configure the Output Directory in your Project Settings.

If I click redeploy, everything is OK. Does anyone know why?

rapid nacelleBOT
#
Still waiting for an answer?

It looks like no-one has responded to your question yet. People might not be available right now or don’t know how to answer your question. Want an answer while you wait? Try asking our experimental bot in #1095492539085230272.

median osprey
#

I think I have found my issue. The problem is that turbo is trying to build my astro repo but I'm using it for 4 websites. So I need to exclude astro from turbo (or at least the build part, so that is not shared)

median osprey
#

/solve

narrow lava
#

@median osprey are you using hybrid in your astro settings?

median osprey
#

hybrid, but I have solved it by creating a new repo

#

I wasn't able to get the right turbo-config, so I moved on

narrow lava
#

I see, i have enabled all the required experimental flags. Still getting errors

#

It tried to build the static routes but fails to find the first image, when i run pnpm run astro build

#

Been trying to figure out what the issue is

#

Any advice on how to try and fix this?

median osprey
#

Not sure what your specific issue is tbh

#

Are you using a mono-repo setup? Whats the error message on vercel?

median osprey
#

Did you set the build config to Astro in your vercel project?

#

How does your astro.config.js looks like?

narrow lava
#
export default defineConfig({
intergrations: [react(), tailwind(), astroImageTools, compress()],
output: 'hybrid',
experimental: {
  hybridOuput: true,
  assets: true,
  },
adapter: vercel({
  imageService: true
  })
});