feat(element-plus): add noStylesComponents for resolver options #471
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
With the release of new versions of Element Plus, it is possible that components that do not have their own style files may appear, which causes an error when trying to resolve non-existent style files. Right now, there seems to be only one such component:
ElAutoResizer
. It has been fixed in #468At the same time would be handy for getting around such blocking cases quickly without having to wait for a new release of
unplugin-vue-components
.On the other hand, it seems useful to keep a list of already known components without styles inside the resolver.
In this PR I suggest combining support for both options.
Linked Issues
element-plus/element-plus#7933