-
Notifications
You must be signed in to change notification settings - Fork 17
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
Nuxt 3 Support #130
Comments
Yes, absolutely 👍 |
This package enabled us to pull the redirect data from CMS and use it in runtime by using its middleware. |
@ersah123 You can still use a nitro servermiddleware and pull things in there (+store them). |
but nitro middleware is a runtime and it runs on every server request, right? So where can i pull the redirect data in build time and share with nitro middleware? |
you can pull them on the first request (or during prerendering), then store them via unstorage ( |
But then my initial page load speed will suffer since it is like 11k lines of redirect rules i have :( |
Only the first one, and as I said, you could still "warm up" that cache |
You should use CloudFlare bulk redirects or something with so many |
That's true. we will implement long term solution later since we are trying to do nuxt 2 - bridge - nuxt 3 migration right now. |
@manniL , to update you and this topic, i have found a another solution for my use case which i believe was better as a short term solution. |
Hey 👋 It looks like this module hasn't been updated for Nuxt 3. In an effort to improve the developer experience of modules, I've updated the module to clarify that it only supports Nuxt 2.
Alternatives:
@manniL I'm presuming it's safe to say this can be deprecated at some point, given #120
The text was updated successfully, but these errors were encountered: