-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Route level config not working for +server.js
#8908
Comments
'Reproduction' is not an optional field. If this relates to ISR, there is a known issue we are currently investigating. |
@Rich-Harris I thought that was pretty self-explanatory, but I guess it's not: https://github.com/Smirow/kit-issue-8908 Should create two lambdas as I defined a config in export const config: Config = {
memory: 512,
split: true // not needed
}; But when deployed to Vercel (or built for Vercel) it is bundled with the other route. So it seems that |
So probably related to this as kit/packages/kit/src/core/postbuild/analyse.js Lines 94 to 130 in 48bdb02
|
Can confirm that if I specify envinfo:
|
Describe the bug
Route level config seems to be ignored for
+server.js/ts
Reproduction
Deploy to Vercel with a route level config in
+server.js/ts
.Logs
No response
System Info
No response
Severity
annoyance
Additional Information
No response
The text was updated successfully, but these errors were encountered: