Are you aware of any different behavior when a PWA (using offline-plugin) is added to the home screen using "Add to Home Screen" on Chrome/Android or Safari/iOS?

I'm having problems with the app getting stuck using the cached version when it was installed and never updating.
I even have offline-plugin responseStrategy set to network-first but it seems to always use the cached version after add

Documentation Is:

• Operating System: N/A
• Node Version: N/A
• NPM Ve

I'm using Critters in my webpack project with the following configuration:

new Critters({
  mergeStylesheets: true,
  inlineFonts: true,
})

I'm using this in combination with MiniCssExtractPlugin. When I add Critters to the plugin list (after MiniCssExtractPlugin and HtmlWebpackPlugin), critters seems to remove the content of media queries - the output still has the media querie

Would be awesome if some benchmarks could be added to show the difference between the webpack perf with and without hard source. Happypack has a good example

如题，mac电脑最新版chrome跑的

This check https://github.com/GoogleChromeLabs/preload-webpack-plugin/blob/master/src/index.js#L118 breaks when the plugin is used with Expo that extends HtmlWebpackPlugin class into ExpoHtmlWebpackPlugin.

Is there a better way to find the plugin instance?

I've seen the advice to override __webpack_chunk_load__ to implement our own retry behavior, but how do I ensure that I override that function for all chunks? I assume that if I put my override in my entry module it will only apply to modules in the entry chunk, not modules in other chunks (which may themselves async load additional chunks).

This issue was moved from webpack/webpack#9102

Hi,

When comparing real assets size to the output of your plugin I see a huge difference.

I guess it's because size-plugin show gzipped sizes...
This can be confusing or non relevant depending of the use case and it could be nice to add a column to the output. (to display both compressed and real assets size)

Or maybe just an option to choose what too show?!

Tks !!

Haven't seen this reporter anywhere, tried out alpha 27 and with workerize-loader I get this:

TypeError: this.cache.get is not a function
    at /Users/nw/projects/motion/orbit/node_modules/webpack/lib/Compilation.js:2186:18
    at arrayEach (/Users/nw/projects/motion/orbit/node_modules/neo-async/async.js:2405:9)
    at Object.each (/Users/nw/projects/motion/orbit/node_modules/neo-async

tl;dr

What?

.mjs crashes during runtime.

Why?

Hard-coded value.

Detailed description

Webpack differentiates between actual ECMAScript modules (.mjs) and regular scripts (.js) in CommonJS style. For the uninitiated, CommonJS uses the global require¹ funct

The issue I'm experiencing is pretty annoying.
I'm trying to optimize my first byte, by turning off compression, and gziping everything by webpack with CompressionPlugin. The issue is that it doesn't compress service-worker.js produced by sw-precache-webpack-plugin.

I understand the reason why: service-worker.js should cache all chunks produced by webpack after CompressionPlugin compress

Do you want to request a feature, report a bug or ask a question?
Request a feature

What is the current behavior?
The examples in this repo include a build/main.js file. The custom runtime generator examples happen to import React and include the entire source code for React in the output.

What is the expected behavior?
It would be more useful as documentation to mark Reac

Documentation Is:

This is just something I was missing and that kept me personally from using fork-ts-checker-webpack-plugin in a few projects: integration with with the "Problems" tab in vscode.

But as I'm starting to dogfood now, too, I did a bit of googling and found https://code.visualstudio.com/docs/editor/tasks#_defining-a-multiline-problem-matcher which describes the process of defining yarn watch as a

Documentation Is:

• Missing
• Needed
• Confusing
• Not Sure?

The issue

In the Readme, the comments say you don't need to specify the entry option. It doesn't say what happens if you do though. Currently, whatever is in the configuration entry will be bundled by Webpack in addition to the karma files.
If you are like me and you are reusing the same configurati

I want to provide confidence to users about the effectiveness of the plugin to provide a secure approach to use .env files with bundles.

I was thinking it may be a good idea to apply a debug parameter to output in the console during the bundle process to show when a variable gets used. This would allow users to see exactly when something gets used.

Another use case would be for shared serv