Jason Miller

that would be very useful @ruyadorno

@paranoidjk ah - you probably want to use the JSX string renderer: ```js import preactRender from 'preact-render-to-string/jsx'; preactRender(bar) /* bar */ ```

Trying to think of the slimmest way to produce JSON output from the string renderer. It's the same flow, just seems awkward to have to have that many branches.

Ah yeah this looks like an issue. In preact it's more common to use the attribute names, but we do officially support both. We'll need to convert them :)

I commented on #66 but I think it's slightly different here - it seems like React has indicated `getDerivedStateFromError()` is not going to be supported in string renderer (ever?). Not...

I'm not entirely sure I understand the need for this to be a feature of `preact-custom-element`. What's happening here is essentially a variant of something the platform has attempted and...

Hiya! Sorry for the delay in responding to PRs. I'm wondering about the size impact of this, versus using a regular expression transform like `name.replace(/([A-Z])/,'-$1').toLowerCase()`.

tbh I never realized that was the case in React. Maybe we shouldn't both initializing it in preact either?

IIRC this is corrected in Preact X.

good to know!