Nuxt open fetch issues
Hi!
https://github.com/enkot/nuxt-open-fetch/issues/83
I spend multiple hours trying to figure out this issue.
I have no idea why this library calculates different keys in server and browser resulting in fetching data multiple times. I tried removing entire
autoKey feature etc, but I can't still make it work. Any ideas?GitHub
Nuxt 3.15.1 breaks the module · Issue #83 · enkot/nuxt-open-fetch
Environment Operating System: Darwin Node Version: v20.13.0 Nuxt Version: 3.15.1 CLI Version: 3.17.2 Nitro Version: 2.10.4 Package Manager: [email protected] Builder: - User Config: default Runtime Module...
3 Replies
Hi @Norbiros. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I understand you're having issues with the nuxt-open-fetch library and key generation differences between server and client. While I don't have specific information about this third-party library in my knowledge sources, I can explain how key generation works in Nuxt's native fetch utilities, which might help you understand the underlying issue.
In Nuxt's native
useFetch and useAsyncData, keys are crucial for preventing duplicate data fetching between server and client. When a key isn't explicitly provided, Nuxt automatically generates one based on certain request properties.
According to the documentation, the auto-generated key in Nuxt's native fetch utilities:
- Is based on URL and some fetch options
- Includes query params, method, and base URL
- Does NOT include the request body
This is mentioned in a GitHub issue comment:
"No, the body is not part of auto-generated keys, only query params, method, base url" Github Issue #31098This could be relevant to your issue if the library is trying to use the request body as part of the key generation process. Some potential solutions based on Nuxt's native behavior: 1. Try explicitly providing a consistent key to your fetch calls 2. If you're using different request bodies but want them treated as separate requests, you'll need to manually set unique keys 3. Check if the library has options to customize key generation If you're seeing hydration mismatches or duplicate fetches, it might be related to how the keys are being generated differently between server and client environments. Without more specific information about nuxt-open-fetch's implementation, I can't provide a definitive solution, but understanding how Nuxt's native key generation works might help you debug the issue. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
<@770620808644919307> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
Manually typing keys fixes it, but it isn't perfect solution
No I am thinking that I could add something like:
But it is still a temporary workaround
Maybe I am doing something very wrong, but when i try linking it using pnpm it works, but if i publish my patched version it doesnt