Anton Kudriavtsev

Hi @Aliaksei-Martsinkevich, @garand, This is intentional. The main reason this was done is to avoid running modules on the same file twice, see [this](https://github.com/egoist/rollup-plugin-postcss/issues/70) for an example. Although this will...

Hi @mnlbox, > Is it supporting now or it's in your roadmap? Yes, it is fully supported. And works just like Rollup's code splitting does, based on dynamic imports and...

> Is it normal to remove scss import from js file? In `extract` mode - this is intentional, since there's no `require` in the browser. I'd imagine you would use...

@mnlbox imports are not kept since they are not JS, thus rollup cannot understand and process them properly. I guess this is not that clear, so this needs documentation and...

@dsluijk Returning to work after a long break, will look into it.

Hello @43081j, Maybe what you are looking for is [emitting CSS down the pipeline, which is already a part of this plugin](https://github.com/Anidetrix/rollup-plugin-styles#emitting-processed-css). For example using [this plugin in conjunction with...

Hi @Grafikart, thank you for your suggestions! > Is it possible to extract CSS from the main entrypoint but inject CSS for async import Not with the single plugin instance,...

@chmelevskij I don't think so, since chunk information is available after transformation step, by which point, as I said before, all the `inject`-related stuff is already done.

Hi @parttee, ` alias` option work only for PostCSS-processed `@import` and `url()` statements at the moment, not for SCSS/LESS/Stylus `@import`s due to high difficulty or even impossibility to implement it...

Hi @dilyanpalauzov, Will do as soon as I'll have some time for this.