v0.15.0

• lit: fix (f0d5da9)
• chore(deps): update all non-major dependencies (#91) (8dfae0d)
• chore(deps): update actions/checkout action to v6 (#100) (8ebcb9b)
• fix: better type detection and exclude duplicate components (0d125c6)
• feat: introduce overrides option to modify metadata (#99) (fa5bf4b)
• chore(deps): update actions/checkout action to v5 (#92) (7f246fc)
• chore(deps): update actions/setup-node action to v6 (#96) (760ea87)

v0.14.2

• feat: introduce no-schema option to drop schema form meta fields (#98) (32d57eb)

v0.14.1

What's Changed

• feat(module): add component-meta:schema hook by @benjamincanac in #95

Full Changelog: v0.14.0...v0.14.1

v0.14.0

• fix: ensure checker exist on dispose (#88) (bff6616)
• fix(propsToJsonSchema): drop function props & better enum support (3165cb4)

v0.13.1

• fix: exclude SVG components (#85) (8c7deac)

v0.13.0

• feat: introduce component parser utility (#84) (3d47c20)

v0.12.1

• fix: filter events from props (a844f93)
• chore: upgrade deps (86a33a2)

v0.12.0

• perf: include less files in typescript checker (#82) (8644efb)

v0.11.0

• feat: use previous meta and prevent duplicate parse (#79) (f9f18b6)
  On the second run of the development server, nuxt-component-meta uses previously generated metadata to prevent re-parsing the same components.

v0.10.1

• fix: prevent duplicate hash generation in Nitro OpenApi (4f5fb93)
• fix(cli): use importModule to generate component-meta output (#77) (4bf5ed9)