-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support SWR #428
Comments
You're right and I think the conclusion is that we do not support SWR. I struggle to see how SWR is compatible with
@Baroshem what's your opinion on this ? |
Thanks for the investigation @vejja I would probably go for the second option but maybe @danielroe would have a better idea? :) |
Let me investigate better because I actually think we can support natively without moving to hash mode Update: I think the new feat/unified-router-context branch will support SWR natively, will confirm later |
@MarijnFK would you be able to share a minimal Stackblitz repro of a basic use case ? |
@vejja I've made a very simple stackblitz, it's not really a use-case but it shows the problem. The top date shows the ssr-date. It should update every 10 seconds. |
@vejja Good to hear, looking forward to the update! Thanks for the (quick!) responses |
When using a SWR option in routeRUles, the nonce-header does not match the one served from the server:
Version
nuxt-security: 1.3.2
nuxt: 3.11.x
Steps to reproduce
enable swr on all routes:
What is Expected?
The header should use the generated nonce value


What is actually happening?
The header uses the new nonce, but the html served is using the nonce that was used when generating the page
The text was updated successfully, but these errors were encountered: