Releases: nuxtlabs/nuxt-component-meta
Releases · nuxtlabs/nuxt-component-meta
v0.13.0
- feat: introduce component parser utility (#84) (3d47c20)
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)
v0.10.0
- chore: upgrade deps (95f461d)
- fix: export module types (b6d3e47)
- feat:
include
option to generate components meta (6807b69)
- ci: use pkg-pr-new (9e638d1)
v0.8.2
- fix(events): do not remove top level external types (98e9719)
v0.8.1
- fix: ignore vue runtime types (40aea05)
- fix(build): remove
declarations
to reduce chunk size (09a96cd)
v0.8.0
NOTE Version 0.8.0 uses vue-component-meta@^2.1.6, which may produce slightly different results compared to [email protected]. For instance, optional types will now include | undefined in their definitions. For example, enable?: boolean will be represented as enable?: boolean | undefined.
- chore: fix module build (4e27090)
- chore: upgrade deps (940fe97)
- fix: use
mlly
rather than deprecated kit cjs util (#69) (72b989c)