Luke Page
Luke Page
Hi @ColinEberhardt / @chrisprice, We're implementing CSP and came across this. Your suggestion above looks like it would work, but there is another css file now: https://github.com/d3fc/d3fc/blob/42243cc311f01b3f248c7a85ae4756164ebbedfe/packages/d3fc-chart/src/css.js pulled in by...
We would either have to change the thing using the css handler to not be static (called once when first needed) or expose it as a seperate export e.g. ```...
> I can confirm - I also experience systematic problems with `turbo.exe` hanging in memory and blocking `node_modules` from being wiped out whenever I need it, not to mention redundant...
Actually addressed in https://github.com/vercel/turbo/pull/8728
To maybe save other people some time (I spent hours suppressing eslint warnings) it looks like this error is going to be disabled from the eslint plugin until it is...
most if not all these issues have been fixed in the latest release (works for me anyway...)
If you decide to merge this, please can you make it an option? Otherwise for people who already upgraded and added hundreds of eslint suppression comments, would have to undo/remove...
Its merged.. so storybook "just" need to upgrade from 0.12 to 0.13 ?
We get this intermittantly and have done for quite some time. No webconnect error for us, just: ``` Runtime.enable will not run as browser CRI connection was reset Error: Runtime.enable...
Note also - typescript eslint v8 is required for eslint v9, so this essentially blocks eslint v9 upgrade even though you now technically support it.