InputMenu emit order #4664
Description
Environment
- Operating System: Darwin
- Node Version: v24.7.0
- Nuxt Version: 3.19.1
- CLI Version: 3.28.0
- Nitro Version: 2.12.5
- Package Manager: [email protected]
- Builder: -
- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, scripts, piniaPluginPersistedstate, modules, sentry, sourcemap
- Runtime Modules: @nuxt/[email protected], @pinia/[email protected], pinia-plugin-persistedstate/[email protected], @sentry/nuxt/[email protected], @nuxt/[email protected], @nuxt/[email protected], [email protected]
- Build Modules: -
Is this bug related to Nuxt or Vue?
Nuxt
Version
v3.3.3
Reproduction
In my reproducible I use Nuxt V4 but it's the same behavior with Nuxt V3
Description
Actually the create emit is triggered after the change one, so it make some strange reactivity issues (because we rely on the change event for our server updates in some cases), actually we simply put a setTimeout on the change emit as a workarround but I didn't think it's a good solution 🥲
I think there is the same issue on the SelectMenu too (I haven't tested it)
Additional context
No response