- Will not work as
file://because browser throws an error. Workshttp://andhttps:// - Will work with
window., but this is bad practice when the file is anticipated to be a module. - Namespace imports are ignored (i.e.,
import * as UMD from './umd.js', UMD is ignored.- We believe this is because it is directly exported by the module to globals, so there is no export to import by the importing module.
- Modules must use the export that's in the UMD section.
- From the exporting file:
factory(global.ExampleUMD = {})but be referred to asExampleUMD
- From the exporting file:
- Will work when being server over
file://,http://andhttps://. - Must use
window.ExampleUMDand cannot use the export directly, i.e.ExampleUMD. - Cannot use
importin any Javascript. - In the UMD export, the
global.becomeswindow.for the browser.- This is why the UMD library doesn't ever refer to
window.
- This is why the UMD library doesn't ever refer to
- UMD declaration must be at the end of the file. This is unlike the unencapsulated version which allows the declaration and exports at the beginning of the file.
Useful examples and documentation on UMD:
Blogs: https://jameshfisher.com/2020/10/04/what-are-umd-modules/ https://jakearchibald.com/2017/es-modules-in-browsers/ https://salomvary.com/es6-modules-in-browsers.html
Issues: systemjs/systemjs#2064 systemjs/systemjs#1933
Repos: https://github.com/umdjs/umd/
Other: https://stackoverflow.com/a/63751410/15147681 https://github.com/paulmillr/noble-secp256k1/releases/tag/1.6.3 evanw/esbuild#507 (comment)