Lewis

Excellent work! Hope to see this merged.

**It is possible to work around this for the time being.** cc @eduardoboucas The following approach lets us get working ESM bundles out. It requires `--bundle` because all other imports...

> @ctjlewis This looks like an interesting approach that might even fix the issues I had with prisma. However, how does esbuild know the modules required with 'require' should be...

I worked around with frontmatter: ``` --- header-includes: - \usepackage{pdfpages} --- ``` And, at the top of the document: ``` \includepdf{Cover.pdf} \pagebreak ```

This can be worked around for the time being by only adding absolute filepaths to Mocha: ```javascript mocha.addFile(path.resolve(file)) ```

A truly terrific piece of software. I can't wait to see what it looks like in 2 years and plan to sink time into contributing over the coming months.

@Andarist @lukastaegert Thoughts?

The reason I said `node-resolve` should imply `commonjs` and `json` is because if we want to bundle arbitrary Node dependencies, we will likely end up encountering CJS modules that end...

The amount of focus on the "implied plugin" comment is a little confusing - the bulk of this proposal is _not_ about implying the `commonjs` and `json` plugins by default...

@aral Agreed. I ended up having to develop a workspace preset and series of configs to work around these issues, and while this is totally not ready for public use,...