fix(vue3): ensure 3rd party components directly imported in script setup do not show up as Anonymous Component
in devtools
#2020
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
When we import and use a 3rd Party component in
<script setup>
like in the following example, it will show up as<Anonymous Component>
in devtools.This PR makes devtools fall back on the internal
__name
property added by@vitejs/plugin-vue
(this name is derrived from the filename) if no explicit name has been set.Additional context
I'm not sure how to add a test case for this. But I hope the fix is trivial enough to do without one.
What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123
).