V3 changes

[nfriedly]

I'm thinking about the changes I'd like to see in a version 3. The two big ones that I'd like to get in are:

• Automatically run splitCookieString() when when the input has a string for the header value (not an array)
  • Probably with a new option to explicitly always/never run it, and only decide based on input when it's unset
• Offer an ESM version of the library

Things I'm considering but haven't yet decided one way or the other:

• Ship both ESM and CJS variations or make 3.x exclusively ESM?
  • Possibly via https://github.com/wessberg/cjstoesm in a pre-commit hook to build the esm version
• Convert the library to typescript?
  • Run tsc twice for ESM and CJS, although TypeScript seems to break the "naked" require in CJS.
• Split parse() into parseToArray() and parseToMap() to make for simpler typing? (Or support all 3?)
  • I think I won't do this one. I hadn't realized typescript supported overloaded signatures, so I can make the typing work correctly with a single function.

[bytesnz]

I reckon for the splitting, just adding an additional function of parseToMap() would be good (and keeping the current parse() as is. I'm sure quite a few people will be currently doing:

const cookies = setCookieParser.parse(setCookieParser.splitCookieString(res.headers.get('set-cookie'))).reduce((obj, c) => { obj[c.name] = c; return obj})

Just adding the parseToMap() instead of replacing parse() with parseToArray() and parseToMap() will mean no changes required when upgrading.

[nfriedly]

There's already a built-in map option that does basically that internally. I was thinking it would be difficult to represent in TypeScript, but it turns out that it's not so hard after all - TypeScript can statically determine the output type based on the input options.

If I was starting over from scratch, I'd probably do like you said, but since the existing API is there and doesn't seem to be causing any trouble, I'm going to avoid an unnecessary breaking change leave it as-is.

[thib3113]

Hello, just a note about CJS/ESM .

yes ESM is great, but shipping only in ESM will force other lib to migrate to ESM to (wich can be a really hard work) ... so, please keep CJS/ESM .

Else, I've done multiple libraries that export CJS/ESM, here is an example, in general I'm using esbuild to build it (because I can create a script to call it, but other options exists) (and if he can compile typescript really fast, he doesn't typecheck, so when I want to typecheck I call tsc --noEmit) .

Here is the little esbuild script : https://github.com/thib3113/node-crowdsec/blob/main/packages/crowdsec-client/esbuild.js

I just setup up some options, and create links file that will reexport another parts (I also generate a pkg.ts to export the current version, but you can remove this) .

and finally some configs in package.json : https://github.com/thib3113/node-crowdsec/blob/main/packages/crowdsec-client/package.json#L5-L8 + https://github.com/thib3113/node-crowdsec/blob/main/packages/crowdsec-client/package.json#L27-L39
( using type = module will change your package to module, so you will need to use import, stop using require, and import file with extension .... but because I use .cjs and .mjs you can decide to don't use module type ) .

And here is the result : https://www.npmjs.com/package/crowdsec-client?activeTab=code

about size, yes using CJS and ESM consume more space ... but, if you use a bundler for your code, it will remove the unused files, so in general will use the ESM files, and remove the cjs . npm show a size of 275 kB, but when it was bundled, bundlephobia return a size of 15kB

[nfriedly]

I might look into that more, thanks.