would you consider providing a pure es module?

[mreinstein]

In my own projects, I'm starting to explore using absolute URLs with no package manager and no bundling step.

I'd love to be able to import segseg directly in my projects. For example:

import segseg from 'https://cdn.jsdelivr.net/gh/tmpvar/segseg@0.2.2/segseg.js'

where the file would basically just look like:

export default function segseg (out, p1, p2, p3, p4) {
    // ...
}

no legacy module systems, no window globals, just a plain old function that uses the new es module system. :)

A working example of this in one of my projects: https://cdn.jsdelivr.net/gh/mreinstein/collision-2d@master/src/segment-segment-overlap.js

[tmpvar]

Not apposed, but what is the node.js support story for this? Do we need to rename the file extension or something?

[mreinstein]

I guess it depends on how much compat we want to keep. I think for node v12+ it might just just be a matter of setting "type": "module" in package.json (see https://nodejs.org/dist/latest-v12.x/docs/api/esm.html#esm_package_json_type_field)

It sounds like there are some "hybrid" package strategies to support both commonjs and esm formats at the same time but these seem fraught with complications. Might just be easier to make a clean break and say the next version of segseg is esm/ node v12+ only?

another option is we could have segseg.js be the pure es module version, and have a build step that turns segseg.js -> index.js and keep pointing at index.js in package.json?

[tmpvar]

Might just be easier to make a clean break and say the next version of segseg is esm/ node v12+ only?

Yep, let's do it!

[mreinstein]

closed via 565f1da