Artur

I've never had this problem. Could you provide a reproduction?

No, not enough. I ran through them and don't see such errors.

Issues without reproductions should be closed as well as on the StackOverflow: > When asking a question, people will be better able to provide help if you provide code that...

PurgeCSS affects only `.css` files, see here: https://github.com/FullHuman/purgecss/blob/master/packages/purgecss-webpack-plugin/src/index.ts#L78-L80 And you've got only `.scss` files. If you create some `cool-styles.css` file in `src` folder: ```css // src/cool-styles.css .cool-style-man { background: darkgoldenrod;...

Seems like it's an Angular's issue. Compression plugin "subscribes" on the _emit_ hook and then runs compressions on files: ```js compiler.hooks.emit.tapAsync({ name: 'CompressionPlugin' }, (compilation, callback) => { console.log(Object.keys(compilation.assets)); })...

@just-jeb it's reproducible as I mentioned in my comment.

> @arturovt But `es5` files shouldn't be in `compilation.assets` at all. That's what I can't understand. I understand your point. But it DOES, there are all files except of `main`...

This won't and shouldn't work since CLI uses `postcss-loader` under the hood to do any CSS processing. This is what I've found when googled _postcss svg_: https://github.com/TrySound/postcss-inline-svg

@metallidevils Hey. > How can I remove/replace this file-loader, and instead use a base64-inline loader to inline the font files? ```js // extra-webpack.config.js module.exports = config => { config.module.rules =...

I think he will need to check the RegEx used by Angular and modify with its own (that doesn't contain font extensions) + also add the `base64-inline-loader`. Something like: ```js...