Titus

> Zero Configuration [...] There is a place for zero config stuff! There is also a place for tools, the stuff we make here in unified, that make *all the...

> I agree with @wooorm that an MDX integration for a build tool should support MDX options. The current implementation picks an arbritrary list of plugins. Some of these are...

> We should pass the file path to compile() if we have access to it. The asset type should indeed match the output type. This means jsx if the {jsx:...

> It would be nice if someone upgrades MDX Node.js loader to read configuration from a mdx.config.js file, then https://github.com/EasyWebApp/Parcel-transformer-MDX/issues/1 may be no need to do. ? I do not...

Can’t work? Footnote definitions, regular definitions, could be anywhere else. What if the current selection looks like it starts with frontmatter, even though it isn’t at the start of the...

Impossible to track every engine, and what it will end up with, and whether that actually works at runtime. But, "type": "commonjs", is what I see, and that's probably what...

Hi again! 👋 Ah, yeah. I guess, when making this initially, the idea was more to track ESM. Not dual. ESM being the “highest to achieve”. So indeed, if `"type":...

Done! :) Top-level conditions weren’t really supported it seems. Affecting some things classified as ESM, and some as CJS/faux, depending on that `type: module`!

Last I investigated, that is not the exact source. Do you have actual examples of markup?

if it is no longer suggested for use, then it is better to remove it from the list of suggestions. So :+1: to Remco’s suggestion. @pastacolsugo, can you instead remove...