Tim van der Horst
Tim van der Horst
@danbovey Woah woah hey, it's not actually solved yet, it was only raised as a hypothetical solution
@danbovey The problematic code is directly created by this babel plugin. Relying on yet another plugin to make further changes over the top of how it already behaves is an...
Has this been fixed yet? This is a really frustrating problem on pages that have constant automatic AJAX requests.
https://stackoverflow.com/questions/63119217/csp-worker-src-blob-security Allowing "blob:" can't be done for just one package, and it opens the gate for arbitrary code execution across the whole app. If someone manages to get code injected...
Additionally, it's hard to figure out what code is actually used by the worker since an entire copy of the module is injected into the worker, including the code that...
@gvaldambrini Storybook 6 has been out for a while, could you merge this?
It's still a current issue
I've also had success with using https://github.com/Gamote/lottie-react
Yes, as long as you create a definition file in the same format as the existing icon definitions, you can import and use them in the same way as the...
In theory, using only explicit imports would make the `icon` (lookup) import obsolete, and then all that's left is the `parse` import from `fontawesome-svg-core`. If those two dependencies could be...