Titus

The problem you describe is not the problem. This package uses `nlcst-to-string` version 2, which was CommonJS. And used `module.exports`. Are you on the latest webpack 5? Have configured it...

TypeScript isn’t 100% there yet on ESM either, so that might be related. I’m moving through my projects again, updating deps and adding strict types, so I’ll soon get to...

It’s impossible to use version 3 of `nlcst-to-string` with a default import!

Different version! The error is not the default export in the old version, Node.js and modern bundlers support using a default export for CJS `module.exports`. Some bundlers don’t though. In...

Bundlers are very good at this. They're not confused. They are meant to deal with dependencies with different versions. Different versions isn't a problem. For your last point, well, the...

Hey there! - What are the exceptions? - If the goal is to support different languages, are exceptions enough? Would more extensions be needed and possible? Couldn’t a `parse-french` be...

Another same/similar example: https://github.com/unifiedjs/unified/discussions/160#discussioncomment-1379260

Could this be an upstream fix?

That is an important caveat that seems like it’s something that should be in a comment next to the function?

I’m okay on that too, but probably also perhaps a new section (Client?) on how to make a client (because Use should be one basic example, and API should be...