Matija Marohnić

Seems like `@vitejs/plugin-legacy` is creating another bundle that's intended to be inserted separately, but perhaps Remix doesn't have a way of handling that, so the server build collects the modern...

@patdx what are you using for CSS? Just regular (S)CSS, Tailwind or something else? Are you using Environment API by any chance?

Yeah, in effort to make the CSS story simple Remix relies on the assumption that the CSS built in client and server build will always match. But the point of...

Actually there is a way to obtain it, via Vite's own `resolveConfig`: ```js async config(config, env) { if (env.isSsrBuild) { const resolvedConfig = await resolveConfig( { configFile: false, // avoid...

> I think it's clear, I haven't read the code but it must need to create a file watcher somewhere and call a new Build everytime file changes. Creating a...

@eps1lon what do you mean by "not supported"? It produces the expected attribute for me. Has this support changed in the meantime? Is there something problematic about this attribute?

Works fine now, thank you!

I was migrating from away ESLint while burnt out, so I jumped straight into docs, that detail slipped past me 😄 But nice! Until Zed provides some configuration leeway, isn't...

That's a cool trick, and appears to be exactly what I wanted, thanks! 🥳

It doesn't work for me either, with npm 😕 I tried the following just in case, I tried overriding it all the way as well just in case: ```json "overrides":...