Support custom JSX components? about markdown-to-jsx

[quantizor]

Hmm. This component is also meant to work in the browser, so traversing the file system is probably not in the cards. One caveat is I'm using remark under the hood, so if its HTML parser rejects the custom components, there's not much I can do short of reimplementing that whole part of the system.

Anything that looks like HTML is generally regarded as an antipattern in markdown land. One thing I might suggest is using fenced code blocks and maybe eval-ing their content if marked with a custom "lang" of your choosing. Interesting, but tough problem to solve for what is intended to be a pretty opinionated format.

[quantizor]

@KyleAMathews on your second point, is the idea to basically create a stringified version of the nested calls that could be its own exported module? Sort of precompiling in a sense...

I could see that being a webpack loader or something.