-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Extend hasPlugin
to accept plugin-configuration array pairs
#13982
Conversation
ab1035a
to
e7c71dc
Compare
d8171de
to
f387fa7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
...l-parser/test/fixtures/esprima/es2015-export-declaration/invalid-export-default/options.json
Show resolved
Hide resolved
packages/babel-parser/test/fixtures/flow/expect-plugin/export-interface/options.json
Outdated
Show resolved
Hide resolved
f387fa7
to
eecabc6
Compare
This also allows expectPlugin and expectOnePlugin to give better error messages. For example: > This experimental syntax requires enabling the parser plugin "pipelineOperator". > This experimental syntax requires enabling the parser plugin ["pipelineOperator", {proposal: "hack", topicToken: "^^"}]. See babel#13973 (comment).
eecabc6
to
af9aaa1
Compare
The parser test262 tests were failing because on some Node.js versions I don't know why it's not failing on |
hasPlugin
to accept plugin-configuration array pairs
See #13973 (comment).
CC: @JLHwung.