Danil Karpenko

It really slows down development a lot.

It seems to be related to React. Are there any workarounds?

> Can you try the same in Edge too? By default they should behave the same (even more than chrome + webview2) > > Also, what kind of GPU do...

I think `--ignore-gpu-blocklist` should help. However, how do I add it? I'll prepare a reproduction repo if that doesn't work.

> The easiest way (and maybe only way, since the `with_webview` method probably triggers to late to inject these flags 🤔) to try that flag is via the `WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS` environment...

> Well for a temporary dev check you'd just set it in the terminal, for powershell it'd be `$env:WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS="--ignore-gpu-blacklist"`. > > For production (or for testing too i guess) you'd...

This seems to have been fixed on the last commit.

I have solved this problem by package extensions in `.yarnrn.yml` ```yml packageExtensions: "@nivo/core@*": dependencies: prop-types: "*" '@nivo/tooltip': '*' '@nivo/legends@*': dependencies: d3-scale: '*' '@nivo/colors': '*' ```

Looking forward to the datagram.

As a temporary solution, this can be implemented via FFI