[Bug]: Bug with fonts during local development about rspack

[github-actions]

Hello @exocornet, sorry we can't investigate the problem further without reproduction demo, please provide a repro demo by forking rspack-repro, or provide a minimal GitHub repository by yourself. Issues labeled by need reproduction will be closed if no activities in 14 days.

[exocornet]

Hello, I provide a repository
https://github.com/exocornet/express-template/tree/rspack

File rspack.config.js 139 line. I had to disable caching to work correctly locally, but the collector began to work slower.
https://github.com/exocornet/express-template/blob/rspack/rspack.config.js

I connect the fonts in fonts.scss
https://github.com/exocornet/express-template/blob/rspack/src/shared/styles/layer-generic/fonts.scss

I also have two more questions:

1. Will there be plugin support webpack-remove-empty-scripts? It doesn't work now, you have to do it with additional code in file server.js 208 - 220 line.
   webpack-remove-empty-scripts
   https://github.com/exocornet/express-template/blob/rspack/server.js

2. Will there be full support for the plugin in the near future image-minimizer-webpack-plugin? It is sorely missed the way it worked before.

Thanks for the help and quick response.

[LingyuCoder]

cc @jerrykingxyz , seems to be a bug of incremental build while handling assets, I made a more simple repro here, just rspack serve and modify the other.css

[jerrykingxyz]

@exocornet you can try set output.clean to false to workaround. The other two questions about plugin compatibility @h-a-n-a cc

[exocornet]

cc @jerrykingxyz , seems to be a bug of incremental build while handling assets, I made a more simple repro here, just rspack serve and modify the other.css

Hello. Yes, that's right, that's true. But webpack did not have this bug. Can you please tell me how to solve this problem? And also tell me, with the other two questions, are there already answers or solutions?

[exocornet]

@exocornet you can try set output.clean to false to workaround. The other two questions about plugin compatibility @h-a-n-a cc

Thank you very much, everything works. But I would like to have support like in webpack. And so I have to set isProd for clean. Although this may be more correct for local assembly, here I rely on your expertise.

@h-a-n-a Hello, I was advised to contact you regarding the two questions above. Can you suggest something?

I also have two more questions:

Will there be plugin support webpack-remove-empty-scripts? It doesn't work now, you have to do it with additional code in file server.js 208 - 220 line.
webpack-remove-empty-scripts
https://github.com/exocornet/express-template/blob/rspack/server.js

Will there be full support for the plugin in the near future image-minimizer-webpack-plugin? It is sorely missed the way it worked before.

Thanks for the help and quick response.

[h-a-n-a]

@exocornet you can try set output.clean to false to workaround. The other two questions about plugin compatibility @h-a-n-a cc

Thank you very much, everything works. But I would like to have support like in webpack. And so I have to set isProd for clean. Although this may be more correct for local assembly, here I rely on your expertise.

@h-a-n-a Hello, I was advised to contact you regarding the two questions above. Can you suggest something?

I also have two more questions:
Will there be plugin support webpack-remove-empty-scripts? It doesn't work now, you have to do it with additional code in file server.js 208 - 220 line.
webpack-remove-empty-scripts
https://github.com/exocornet/express-template/blob/rspack/server.js
Will there be full support for the plugin in the near future image-minimizer-webpack-plugin? It is sorely missed the way it worked before.

Thanks for the help and quick response.

The plugin's relying on a few hooks that does quite expensive jobs on the JS side. We're not likely to support this.
https://github.com/webdiscus/webpack-remove-empty-scripts/blob/84157f850976c00474a97cc954f2a9837c2c0347/src/index.js#L53-L102

[h-a-n-a]

Since the bug has been resolved, I will close this issue.