Alex

It turns out that `node --test -r esbuild-runner/register` works well, but because of the [runner execution model](https://nodejs.org/api/test.html#test-runner-execution-model) it won't find .ts files unless they are added explicitly: `node --test -r...

> That's expected because `buffer@6` dropped support of IE11: [840160f](https://github.com/feross/buffer/commit/840160f352ff0d8e88d4ac308a1640fd278f50fc) should the readme mention this as it currently says 'all browsers'?

wow - sound likes a lot of work and a huge scope!

I believe that this will only happen in development, not production which is by design with React 18 StrictMode changes.

I have the same issue with my package @fairfox/adorn It doesn't find the types and it doesn't see the latest version. https://codesandbox.io/s/adorn-react-0vbwqo?file=/src/App.tsx

This is likely because the pipe option does not work in Deno which makes the compatibility claim in https://deno.com/blog/v1.35 a little confusing. Assuming you have “installed” a browser with `deno...

It seems like having the `pipe` launchOption in Puppeteer set to true has the same result. See https://github.com/lucacasonato/deno-puppeteer/issues/56

I would say that an approach which is as 'native' as possible to scoping styles to es components is preferable. In reflecting on the problem that css modules attempts to...

I suspect that the deno-ts error would be resolved by https://github.com/lucacasonato/esbuild_deno_loader/pull/78 but for some reason the maintainer has not deployed it.