feat(component-meta): add component name and description fields

[Copilot]

Enables extraction of component-level metadata (name and description) from Vue components for tooling like web-types.json generation.

Changes

• Interface: Added optional name and description fields to ComponentMeta
• Extraction logic:
  • name: Reads from component options name property (Options API)
  • description: Parses JSDoc comments on export statements using ts.getJSDocCommentsAndTags()
• Utilities: Extracted shared AST traversal functions (getComponentNodeFromAst, getComponentOptionsNodeFromComponent)
• Tests: Added coverage for Vue/TS components with/without name and description

Usage

const meta = checker.getComponentMeta('./MyButton.ts');

console.log(meta.name);        // 'MyButton'
console.log(meta.description); // JSDoc comment from export

Limitations

• JSDoc descriptions only extracted for .ts/.js files (Vue SFCs not supported due to TypeScript virtual file processing)
• Both fields return undefined when not present

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• plugins.dprint.dev
  • Triggering command: /home/REDACTED/work/language-tools/language-tools/node_modules/.pnpm/dprint@0.50.0/node_modules/dprint/dprint /home/REDACTED/work/language-tools/language-tools/node_modules/.pnpm/dprint@0.50.0/node_modules/dprint/dprint fmt (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add component description and name to vue-component-meta</issue_title>
<issue_description>### What problem does this feature solve?

I am using vue-component-meta to extract meta data from my components to then generate web-typers.json so that IntelliJ will correctly offer data on hover and the autocomplete works. This works great for what is currently offered, but I would like to also get the component description that can be added by using a jsdoc string above the export default.

Currently I do that with a workaround, namely reading the file from disk, parsing and compiling it with the vue-compiler-sfc, then throwing the resulting js code into a jsdoc extraction script and it seems like such a waste to go through all that, when I see that vue-component-meta already deals with exports in a private function.

What does the proposed solution look like?

I propose to add a name and a description entry on the root of ComponentMeta to also expose the "global" meta data for the component. Name can technically be inferred from the file name, but with the option of actually setting a name in the options api it would be nice to also expose that.

{
  name: 'MyComponent',
  description: 'My awesome component description',
  type: [Getter],
  props: [Getter],
  events: [Getter],
  slots: [Getter],
  exposed: [Getter]
}
```</issue_description>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

• Fixes Add component description and name to vue-component-meta #5693

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.