I wouldn't use ^ in any of these versions since you never know if we'll make any final breaking changes that may or may not affect this.

The parser doesn't have * anymore. Some parser plugins conflict with others, so we require an explicit list of parser plugins to enable.

Did this get missed?

Oh we renamed, which is why the versions don't match. It's just @babel/parser now.

interesting, switching to @babel/parser seems to break shebang support:

  1) statement.yaml/shebang code
       covers line and one branch:
     AssertionError: Error compiling
1: #!/usr/bin/env node
2: 
3: var x = args[0] > 5 ? args[0] : "undef";
4: output = x;
5: 
Invalid or unexpected token: expected false to be truthy

is there an additional plugin that's required? seems to be a regression from [email protected].

Hmm interesting. I'll take a look. I did land a change for shebang handling, but I can't tell from that error if it's a bug, or just not expecting the new logic.

interesting, it doesn't seem to be shebangs in general, this works:

// #!/usr/bin/env node
var x = args[0] > 5 ? args[0] : "undef";
output = x;

but this doesn't work:

#!/usr/bin/env node
var x = args[0] > 5 ? args[0] : "undef";
output = x;

update: I only seem to have one test that uses a shebang.

Okay, I see what's up. In Babel 6 the interpreter directive was basically silently converted into a LineComment in the AST.

In 7.x, we changed is that now if your input file had a shebang, it actually gets passed to the code generator and generated as a shebang again. That's causing problems for your logic here:

Maybe your tests should just strip directives in that logic?