Intent to ship browser packages as ES Modules exclusively

[fregante]

npm modules never end up in the browser without a compilation/bundling step¹ and since all bundlers now support ES Modules (natively or via esm package) it makes no sense to keep shipping Common JS modules, which have compatibility issues with ES Modules and different expectations for multiple exports.

Browser + node packages

Only ship CommonJS, since they're supported everywhere and most bundlers also have a compatibility layer to enable importing them, which correctly selects the "default" CommonJS export.

Browser-only packages

Only ship ES Module, since the only reason to have CommonJS modules at the moment is to support older Node versions.

This will change as Node finalizes ES Module support and is widespread enough to completely and finally drop CommonJS.

---

¹ If you want to use one of my npm-only modules directly in the browser, I provide a packd link that makes a bundle for you, example: fregante/webext-options-sync@37d606a