Updated. Also, for RegExp constructors with 0 arguments, this would currently throw at const pattern = evals[0].value;. Catching this case at pseudo-compile time is not terrible, but should this behavior be changed/documented?

Yeah, let's definitely add a check for 0 arguments. It should transform to /(?:)/ (empty non-capturing group). Also, I would rename evals to evaluatedArgs for clarity.

Updated to gracefully handle empty RegExp constructions.

Thanks!

@hzoo @loganfsmyth @danez do we want to also update babili preset?

yeah if want to add it now - we'll need the package.json for this package + adding it to the preset package.json if we do

@shinew Let's do it. That way we could also see the impact of this plugin on performance with our benchmark.