using postcssModules make sass file cannot extract into a single css file about esbuild-sass-plugin HOT 6 CLOSED

I'm facing the same issue, I wonder if this is a limitation with esbuild at the moment. Is this something that you know @glromeo ? Nice plugin by the way :-)

from esbuild-sass-plugin.

Sorry guys what you ask is against esbuild design. In order for the css modules to be imported they have to be specified as 'js' for the loader and then esbuild leaves their handling to the plugin with no way for that css to be part of the compact bundle you want. I left this issue open while I was getting my head around the possibility of writing myself a bundling of all the styles module into a single one but the effort of such task (considering the issue with sourcemaps) puts it out of scope

from esbuild-sass-plugin.

@glromeo I created custom transform for this but I don't find a way to know when the rebuild started so I can remove/clean the css file

from esbuild-sass-plugin.

@ronkorland esbuild provides a callback for that https://esbuild.github.io/plugins/#on-end

you just have to add an extra little plugin to your build e.g.

   ...
   plugins: [
     esbuildSassPlugin({...}),
      {
        name: 'example',
        setup(build) {
          build.onEnd(result => {
            ...here you can trigger your remove/clean...
          })
        },
      }
   ]
   ...

from esbuild-sass-plugin.

I would also be interested in extracting the css to a separate file. @ronkorland would you mind sharing your approach?

from esbuild-sass-plugin.

@franckchen @yourivdlans @tiagovtristao @ronkorland
v2.7.0 brings, at long last, a solution to this CSS vs Js problem
while playing nicely with esbuild pipeline...have a try!

from esbuild-sass-plugin.