Yes, that's a good idea. You'd just need to introduce a little wrapper around the client-side rehydrate to move the contents of the <noscript> tag out of the <noscript> before calling React.render.

Then again, you don't really need <noscript> in that case. It's rendering server-side, so the page already displays correctly, you just need to make sure all your links work.

I've been burned by trying to read the contents of noscript nodes before. Some browsers don't support that at all.

Oh wow that's annoying.

Why? The whole content is renderable server-side and all links should work. What purpose would <noscript> serve?

Wouldn't that hide the page for JS clients? Or would the JS client remove the <noscript> tags?

<noscript> is only rendered if JavaScript is disabled.