Server Rendering about dev

[marijnh]

Interesting, but hydrating such a rendering into a working editor would be a whole different problem. Being able to do this would be cool, but, I think, too much extra complexity to be justified by that coolness. So yeah, this is probably out of scope.

[curran]

The hydration problem can be avoided by clearing out and re-building the DOM once the JS loads, like this (which is how the demo does it):

const editorDiv = document.querySelector('#editor');
editorDiv.innerHTML = '';
editorDiv.appendChild(view.dom);

It's not as fancy as React hydration by a long shot, but it works. For my use case I think this is perfectly acceptable as a hydration solution.

I just had another idea. As an alternative to populating global (which doesn't feel quite right anyway) and detecting the Node environment, what if you could pass in document as an optional argument to the EditorView constructor? Something like this:

const dom = new JSDOM(html);   
const document = dom.window.document;
new EditorView(state, document);

If document is passed in, it can be assumed to be from JSDOM, and its presence can be used as the trigger to avoid executing code that's not necessary for just constructing the DOM.

Food for thought!