with statement not supported about civet HOT 3 OPEN

Emitting "use strict" could be default. A notStrict or sloppy parse option would be great then. If export or import are used anywhere the "use strict" should be omitted either way I think.

from civet.

I didn't realize that TypeScript allowed with. Given this, I could see supporting it, for compatibility sake...

TS does not support it, oops! Though it would still be a JS compat feature.

from civet.

I think we've been generally assuming strict mode. I've added a section about this in the comparison page.

I didn't realize that TypeScript allowed with. Given this, I could see supporting it, for compatibility sake...

A related question is whether we should emit "use strict" in our JS output. Perhaps we should by default, but there's a way to request omitting it? Of course, it's implicit in ESM, so it's less important these days, but it's probably safer to include it unless the user needs e.g. implicit globals. Related to TypeScript's alwaysStrict setting.

from civet.