Publishing ESM

[43081j]

Most consumers are running in node (without a bundler) so this has been fine so far as CJS

However, it is the only one of the many alternatives that doesn't ship modern modules. So it would be good to solve that

To avoid having to ship a dual package (which would mean doubling the package size), my suggestion is basically:

• maintain a 1.x branch which ships as CJS
• maintain main which ships as ESM
• all changes go into both branches until a majority of consumers are using the ESM version

Id be happy to help out if needed

[crutchcorn]

Something like TanStack Config, suggested here: #59 (comment)

Would fix this and allow dual-publishing. I can make a PR for this if wanted

[43081j]

i'd be cautious of publishing a dual package, especially since require(esm) will soon be in all LTS node versions and typescript

if it was up to me, i'd still opt for going esm-only and keeping any CJS/older-node consumers on the old version (but backporting fixes if we ever needed any). its a fairly simple package so i can't see many fixes being needed, if any

just my opinion though ofc

[43081j]

@alexeyraspopov this was brought up again recently in the e18e discord

since all but one of node LTS have require(esm) now, and it seems very unlikely there'll be any bug fixes to do (the code has settled), maybe a new major which is esm-only could be an option?

people can upgrade as needed, no rush since both would have identical feature sets

[hyoretsu]

Maybe this is why I'm getting TypeError: Cannot read properties of undefined (reading 'bold') when using this.

[43081j]

For if/when you ever want it @alexeyraspopov , here it is #93

[inoyakaigor]

Node.js got native support for CLI text styling in v20. I don't think it makes sense to do anything with this package.

[43081j]

it'll take quite some time for very popular projects to require >=20, this package is still necessary.

it makes sense to modernise it given it will certainly still be here for the next couple of years and hugely popular still