Tymoteusz Czech

> Anyway, here's what happens when you have too many projects for a single API key at the moment Not possible with virtualized table, where all rows need to be...

> I'm also a little concerned about the potential a11y impacts of this change. Previously you could find any link on the page (by tabbing to it or by searching...

It's an interesting challenge. What I found so far: ### `window.WebAssembly` does not live in native land Automerge Slim Next is using this global in `./wasm_bindgen_output/web/automerge_wasm.js`. 1. I doubt using...

We’re aware that older browsers might face issues, but we’re focusing our efforts on current versions. Chrome 50 is nearly 9 years old and should not be used due to...

: +1 : I think metrics like bundle size should also be tracked. See bundlephobia: - [1.0.0-beta.9](https://bundlephobia.com/package/[email protected]) 44.4kB gzip - [1.0.0-beta.18](https://bundlephobia.com/package/[email protected]) 11.2kB gzip 🙌🏻 By the way, latest beta releases...

https://github.com/Unleash/unleash/pull/8046

Valid point @OnkelTem! Since you also got the exact place in the code where it is triggered, would you like to contribute a PR?

I did more digging. @Criezc how did you check that `useCallback` is working? I'm writing a test for it and I don't see the any difference in number of re-renders....

In my testing re-renders are caused by `flagsReady` and `flagsError` state in `FlagProvider`. I'm refactoring logic into `useFlagsStatus`. I'll check out React-scan. Any reproducible example will help. Do you update...

If we where to improve re-rendering for 'flagsRead' and 'flagsError', we would need to split provider into React Context Providers. That's a large refactor for a little improvement. This could...