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:
• Node Version:
• NPM Version:

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?

A pull request by @vankop was merged and maintainers requested a documentation change.

See pull request: webpack/webpack#10557

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

Issue description

workbox-webpack-plugin has an option to add a versioned workbox folder to the output directory.

When clean-webpack-plugin v3 is in the plugins list before workbox-webpack-plugin everything works as expected, but when it's in the plugins list after workbox-webpack-plugin the versioned workbox fold

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 !!

Hi,

any plan for supporting the upcoming [webpack 5][11]?

I had a quick try and I istantly hit a wall at this point which should be updated to:

import ParserHelpers from 'webpack/lib/javascript/JavascriptParserHelpers';

Thanks 💯 for the awesome lib!

svg-sprite-loader is good loader for svg.

But the example custom-runtime-generator only include React.

I create a repo for use svg-sprite-loader in vue through runtime-generator.

Please see this repo: https://github.com/Akimyou/svg-sprite-vue-generator

But i want to add some example in svg-sprite-loader main repo or in docs, can U give me some suggestion about it?

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

Frameworks like Gatsby already come with their own PostCSS loader, handling autoprefixing and more. I think treat could reduce its dependencies by delegating post-processing to webpack loaders.

https://docs.travis-ci.com/user/build-stages/

• Add build stages for lint, build, tests, and deploy
• Allow travis to test "latest" stable node version

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

Sorry if this is a duplicate. I saw there was #10 but I think this is a little different. With webpack-dev-server we're running it off another port locally. I looked at how wds tries to establish the socket and noticed __resourceQuery, but also that it falls back to trying to use document.currentScript. For the time being would it be ok to add in trying to parse document.currentScript an