Mateusz Burzyński

> but @jsx jsx and @jsxImportSource could be set at same time. can they? arent they mutually exclusive? > I think add a custom jsx-runtime should only foucs @emotion/core/jsx-runtime with...

Sorry for being overly terse and losing the required context. I'll try to amend it now as well as I can. As you may know, Emotion has chosen to support...

> Hmm, are you saying that Emotion provides jsx but it has no relation to React's concept of jsx because Emotion wanted a shorter synonym for createElement? Not sure if...

> I personally wish this stuff was brought up a little bit earlier than a stable release including the transforms. We published the first RC in August (although to be...

@gaearon sure thing, gonna ping you and @lunaruan once I do this. Might also offer my help implementing this.

> Just to be clear, they would be able to solve that by changing the pragma they use (to the new one), would they not? Yes, but it requires us...

Moving the discussion from [here](https://github.com/microsoft/TypeScript/pull/39199#issuecomment-710962485): > I don’t think anyone is arguing that this isn’t confusing for the implementors. :-) In particular because it wasn’t clearly specified in the RFC....

Related issue: https://github.com/facebook/react/issues/24831

Hm, while priority-based updates are probably a powerful feature - it's really hard to grasp how this works in edge cases like this. It feels like there should be a...

> The interesting thing about these things is whether it's observable behavior or a perf consideration. The first minimal~ repro case in [this thread](https://github.com/facebook/react/issues/24831#issue-1290433788) showcases this problem through an observable...