-
Notifications
You must be signed in to change notification settings - Fork 34
Handle SvelteKit breaking changes - build fails for versions >= next.208 #6
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
Comments
Update: looks like sveltejs/kit#2931 is the correct PR to reference, which also includes changes to generate functions per route instead of a single monolith. |
Also some changes to integrate w/ the request object -- path/query have been replaced with URL. See sveltejs/kit#3133 |
I made the updates to support v. next-208 and confirmed it works with the latest SvelteKit demo app. The linked PR did not include code-splitting API routes, since it seems like that's only implemented for the Netlify adapter and is marked as experimental. I'll look into implementing that feature when it's more stable. |
Uh oh!
There was an error while loading. Please reload this page.
sveltejs/kit#2580
$server-build
alias instead of hard-coded relative pathserverEntryPoint
@sveltejs/kit/install-fetch
directly instead of more complicated shimReference that PR for README updates as well (no more custom esbuild config).
The text was updated successfully, but these errors were encountered: