-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
adapter-vercel seems to be broken at @sveltejs/kit@1.0.0-next.292 #4224
Comments
It looks like #4192 didn't include the appropriate changesets for any of the adapters, and so they weren't actually released. |
Just going to note that this appears to impact more than just vercel. I'm attempting to build with the static-adapter and running into the same error message. |
yes, same for
|
The solution from me turns back or use the previous version that
Thanks |
|
Confirmed that this issue also affects |
See this issue is closed but I'm still experiencing the problem with adapter-node. Just reverted to SvelteKit 1.0.0-next.291 as a temporary fix. |
The build is broken. The release of adapter-static 29 is coming. |
so any version that doesn't include the changes made by #4192 currently works? |
Now we can install |
I'm still having the same issue even with adapter-static 1.0.0-next.29. |
Same here, issue persists even with rolling back the adapter version. |
It would be much more useful to open a new issue rather than comment on a closed issue. The comments here have none of the information that would be required to debug an issue and the issue template will guide you to providing that information |
I managed to fix mine by manually installing/updating both sveltekit and the adapter even though they were set to install the latest version when building in Netlify. |
You probably needed to update your npm lock file |
Thanks dude. @faisalramdan17 |
After much trial and error here are some settings that work:
|
why is this closed? has it being fixed? |
Sometimes destructive change occur because kit is under beta. This problem was opened when release timing between kit and adapters was off by several hours. If you have a problem now, you need to open a new issue. |
Ran into the same problem yesterday with adapter-node and had to downgrade to 288. |
Yeah, for me I only got around it with some magical combination of downgraded versions. Eventually something worked, not ideal by any means. 🤷 |
I did a |
Also, update adapter-static to 1.0.0-next.29, following the instructions from sveltejs/kit#4224 (comment) and setting kit.prerender.default to true (whatever that means...)
Also, update adapter-static to 1.0.0-next.29, following the instructions from sveltejs/kit#4224 (comment) and setting kit.prerender.default to true (whatever that means...)
Also, update adapter-static to 1.0.0-next.29, following the instructions from sveltejs/kit#4224 (comment) and setting kit.prerender.default to true (whatever that means...)
Describe the bug
Vercel builds seem to be broken by #4192 since adapter-vercel still uses
builder.prerender
.Reproduction
StackBlitz link
Run
npm run build
to see error.Logs
System Info
Severity
blocking an upgrade
Additional Information
Blocks upgrade to @sveltejs/kit@1.0.0-next.292
The text was updated successfully, but these errors were encountered: