Jolyn

@sebmarkbage I see that [email protected] was released today - does that have the new support you talked about for custom elements, where everything is properties instead of attributes? Also, one...

Answering my own question above: [email protected] does not have support for this yet. I have created #8755 to add it to react@16, though

@gaearon I see. Is there somewhere I can read about 16? Has it been decided when it might be released? Is there a roadmap or tentative list of what might...

@justinfagnani those are good points. I have a question about the upgrading scenario that you brought up, though: In general, don't elements (both native and custom) look at attributes when...

Ah that's a good point. So if an element isn't upgraded yet, you may still need to set properties on it because setting it as an attribute won't work if...

I agree with @staltz -- we've always been able to interoperate with custom elements inside of React. But it would be really nice if (at least for the majority of...

@jfhector I believe the most up-to-date discussions on improved custom element interop for react are now at https://github.com/reactjs/rfcs/pull/15 -- this thread might no longer be relevant.

@benkocabasoglu here's a comment from a while ago from Dan Abramov that clarified for me why React has been slow to change/improve React's support for web components. https://dev.to/dan_abramov/comment/6kdc

Do you have an idea of what the API of the module would be? If so, could you share? Having just created a PR in #112, I think the it...

Thanks for the explanations and code example. So pipelines would be an in-between step between extraction and exporting? What isn't clear to me in the pseudo code you wrote is...