-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Configurable Babel Plugins #2772
Labels
feature
This is not a bug or issue with Docusausus, per se. It is a feature request for the future.
Comments
Huxpro
added
feature
This is not a bug or issue with Docusausus, per se. It is a feature request for the future.
status: needs triage
This issue has not been triaged by maintainers
labels
May 19, 2020
yangshun
removed
the
status: needs triage
This issue has not been triaged by maintainers
label
Jun 5, 2020
This is definitely something we want to add support for, it should work similar to Next.js' Babel config customization. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature
This is not a bug or issue with Docusausus, per se. It is a feature request for the future.
Posted in v2 feedback as well : https://docusaurus-2.netlify.app/feedback/p/configurable-babel
🚀 Feature
Being able to configure/add babel plugins such as optional chaining and Flow.
Have you read the Contributing Guidelines on issues?
Yes
Motivation
I'm not sure if it's not supported or just not documented (I looked up both v1/v2 doc but wasn't able to find it). I didn't even find what exact babel presets are used from the docs and have to look into the source code.
It just doesn't feel right that Babel is used but not configurable. It's been a norm for JS developers tweaking this very fundamental tooling.
This also help with people asking for Flow support since they can just do it on their own. I found TS has been added as part of the default presets via #2310, which means people not using TS w/ docusaurus is wasting their time/space for this.
The text was updated successfully, but these errors were encountered: