Question about useFetch running with undefined route param
nuxt4
Hey 
I’m using useFetch with a dynamic route param and sometimes it executes with route.params.id being undefined, which causes a request like:
Example:
If route.params.id is temporarily undefined (SSR / hydration timing?), the request still runs and fails.
What’s the recommended Nuxt 3 way to prevent useFetch from executing when the param doesn’t exist?
Currently I’m working around it like this:
Is returning null the intended/official pattern, or is there a better approach?
I’m using useFetch with a dynamic route param and sometimes it executes with route.params.id being undefined, which causes a request like:
Example:
If route.params.id is temporarily undefined (SSR / hydration timing?), the request still runs and fails.
What’s the recommended Nuxt 3 way to prevent useFetch from executing when the param doesn’t exist?
Currently I’m working around it like this:
Is returning null the intended/official pattern, or is there a better approach?
