Can we target the generated css file (generated from css module imports) about esbuild

[evanw]

maybe would just be better to do something like copying public assets to whichever folder after esbuild is done.

This is likely the most straightforward solution. If you need to, you can look in the metafile for the cssBundle property on the JavaScript entry point to get the path to the CSS entry point.

[maxmezzomo]

I don't know what you wanna do for the issue, for me its fine to close as can be outside scope.

[maxmezzomo]

okay nice thanks, in case anyone looking for something similar, this works for my case and think there's some flexibility with build onEnd res callback arg providing metafile also

const moveCss: Plugin = {
  name: "move css",
  setup(build) {
    build.onEnd((res) => {
      fs.renameSync("server.css", "public/server.css");
    });
  }};