Alex Miller

Would also love to see comments accessible to some degree, i.e. ```ts transform({ filename: "", code: Buffer.from(css), visitor: { CommentBlock(cmt) { console.log(cmt); }, }, }), ``` So even if they...

I've done some debugging and found where this is caused: during the asset resolution, public assets are always treated like a file path and not possibly as a URL, so...

Unsure why the macos tests timeout, I ran the tests successfully locally on macos 🤔

@patak-dev really interesting test suite with `playground`, was interesting to dig into! I've adapted the `relative` tests in `assets` to a new suite `url`, hopefully this makes sense to do....

- Rebased - Updated added tests to match upstream move to `esm` @patak-dev is there anything you want from me to get this moving? :)

`@swc/plugin-emotion` latest is build with the newest `swc_core` crate. As a result it requires `@swc/core`@1.3.106 See https://swc.rs/docs/plugin/selecting-swc-core#swc_core

Looks like the package for the vite swc plugin has been bumped: https://github.com/vitejs/vite-plugin-react-swc/blob/main/package.json#L17 (needs another bump already) I wonder if it would make sense to have `@swc/core` as a peer...

That's reasonable Consumers of this plugin could also choose to override the `@swc/core` version too I suppose if they need bleeding edge

Looks like a lot of these would be resolved by: https://github.com/jsdom/cssstyle/pull/127 I'm also experiencing the same difficulty with this current limitation, hoping we can get some movement on that PR...

Found this while looking for issues around using emotion with this builder, worth mentioning that we recently moved from cypress to playwright. It greatly simplified our tests, and removed a...