Support for options in data-plugins attribute to fix #8831 #11594
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.
It is currently not possible to use plugins that require options when injecting plugins using the
data-plugins
attribute. For instance, currently is not possible to make the proposal-pipeline-operator working with code similar to:The problem is that this plugin and others require additional options, while they can be specified explicitly under a
Babel.transform()
, it's not possible to inject them directly with thedata-plugins
attribute.This PR adds support for plugins with options specified as
plugin-nane{option1=value1,option2=value2}
which, for instance, enables specifying the requiredminimal
option to the pipeline plugin: