-
-
Notifications
You must be signed in to change notification settings - Fork 7k
feat(package): add unimport
presets and unplugin-vue-components
resolvers
#21129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
info.push({ | ||
pascalName: component, | ||
kebabName: toKebabCase(component), | ||
export: component, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we add component prefix support here?
At this point I want to create also custom vuetify styles plugin using unplugin, this way we can also support other bundlers "for free" (🤞 ). I guess at this point this PR should be moved to loader repo as a new package with 3/4 sub-package exports, unimport preset, unplugin-vue-components resolvers, unplugin styles plugin (default) and maybe utils with some exports from the utils.ts module here. /cc @KaelWD @AndreyYolkin Kael, we should move the repo to pnpm workspaces using pnpm catalogs (VSCode pnpm lens plugin), 30 minutes to add dependencies to the new package ;) |
New @unvuetify/monorepo repository created and initial packages versions published, we'll have some more Vite/Nuxt utilities in this new repository |
Description
Last PR to include
node
stuff: this PR can be closed once merged #20536Both subpackage exports ESM-only, if you want to use dual ESM/CJS ping me...
I need to do some tests...
dev-pr-21129
branchunplugin-vue-components
working: https://github.com/userquin/check-vuetify-unplugin-vue-components-2 (the directives works only via unimport preset)Markup:
NA