翠

I noticed that esbuild lowers the tagged call case (https://github.com/evanw/esbuild/commit/58ac420581421b36c03649c0018286e5a8e58ffd#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4edL48-R50, [esbuild try](https://esbuild.github.io/try/#dAAwLjI1LjEyAABmb29gPC9zY3JpcHQ+YA)). I guess Oxc should do that.

@IWANABETHATGUY I was thinking of enabling `tagged_template_transform` for `platform: 'browser'`. But on second thought, we should enable it unconditionally for now until #15306 is fully resolved (https://github.com/oxc-project/oxc/issues/15306#issuecomment-3530678259), otherwise it'll break...

A PR that handles `import.meta` is welcome 🙂 BTW "A longer term solution could be to not bundle the configuration" is available since 6.1 as an experimental feature. https://vite.dev/config/#:~:text=CONFIG%20LOADING,the%20Vite%20server.

Vite 6 includes this fix (https://github.com/rollup/plugins/pull/1618) from commonjs plugin. Probably this is related.

FYI the error position in the input code is https://github.com/sebmarkbage/art/blob/20b1462e35c330b60c746112feb6640edc1f18b3/core/color.js#L196

> Digging deeper, I noticed that both empty and non-empty CSS files send the same metadata to Rollup for bundling. @0xlakshan Would you elaborate what you mean by the same...

That doesn't necessarily mean it’s an upstream bug. Vite's internal plugins can modify the inputs and outputs, but those changes may not be observable there.

Ah, no, I was wrong. [email protected] is actually used. But the activation for [email protected] is running even if it's not needed, I guess.