JavaScript Module shim for UMD bundles about umd HOT 1 OPEN

Why not having window.exports = {} in the shim instead of import './my-module-setup.js'?

The shim depends on the UMD template:

• commonStrict.js (and commonStrictGlobal.js) uses exports
• returnExports.js (and returnExportsGlobal.js) uses module.exports
• amdWeb.js (and amdWebGlobal.js) uses only define()

In case the module has dependencies, require() must be provided in the shim as well.

🤔 For own modules maybe writing them as es6 (with import and export statements) and converting to UMD is simpler (or using esm for nodejs). But for 3rd party libraries, shims could still be helpful.

from umd.