[next] feat!: remove plugin#6349
Merged
Merged
Conversation
4 tasks
221b130 to
9084c0a
Compare
susnux
approved these changes
Jan 18, 2025
15 tasks
Antreesy
approved these changes
Jan 20, 2025
Signed-off-by: Grigorii K. Shartsev <me@shgk.me>
9084c0a to
49f23a9
Compare
Contributor
Author
|
Rebased, conflick in the changelog resolved |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
☑️ Resolves
Using plugin was not recommended in v8.
It is generally a bad idea to import all the components, resulting in a slow build of a large bundle.
Only used components should be imported and registered locally.
If a library user wants to avoid imports, they can use
unplugin-vue-componentsas an alternative even keeping tree-shaking.🏁 Checklist
nextrequested with a Vue 3 upgrade