feat: add a components api to allow manual detection in frameworks #329
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
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 📖
This pull requests adds an
apitounplugin-vue-components, allowing it to be used programmatically.The benefit of exposing an API is that frameworks can easily integrate with this plugin and leverage any component resolvers that the user has already configured, providing a consistent DX.
Examples 📝
îles uses this api to resolve components inside islands.
It also can conditionally inject imports based on whether the islands are SSR-compatible. This is an advanced use case that wouldn't be possible if the user imported components manually.