A static archive of Markus Tacker's tweets. Follow me on Mastodon: @[email protected].
OTOH it might be a good time to do it now, before a "1.0" release.
The upside is that it moves the code base further in the right direction, but
since it's written in TypeScript I already have the ability to author pure ESM
JS code, so I can do the switch in the future as well.
The needed changes to the codebase can be automated: adding a .js extension to
imports, might even not be necessary in future TypeScript versions. And from a
user point of view it also has no immediate benefit
(@bifravst code mostly targets Node.js, with a
few browser libraries).