Add support for custom babel configuration #44
Merged
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
|
Hey @marvinhagemeister, is there any option that this pull-request could be reviewed? |
marvinhagemeister
approved these changes
Mar 29, 2022
|
Hi, sorry to bring this to a Pull Request but I'd like to change the |
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.
I currently ran into an issue that legacy-decorators are not supported (same as #43) and I fixed it by adding the
@babel/plugin-proposal-decoratorsand@babel/plugin-proposal-class-properties.Unfortunately I had to inject these plugins directly into the packages source code. So I thought it would be nice to have an option to change babel config in vites config file.