feat: pref build components library production #89
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
✅ Deploy Preview for idyllic-kitten-f7a0d0 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for spectacular-wisp-fcff7b ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
production: |
zyyv
approved these changes
Oct 27, 2022
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.
Using volar's vue-tsc can avoid a lot of trouble caused by the vue component build. There were some bugs in the previous
vite-plugin-dtsbuild, for example, it could not properly generate the props for the component, for example, it set the type to any whenever a problem was encountered. I think the current scheme has been a relatively perfect package component library scheme.By the way,I hope you can try it locally, I hope you like it. One more thing, we should be careful about updating the dependent version to the latest one, as this may result in API incompatibilities between some frameworks or plug-ins, resulting in some errors.