During modularization of dotnet.js we adopted CommonJS format as transition step to ES6 modules.
Build flag WasmEnableES6 enables us to produce either CommonJS or ES6 module.
Are there future use-cases for CommonJS module format ?
If not we could drop the WasmEnableES6 flag and simplify build and test landscape.
We should also drop CommonJS samples.
Note we have disableDotnet6Compatibility: false switch which exports the MONO and BINDING namespaces into global namespace, in same way how Net6.0 did. This would continue working with ES6 too.
During modularization of
dotnet.jswe adopted CommonJS format as transition step to ES6 modules.Build flag
WasmEnableES6enables us to produce eitherCommonJSorES6module.Are there future use-cases for CommonJS module format ?
If not we could drop the
WasmEnableES6flag and simplify build and test landscape.We should also drop CommonJS samples.
Note we have
disableDotnet6Compatibility: falseswitch which exports theMONOandBINDINGnamespaces into global namespace, in same way how Net6.0 did. This would continue working with ES6 too.