Skip to content
This repository has been archived by the owner on May 14, 2021. It is now read-only.

Support to specify parser plugins #229

Merged
merged 2 commits into from
Oct 4, 2018
Merged

Support to specify parser plugins #229

merged 2 commits into from
Oct 4, 2018

Conversation

chinesedfan
Copy link
Member

Fixes #228 and solved #183 in another way.

Now users can use options.parserPlugins to custom plugins to babel.

@coveralls
Copy link

coveralls commented Oct 2, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling d27a9e3 on parser-options into 3ca7c63 on master.

@chinesedfan chinesedfan merged commit 5e1485b into master Oct 4, 2018
@chinesedfan chinesedfan deleted the parser-options branch October 4, 2018 04:25
@rylek90
Copy link

rylek90 commented Oct 17, 2018

Is there an option not to rewrite whole array but rather concatenate with default one?
Can we work towards passing whole Babel configuration in the future?

@chinesedfan
Copy link
Member Author

@rylek90 See #231. Please feel free to send a PR if you would like do that.

@rylek90
Copy link

rylek90 commented Oct 17, 2018

@chinesedfan thanks, I will take a look at it if I'll have some free time 🙌

@jeffcatania
Copy link

Is there any documentation on how to use this option?

@chinesedfan
Copy link
Member Author

@jeffcatania I am afraid not because #231 should be the better way. You can use the test file(options.test.js#L211) as a Node API example now. Following links may
also help you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants