Solid start build sometimes doesn't work on vercel

[OrJDev]

(Sometimes) Log stucks on vercel when trying to build & deploy, no error or anything it just freezes. It does work when trying to build locally but it is pretty annoying having to wait for it to build before running

vercel deploy --prebuilt.

Any idea what causes that?

[OrJDev]

(here)

[nksaraf]

I think this might be a bug with our SPA mode build. We start a vite dev server to ask for the index.html but we should probably figure out a different solution. I have some ideas. You can keep ssr: true for now? That should be more reliable

[OrJDev]

Based on my stack I really prefer not to, but if that's the only solution I'll do that.

[nksaraf]

Just a workaround for vercel until we fix this.. or you can build locally and deploy using vercel deploy --prebuilt

[OrJDev]

Just a workaround for vercel until we fix this.. or you can build locally and deploy using vercel deploy --prebuilt

Bulding and deploying it locally is more complicated when using Prisma, it requires additional configuration and since all of my projects use Prisma this isn't an ideal solution.

[nksaraf]

Ahh okay makes sense. Is there a repo I can look at and try.. Have been meaning to figure out is prisma works properly.. I can debug the issues better than way

[OrJDev]

Sure

https://github.com/OrJDev/solid-trpc-authentication

Edit: Also notice that i deployed this not using the cli but using the vercel website connected to a github repo - so Prisma does work on the website that's linked to the repo, so try to debug it when deploying using the vercel cli and not when deploying from the vercel website.

[nksaraf]

Ahh okay so it works when deployed from vercel website but not locally ?

[OrJDev]

Ye i mean you could try any repo that uses prisma, not mine specifically. If you build it locally and deploy it using the cli it will throw some ssl xxx weird error, therefore it needs to be built in vercel environment instead.

[aidanaden]

hi! i ran into the same issue when using pnpm as my package manager, solved this issue by using yarn instead!

[atzzCokeK]

The same thing happens to me. Suddenly It can't be deployed. I tried to use yarn instead of pnpm, but never solved. ~I add source code about <Context>, that might cause this failed?~ I don't know..., sorry I am very new.

[atzzCokeK]

When I change to ssr mode, the error is updated!

[rshov]

Same problem here

[AshSimmonds]

Not a definitive answer, but longer thread on Discord, basically you can have a typo in an import (and possibly other things) and it will get stuck in a loop at that point in the build process before it can fail that.

[ryansolid]

Please retry again 0.2.19. I've made some big improvements to ssr: false. I can't reproduce the issue locally at least by messing with imports.

[OrJDev]

Please retry again 0.2.19. I've made some big improvements to ssr: false. I can't reproduce the issue locally at least by messing with imports.

Yes this seems to work with the exact same project that failed with older versions:

solid-start building client...
--
10:13:47.448 | solid-start rendering index.html...
10:13:49.696 | solid-start index.html rendered in: 2.248s
10:13:49.736 | vite v3.2.5 building for production...
10:13:49.763 | transforming...
10:13:53.533 | ✓ 212 modules transformed.
10:13:53.602 | Inspect report generated at /vercel/path0/.solid/inspect

closing this