primocms/primo

adapter-auto @next breaks new deployments

niktek opened this issue · 1 comments

niktek commented

With the release of Svelte Kit 2 there were also new releases of the adapters. In package.json adapter-auto is set to next so it auto moved to the new releases, but svelte-kit is pinned at the major ^1 version. Changing the version of adapter-auto back to ^2.0.0 fixes the deployment issues on Vercel (and probably everywhere else)

Thank you! That did it