![renovate[bot]](https://avatars.githubusercontent.com/in/2740?v=4&s=144)
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4&s=144)
![dependabot-preview[bot]](https://avatars.githubusercontent.com/in/2141?v=4&s=144)
Community health
2 of 6 standards met
37
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Active · Last activity 5m ago
See all on GitHub →
## Summary resolve component registration names from the app-level component registry when matching keep local component registration names as the first priority, then fall back to global registrations and existing script setup/name inference add a regression test for components registered by a plugin under a public alias that differs from the component's internal name Root Cause only inspected the parent component's local option. Components installed through plugins or libraries with were resolved by Vue at runtime, but Vue Test Utils could only see the component's internal . As a result, did not match unless the internal component name happened to be the same. Fixes #2541. Validation
Recent fixes
Describe the bug always returns for the element and its descendants when there is no attribute. The is visible in the browser even when is not open. is visible, but any other children than are hidden when the attribute is not present. To Reproduce Given component : Expected behavior Additional context A text node can also be a direct child of . That direct text node is hidden when the attribute is missing; Used test-utils version 2.4.6
This PR addresses https://github.com/vuejs/test-utils/issues/2626. The issue is that element behavior is inconsistent with the real browser. I verified this in a real browser, and the issue still occurs. Reproduction: https://stackblitz.com/edit/vitejs-vite-qxxwzrgz?file=src%2Fcomponents%2Ftests%2FDetailsComponent.test.ts
Describe the bug currently depends on an older version of , which in turn depends on an older version of glob. Recent versions of (v2.x) have updated their dependencies to use a newer, non-vulnerable version of . Because of the current dependency chain, projects using may report transitive vulnerabilities during security scans (e.g. npm audit, GitHub Dependabot, Snyk). Updating to the latest compatible 2.x release would help eliminate these transitive vulnerabilities for downstream users. See https://github.com/beautifier/js-beautify/releases/tag/v2.0.1 Expected benefit** Removes transitive vulnerabilities related to older versions of glob. Improves security posture for projects using @vue/test-utils. Reduces noise from dependency scanning tools. Reproduction https://stackblitz.com/github/vuejs/create-vue-templates/tree/main/typescript-vitest?file=src%2Fcomponents%2F__tests__%2FHelloWorld.spec.ts Expected behavior Environment Additional context _No response_
Structured data for AI agents
Repository: vuejs/test-utils. Description: Vue Test Utils for Vue 3 Stars: 1154, Forks: 287. Primary language: TypeScript. Languages: TypeScript (95.2%), Vue (4.6%), JavaScript (0.1%). License: MIT. Homepage: https://test-utils.vuejs.org Open PRs: 10, open issues: 26. Last activity: 5m ago. Community health: 37%. Top contributors: renovate[bot], dependabot[bot], lmiller1990, cexbrayat, dependabot-preview[bot], xanf, dobromir-hristov, afontcu, freakzlike, pikax and others.