Skip to content

feat(element-plus): add noStylesComponents for resolver options #471

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 20, 2022

Conversation

dblazhkun
Copy link
Contributor

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 #468
At 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

@dblazhkun dblazhkun requested a review from sxzz as a code owner July 20, 2022 11:22
@sxzz sxzz changed the title feat(element-plus): add optional noStylesComponents for resolver options feat(element-plus): add noStylesComponents for resolver options Jul 20, 2022
@sxzz sxzz enabled auto-merge (squash) July 20, 2022 11:24
@sxzz sxzz merged commit f43f073 into unplugin:main Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants