Environment

• Operating System: Darwin
• Node Version: v20.19.2
• Nuxt Version: 3.17.6
• CLI Version: 3.25.1
• Nitro Version: 2.11.13
• Package Manager: pnpm@10.10.0
• Builder: -
• User Config: ssr, modules, devtools, spaLoadingTemplate, future, runtimeConfig, colorMode, ui, css, app, routeRules, plausible, $production, $development, sourcemap, sentry, compatibilityDate
• Runtime Modules: @sentry/nuxt/module@9.35.0, @nuxt/ui-pro@3.2.0, @nuxtjs/mdc@0.17.0, @nuxt/image@1.10.0, @vueuse/nuxt@13.5.0, @nuxt/scripts@0.11.9, @nuxtjs/plausible@1.2.0
• Build Modules: -

Reproduction

x

Describe the bug

After a recent Nuxt update, it seems that this pattern no longer works :

watch(q, execute)

Only works with :

watch(q, () => execute())

Proposal by @OrbisK

Implement a runtime check to handle non-objects being passed to execute.

linked to #32109 (comment)

Additional context

No response

Logs