Mateusz Burzyński

It's a limitation of TypeScript. We can't "capture" and retain the generic nature of `FlatList` when we wrap it. As a workaround you can use this patch: ```diff diff --git...

@siriwatknp this one: https://github.com/thysultan/stylis/issues/301 . It got fixed in Stylis in September but I have only released an Emotion version with that fix just now

Wouldnt `node: "engines"` be more explicit and readable? Although it's also worth discussing if `engines` could support also some format for `browsers` - and if yes then this should be...

I know its a standard field, but as it is an object with "node" key and it could easily support browsers too - but i guess it could have been...

`buildExternalHelpers` builds helpers as string, you should save the result in a file and later `require` that file in your app.

I think documentation must be updated + we could add new function, smth like `injectExternalHelpers` which could build the helpers and evaluate them in global context, although we should add...

Apart from what Babel should do here, there is also an issue of the overall DX of the whole situation. I believe it's just terrible for both consumers and library...

> Writing ESM, then attempting to published it transpiled to CJS is a bad idea. Writing ESM, and attempting to publishing ESM with copies of the same API in separate...

I've looked through all of the examples and I think that essentially all of them are the same (from our PoV). It doesn't work because the `eventsCausingActions` is narrowing the...

We plan to rethink how parent-child communication is done in v5 and hopefully, this will get fixed holistically then. The problem here is that we don't have any special generic...