-
Notifications
You must be signed in to change notification settings - Fork 111
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
kyt .babelrc preset POC #250
Comments
gonna take a crack at this 🙏 |
i've got a POC going here--feel free to poke around, though realize it's very preliminary. the most important questions seem to be (in descending order of difficulty):
(this branch also starts to outline a direction we could go for #240, using a pretty common pattern--creating a |
Closing this - we'll track from #322 |
Internally, there's been some discussion about creating a kyt .bablerc preset. As a standalone package, the preset could be configured in a user's .babelrc file which will give them a convenient way to extend kyt's defaults or start over from scratch. Another idea, if it would work, is to break out the React related stuff into a separate preset so that a user could easily opt in or out of the React defaults.
The advantages to this approach are 1) it supports a standard .babelrc file which is easier for users to customize and 2) by giving users presets, kyt can encapsulate and manage most of the configuration. One problem with this approach is the use case where a user would need to override/remove a plugin or preset in the kyt presets. In that case, the user would most likely have to go without the kyt preset and roll their own configuration.
I'd love to see a POC that supports a user .babelrc with a
kyt-core-preset
andkyt-react-preset
. Each preset could be a separate package but included in the kyt repository.The text was updated successfully, but these errors were encountered: