fix: stub directives registered with a camelCase or kebab-case name - #2982

Summary

global.stubs only replaces a directive when the component registers it under exactly the name in the stub key minus the v. If the directive is registered as myDirective or my-directive, vMyDirective is ignored and the real directive keeps running, even though Vue resolves v-my-directive to those registrations too:

const Component = {
  template: '<div v-my-directive>text</div>',
  directives: { myDirective: MyDirective }
}

mount(Component, { global: { stubs: { vMyDirective: true } } })
// MyDirective still runs

Lowercase keys are the common Options API style. The Vue docs register their example as directives: { highlight } for v-highlight, which vHighlight cannot stub today. A stub key is only treated as a directive when it is v followed by an uppercase letter, so no stub key can match such a registration.

Root cause

createStubDirectivesTransformer (src/vnodeTransformers/stubDirectivesTransformer.ts) picks the directives to replace with Object.keys(type.directives).filter(key => key in directives). getDirectivesFromStubs strips the leading v from the stub key (vMyDirective becomes MyDirective), so only a registration named exactly MyDirective matches. Vue's resolveAsset looks a template directive up by its name, the camelized name and the capitalized name, so myDirective and my-directive are equally valid registrations for v-my-directive.

Fix

Compare the registered name with the stub names using matchName, the helper the component stubs already use. The directive is still replaced under the key it is registered with. PascalCase registrations behave as before, and vMyDirective: false still opts out.

Validation

I added two regression tests to tests/mountingOptions/global.stubs.spec.ts. One stubs a camelCase registration with a stub directive. The other replaces a kebab-case registration with the true noop.

I could not install the project's dependencies in my environment, so I have not run vitest, lint, format-check or the type checks locally. Instead I loaded Vue 3.5.44's runtime-core and compiler-dom from source, using the DOM-free @vue/runtime-test renderer. I then ran this repository's stub transformers on the same templates as the directives tests. On main, both new cases render the real directive's class. With this change they render the stub, and the existing directive cases give the same output as before.

🤖 Generated with Claude Code