-
Notifications
You must be signed in to change notification settings - Fork 13
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
Edge runtime is not compatible with ISR #102
Comments
I see there is a TODO already: 😄 vite-plugin-vercel/packages/vike-integration/+config.ts Lines 9 to 15 in 5a75f94
Maybe headers could be implemented in vike code. |
My opinion is that if one has edge + ISR activated for an endpoint, it should be considered a configuration issue (and users should be warned accordingly). I just wonder if we should just warn the user and default to edge only, or just throw an error. |
I agree, it's a configuration issue and we should throw an error. But I think we should also:
For the second one, I think we can make two ssr bundles, one for edge and one for node? Or maybe we can get away with having only the edge bundle and just set the runtime to node for that page in |
This should be fairly straightforward to implement, and I'll probably try this solution first.
I need to see what I can do about that. I probably will not be able to try this soon, so any help is welcome on that matter :) |
Vike now supports |
https://nextjs.org/docs/pages/building-your-application/data-fetching/incremental-static-regeneration
I have a few different ideas to solve this:
headersResponse
vikejs/vike#1803The text was updated successfully, but these errors were encountered: