David Hewitt

@patrickhulce Just a heads up :)

I am also experiencing the same error: ``` Failed to find a valid digest in the 'integrity' attribute for resource 'https://cdn.amplitude.com/libs/amplitude-8.16.0-min.gz.js' with computed SHA-384 integrity 'G5p3YHHIMhqDroi1wiIRIEJZZCcdNsFWb90cB5FCjJEkCV1NN5gal4aaJRDHU6Qy'. The resource has been...

https://github.com/FormidableLabs/react-live/issues/339 Looks like there is a PR but it's not merged yet

Recently ran into this as well. Because NextJS has a feature called [output standalone](https://nextjs.org/docs/pages/api-reference/next-config-js/output#how-it-works) which analyses your code for modules that you import and then only includes them specifically in...

There is an enabled flag? https://github.com/pinojs/pino/blob/master/docs/api.md#enabled-boolean `disabled` is also very vague imo as it could be misinterpreted as disabling the whole browser functionality including the transmit function where as this...

The concerns are the mixing of two very different css methodologies. Perhaps we may consider adding atomic classes to our roadmap however, that is a discussion for the guild. i.e....

@RodEsp Good catch thanks, updated

@philipp-spiess Sorry to ping you but this bug is affecting us and was wondering if you wouldn't mind reviewing this PR for me please?

Yeah I get the feeling something is wrong in playwright's component testing which uses [Vite](https://vitejs.dev/) under the hood to create the components bundle and serve it. ```ts // playwright-ct.config.ts import...

So turns out the fix is to add `"type": "module"` to your package json file this forces playwright to build using esm