Is there a way to gracefully handle Mdx parsing failure in gatsby-plugin-mdx?

[Stvad]

My situation is as follows:
I get input content as a set of "blocks" each of the blocks contains a flavored Markdown. A part of this special flavor is that html elements are not rendered. So those block can contain both valid and invalid html (I don't control the content).

What I want to do is to assemble a set of blocks into a pages rendered by MDX. Which works well most of the time, but things fail parsing (and the build) when there is malformed html present in the source.

My question is - can I somehow configure gatsby-plugin-mdx to fail gracefully in such a situation?
What I mean by "failing gracefully" is:

• not failing overall build. This is the critical part. I don't control the inputs, and failing the build is worst thing that I can do there. Instead I'd like to do the build on a "best effort" basis:
• render inline error for content that failed to parse properly/or just display it as plain-text.

Alternatively a reliable way to escape html inside mdx would work too (related: mdx-js/mdx#1477 ) - some good discussion there, but that's not sufficient

[Stvad]

Looking at https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-plugin-mdx/utils/create-mdx-node.js#L15 it does not seem to be possible atm :(. The plugin seems to just re-throw any error it gets from mdx =\