HTML Serializer is Incompatible with React-Native

Do you want to request a feature or report a bug?

Feature

What’s the current behavior?

Trying to import the html-serializer into a react-native project causes the error:

document is not defined - I assume this occurs because the html-serializer relies on the built in DOMParser

The above is inaccurate and seems to be caused by my schema somehow, although I believe the issue itself is still relevant as React-Native is missing DOMParser as far as I can tell.

What’s the expected behavior?

It’s probably not reasonable to expect this to work out of the box, but it would be great to:

1. Find a way to throw a friendlier error message thrown before React-Native can throw its own - Right now we have that, but React-Native beats it to the punch.
2. Determine an alternative to DOMParser and jsdom that can be passed to the html-serializer

Potentially interesting avenues to explore:

• https://www.npmjs.com/package/react-native-dom-parser
• Find a way to use jsdom without reliance on NodeJS built-ins

@ianstormtaylor do you have any ideas that might be less cumbersome than the above?

[brendancarney]

I had an issue with parse5 where node.nodeValue is null in parse5, but node.value isn’t:

https://github.com/ianstormtaylor/slate/blob/master/packages/slate-html-serializer/src/index.js#L47

I haven’t looked into what is right.

[ianstormtaylor]

As of https://github.com/ianstormtaylor/slate/pull/3093 (which was just merged), I believe this issue is no longer applicable, because a lot has changed. I’m going through and closing out any potential issues that are not out of date with the overhaul. Thanks for understanding.