Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The data returned by useFetch has contents, but the value is null where lazy is true
See original GitHub issueEnvironment
- Operating System:
Windows_NT - Node Version:
v14.17.5 - Nuxt Version:
3.0.0-rc.6 - Package Manager:
npm@6.14.14 - Builder:
vite - User Config:
alias,runtimeConfig,css,modules,postcss,autoImports,hooks - Runtime Modules:
@nuxtjs/tailwindcss@5.3.1,@pinia/nuxt@0.3.1,@vueuse/nuxt@8.9.4 - Build Modules:
-
Reproduction
https://stackblitz.com/edit/github-svkc8u?file=pages%2Findex.vue,pages%2Ftest.vue
Describe the bug
When you go to the test page and you go back to the index page through nuxtLink, you get this situation that I just described,
Additional context
I am not sure if this problem occurs only when lazy is true. I have encountered the situation that the data has content but the value cannot be obtained for several times. At present, it will occur in the demo I provided
step: 1.The URL directly accesses /test 2.Go back to Index via Nuxtlink 3.To view the log
Logs
No response
Issue Analytics
- State:
- Created a year ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I appreciate that, brother!
I suggest you read the data fetching section of nuxt 3’s documentation for ways to deal with this. Either you will rely on a lazy solution, in which case you will need to deal with the data being null for a while, or you don’t use a lazy solution but your fetch will block navigation until data is there.