fix: augment GlobalComponents in multiple vue modules #20144
Merged
Conversation
This file contains 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
KaelWD
reviewed
Jul 11, 2024
guibulator
force-pushed
the
fix-module-augmentation
branch
from
cb64e8c to
8235dec
Compare
guibulator
force-pushed
the
fix-module-augmentation
branch
from
8235dec to
933b9f8
Compare
johnleider
added
T: enhancement
johnleider
changed the title
johnleider
approved these changes
Jul 16, 2024
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
Starting with the VScode Volar extension
v2.0.20, Vuetify components when using auto imports will show asUnknownby IntelliSense.This module augmentation has been done in many projects so far, i.e: nuxt/nuxt#26541
The idea is to augment modules
vue,@vue/runtime-domand@vue/runtime-coreAfter augmenting all the proper modules, IntelliSense starts to work again.