matey-jack / http-link-header Goto Github PK

Benefits:

• users get autocomplete
• easier to maintain

use deno bundle to generate a JavaScript file to be imported in the Browser (and other non-TS environments).

title of issue says it all, using the body only to collect info on how to do it.

https://2ality.com/2019/10/hybrid-npm-packages.html seems to have the clearest explanation, but the core point is:

• to be compatible with older versions of Node, we need to ship CommonJs and ESM versions of the JavaScript sources in the same package
• it doesn't give any hints on how to build such packages, especially in our case of a project that does not use rollup or a transpiler. npm publish just publishes the source

This example project actually seems nice: https://github.com/dandv/local-iso-dt

• edit your code as ES module and use babel to create a CommonJs version for backward compatibility
• package both as described by duality above
• if you write a new package, make it ESM only, because new projects can directly use that
• is it so that TypeScript compiler or other tool in its ecosystem allows a CommonJs module to be imported via ES syntax? then maybe many users do that already and we can just switch to only support that – but I guess for any project with a lot of users, it would just break updateability for some people

other info for context, but doesn't seem to have the simplest information:

• https://blog.logrocket.com/es-modules-in-node-js-12-from-experimental-to-release/
• https://stackoverflow.com/questions/29738381/how-to-publish-a-module-written-in-es6-to-npm
• https://github.com/nodejs/modules/blob/master/doc/unflagging-announcement.md (has a dead link to a "Dual CommonJS/ES Module Packages" section of the next doc)
• https://nodejs.org/api/esm.html
• especially: https://nodejs.org/api/esm.html#esm_compatibility_with_commonjs_only_versions_of_node_js