Skip to content

useFetch with immediate: false causes watch to stop triggering in Nuxt 3.17.3 #32109

@maximepvrt

Description

@maximepvrt

Environment

nuxt: 3.17.3

Reproduction

Partage.d.ecran.-.2025-05-14.16.h.57.min.17.s.mp4

https://stackblitz.com/edit/github-ycxmi8dl-ou7o3zwv?file=pages%2Findex.vue

Describe the bug

When immediate: false is set, the watch that should trigger the fetch stops working after a while. I haven't been able to fully isolate the cause, but it seems to happen when I change the watched value before the previous fetch has completed. After that, subsequent changes to the value don't trigger any new request.

Additional context

No response

Logs

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy