chore(readme): link to vuetify plugins #620
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I would actually happy we directly remove the Vuetify resolver in favor of the official plugin |
|
We don't currently have any support for v2+vite so it's still somewhat useful. |
It is actually, for most of us, the main scenario as Vuetify 3 with Vue 3 support has not yet reached feature parity with Vuetify 2 whereas vite has become the preferred (if not only) choice for many third-party tools / librairies in the Vue ecosystem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We've been getting lots of support questions from people using unplugin-vue-components, our own build plugins use a map which is more efficient and avoids matching components that don't exist in the library.