When a reactive object is cleared (e.g. form = {}), Alpine's x-model effect fires _x_forceModelUpdate(undefined) on inputs still connected to the DOM. The mask plugin's wrapper around this function converts undefined to the string "undefined" via String(value), formats it to "", then calls el._x_model.set('') — which evaluates form.amount = '', resurrecting the deleted key with an empty value. In a Livewire context, this stale key gets sent back with the next server request, corrupting server-side state.

Steps to reproduce:

• Have an input with x-model="form.amount" and x-mask:dynamic="$money($input)"
• Set form.amount to a value (e.g. '5000')
• Clear the parent object: form = {}
• Observe that form.amount reappears as an empty string

Findings

The mask plugin wraps _x_forceModelUpdate (defined in x-model.js) to apply formatting before updating the DOM. The original function already handles undefined correctly for nested model paths (converts to '' and updates the input). The issue is that the mask wrapper runs String(value) and el._x_model.set(value) unconditionally — even when the value is undefined because the model path no longer exists.

Proposed solution

Add an early return in the mask wrapper when value === undefined. This skips the formatting/write-back path entirely and delegates to the original _x_forceModelUpdate, which already handles undefined properly. Crucially, el._x_model.set() is not called, so the deleted key is not recreated.