Oh I'm sorry, I thought you were referring to an error when adding defineModel, so I tried to remove it and found that the error disappeared, which led me to discover another issue...

When there are no events on a component, its $emit will be inferred as any event function.

As you said, this is the same issue with fallthrough attributes. Regardless of whether there is a defineModel, it should report an error.

Should it report an error? My understanding is that <MyComponent @click="onClick" /> is the correct way to add a native click event listener now that .native modifier has been removed

IMO in strictTemplates, just as unknown props should report errors, the listening for events is similar to assigning values to the 'onXxx' prop, and it should also apply the rules of the former.

My understanding is that <MyComponent @click="onClick" /> is the correct way to add a native click event listener now that .native modifier has been removed. Though I do also see the argument for not allowing this with strictTemplates and only allowing events that are defined with defineEmits. The main issue is that it is currently not consistent (only some cases it causes error)

Maybe it's possible to add an option to vue language options for globally allowed event listeners, kind of like htmlAttributes/dataAttributes settings?

What I'd fixed is exactly the inconsistency you mentioned.

The reason of <MyComponent @click="onClick" /> is the correct way to add a native click event listener, is because it passes click events to the root element of the component as a "fallthrough attribute", rather than the component itself containing the attribute; So when strictTemplates is enabled, it should report an error. This does not mean that this way of adding events is incorrect.

And what #4103 want to solve includes this issue.