Вадим Бударин

I can't share repo - it's company's project I simply have made upgrade webpack and have excluded the plugin and compare generated bundle sizes Webpack 4  [webpack 4 config...

@sokra The plugin successfully deals with many problems - you could use the experience from the plugin

> @budarin Hi. Please try [v4.0.0-beta.1](https://github.com/browserslist/browserslist-useragent-regexp/releases/tag/v4.0.0-beta.1). it still unsafe :( try it with this rule https://github.com/nodesecurity/eslint-plugin-security/blob/main/docs/regular-expression-dos-and-node.md

> So far, I think it's possible to solve this using `injectManifest` and a similar file: will there be any competition when downloading between your code and the workbox code?...

> @budarin But you are using manualChrome option and not calling anything manually? It apears itself, without calls from the your app side? yes, without calls from the app side...

I've found that there is another package in my node_modules folder with name 'image-size' so I changed loaders name to ```js { test: /\.(svg|png|jpg|gif)$/, include: path.resolve('./src'), exclude: path.resolve('node_modules'), use: {...

Finally - adding context option makes loader to work properly ```js { test: /\.(svg|png|jpg|gif)$/, include: path.resolve('./src'), exclude: path.resolve('node_modules'), use: { loader: 'image-size-loader', options: { name: 'img/[name].[hash:7].[ext]', context: path.resolve(__dirname, 'src'), },...

and that nothing has changed over the years??

has anyone figured out what the problem is? it's the first time I've encountered her in so many years and I don't understand what the problem is! I am assembling...

@Smorgasbordq Hi! why didn't you publish your work in npm? PS: by the way, the code falls with some errors