fix(InputNumber): work uncontrolled with only a default value (nuxt/ui@2d4782b)

[IgorShevchik]

Port of nuxt/ui@2d4782ba — third of ten in this run.

The defect, and it was live here

useVModel(props, 'modelValue', emits, { defaultValue }) kept its own copy of the value, and that copy was bound to NumberFieldRoot's model-value. With only a defaultValue and no v-model, reka has internal state of its own — and the two disagreed. The field stepped off the wrapper's copy instead of off reka's, so an uncontrolled InputNumber did not increment at all.

Removing the wrapper alone trades that for a different bug, which is why the fix has a second half. Reka writes update:modelValue on every write — blur, Enter, stepping at a bound — whether or not the value moved, and with useVModel gone nothing absorbs those. So onUpdate gains an equality guard and emits by hand:

if (value === props.modelValue || (value == null && props.modelValue == null)) {
  return
}

emits('update:modelValue', value as ApplyModifiers<T, Mod>)

The second clause is not redundant: undefined and null are different values but the same emptiness — the .optional modifier produces the first, a caller supplies the second. useForwardProps(…, emits) loses its second argument for the same reason, so the root cannot re-emit what onUpdate now owns.

Applies verbatim. Our pre-image is upstream's at all five sites, eslint-disable comment included, useVModel appears nowhere else in the file, and the selectors and imports the new tests need (data-slot="increment", flushPromises, test) were already present.

Verified against the pre-image, not assumed

With the component reverted and upstream's four tests kept, all four fail; with the port, all pass. So this fixes a defect that was live in this fork rather than a theoretical one.

Mutations, and the counts separate the two halves of the fix:

mutation	result
drop the emits('update:modelValue', …) call	14 red
drop the equality guard entirely	6 red
keep only value === props.modelValue, drop the == null clause	2 red

The last row is the one worth having: it shows the == null clause is load-bearing and covered, rather than defensive padding no test would miss.

Bookkeeping

• .sync/nuxt-ui.json — cursor ebd4adfc → 2d4782ba, entry added; and ebd4adfc reconciled to chore(deps): update non-major dependencies, pin happy-dom (nuxt/ui@ebd4adf) #551 / d57db682, per §6 step 4 (the next port closes the previous entry, so only the last needs a PR of its own).
• .sync/dep-parity.json — refreshed at the new cursor.
• .sync/log/2d4782ba….md — the long-form reasoning.

Local gate green: lint · typecheck · build (3.87 MB) · test (347 files, 7895 passed, 6 skipped) · test:module · repl:build.

Still ahead

Seven upstream commits: 042bf3b7 (tiptap deps), 7224333b (upstream's own release), 5fd94e13 (theme editor docs), 9076ca2d (virtualizer size fallback), and three docs-only commits.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JS8ypVfQSFzYVZzkTHhURb

---

Generated by Claude Code