InputNumber can return NaN

[adamgreenhall]

Environment

latest - see repro

Is this bug related to Nuxt or Vue?

Vue

Package

v4.x

Version

latest

Reproduction

https://play.ui.nuxt.com/#eNo9jzFvhDAMhf/KU5YDqYXreuKqdujQha1bFqCGQwpOBE5aCfHf6wP1puTZfp+fV/MeQpEimYuplm4eg2AhiQGu4eFqjSzWvFoep+BnwYqZemzoZz/hpLaTZcud50WQcL13s3NuuY/cyegZ3U0xlOVYLQP3Qe+ocH7IUpEaF+kJ41I39b/M1bxZrsoji25WITQF1wipAqqwP8AHC82wprAGI0NuhNb/oiXnfyAeAwkaKBs7efeWh7n6+uQQpY5Tq4j0PPlvcnpsUtTbEVnV8dHSZREKWjgXL9aUSqjKRySz/QH1Y2y8

Description

If the user enters "." or "-" into an InputNumber and hits enter, the resulting value is set to NaN.

NaN values cause all sorts of wacky problems - if the user does this, maybe just revert to the previous value instead?

Additional context

No response

Logs

[danekslama]

Related, but a distinct typing-soundness bug (this one is about undefined, not NaN):

InputNumber emits undefined when the field is cleared, but the emit type never includes undefined unless the optional modifier is used.

Wthout v-model.optional, consumers get number | null (or number when T is inferred as number) — undefined is never part of the type. Yet clearing the field emits undefined at runtime regardless of the modifier. The type promises a value the component doesn't deliver, so downstream code silently assigns undefined (in my case it then dropped out of an outgoing request body unnoticed).

Minimal repro — no .optional, so onUpdate is typed (value: number) => void:

<script setup lang="ts">
const onUpdate = (value: number) => console.log(typeof value); // logs "undefined" after clearing
</script>

<template>
  <UInputNumber :model-value="30" @update:model-value="onUpdate" />
</template>

Type it, then clear the field → the handler receives undefined despite the number type.

Expected: either the emit type includes undefined (regardless of .optional), or the component shouldn't emit undefined without it.

Versions: @nuxt/ui@4.5.1, reka-ui@2.8.2.