Use babel standalone package #723
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
Though it isn't recommended, MDX often finds itself being used on the client or other environmentts where bundler configuration might not be customizable. This switches to babel standalone to allow for better support for those scenarios. Before actually merging this it might be worthwhile to add some benchmarking to ensure that this doesn't introduce a performance regression (I'm not sure how standalone works internally). --- Closes #704
|
This pull request is automatically deployed with Now. Latest deployment for this branch: https://mdx-git-babel-standalone.mdx.now.sh |
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.
Though it isn't recommended, MDX often finds itself
being used on the client or other environments where
bundler configuration might not be customizable.
This switches to babel standalone to allow for better
support for those scenarios.
Before actually merging this it might be worthwhile to
add some benchmarking to ensure that this doesn't introduce
a performance regression (I'm not sure how standalone
works internally).
Closes #704