Search Terms
esnext, es6, es2015, module, tsconfig, tsconfig.json, difference, document
Suggestion
It would be great if this can be documented. On the face of it, the output for all three seems to be identical.
Related: It would also be nice to document why targeting module: "none" when your code is a module (ie. uses ES2015 imports/exports) generates CommonJS-compatible code instead of exporting to globals as "none" seems to imply.
Search Terms
esnext, es6, es2015, module, tsconfig, tsconfig.json, difference, document
Suggestion
It would be great if this can be documented. On the face of it, the output for all three seems to be identical.
Related: It would also be nice to document why targeting
module: "none"when your code is a module (ie. uses ES2015 imports/exports) generates CommonJS-compatible code instead of exporting to globals as "none" seems to imply.