????????????It's our absolute pleasure to announce Webpack 4 Support ????????????
\n\n> **HEADLINES (May 2018): Now Independently supports Webpack 4:**\n> Yep that's right. The universal family is now fully Webpack 4. Thank you to all our users for your loyalty and patience! If you love Universal, then you are gonna fall head over heels when we bring out the main course!\n\nSo... why did we rebuild `extract-css-chunks-webpack-plugin`? What does it offer?\n\nIt's got all the goodness of `mini-css-extract-plugin` but with 2 gleaming, sought after benefits.\n\nCompared to the existing loaders, we are offering a single solution as opposed to needing to depend on multiple loaders to cater for different features:\n\n## Perks\n\n- **HMR:** It also has first-class support for **Hot Module Replacement** across ALL those css files/chunks!!!\n- cacheable stylesheets\n- smallest total bytes sent compared to \"render-path\" css-in-js solutions that include your CSS definitions in JS\n- Faster than the V2!\n- Async loading\n- No duplicate compilation (performance)\n- Easier to use\n- Specific to CSS\n- SSR Friendly development build, focused on frontend DX\n- Works seamlessly with the Universal family\n- Works fantastically as a standalone style loader (You can use it for any webpack project! with no extra dependencies!)\n- Async styles do not render block webkit browsers, if you use the `insert` option\n\nAdditionally, if you are already a user of the universal family -- we will be waving goodbye to the mandatory `window.__CSS_CHUNKS__`.\n\nThe functionality is still available to you via chunk flushing, and it can come in super handy when needing to easily resolve style assets as urls that might need to be passed to a third party.\n\n**webpack.config.js**\n\n```js\nconst ExtractCssChunks = require('extract-css-chunks-webpack-plugin');\n\nmodule.exports = {\n plugins: [new ExtractCssChunks()],\n module: {\n rules: [\n {\n test: /\\.css$/i,\n use: [ExtractCssChunks.loader, 'css-loader'],\n },\n ],\n },\n};\n```\n\n## Options\n\n### `publicPath`\n\nType: `String|Function`\nDefault: the `publicPath` in `webpackOptions.output`\n\nSpecifies a custom public path for the target file(s).\n\n#### `String`\n\n**webpack.config.js**\n\n```js\nconst ExtractCssChunks = require('extract-css-chunks-webpack-plugin');\n\nmodule.exports = {\n plugins: [\n new ExtractCssChunks({\n // Options similar to the same options in webpackOptions.output\n // both options are optional\n filename: '[name].css',\n chunkFilename: '[id].css',\n }),\n ],\n module: {\n rules: [\n {\n test: /\\.css$/,\n use: [\n {\n loader: ExtractCssChunks.loader,\n options: {\n publicPath: '/public/path/to/',\n },\n },\n 'css-loader',\n ],\n },\n ],\n },\n};\n```\n\n#### `Function`\n\n**webpack.config.js**\n\n```js\nconst ExtractCssChunks = require('extract-css-chunks-webpack-plugin');\n\nmodule.exports = {\n plugins: [\n new ExtractCssChunks({\n // Options similar to the same options in webpackOptions.output\n // both options are optional\n filename: '[name].css',\n chunkFilename: '[id].css',\n }),\n ],\n module: {\n rules: [\n {\n test: /\\.css$/,\n use: [\n {\n loader: ExtractCssChunks.loader,\n options: {\n publicPath: (resourcePath, context) => {\n return path.relative(path.dirname(resourcePath), context) + '/';\n },\n },\n },\n 'css-loader',\n ],\n },\n ],\n },\n};\n```\n\n### `esModule`\n\nType: `Boolean`\nDefault: `false`\n\nBy default, `extract-css-chunks-webpack-plugin` generates JS modules that use the CommonJS modules syntax.\nThere are some cases in which using ES modules is beneficial, like in the case of [module concatenation](https://webpack.js.org/plugins/module-concatenation-plugin/) and [tree shaking](https://webpack.js.org/guides/tree-shaking/).\n\nYou can enable a ES module syntax using:\n\n**webpack.config.js**\n\n```js\nconst ExtractCssChunks = require('extract-css-chunks-webpack-plugin');\n\nmodule.exports = {\n plugins: [new ExtractCssChunks()],\n module: {\n rules: [\n {\n test: /\\.css$/i,\n use: [\n {\n loader: ExtractCssChunks.loader,\n options: {\n esModule: true,\n },\n },\n 'css-loader',\n ],\n },\n ],\n },\n};\n```\n\n## Examples\n\n### Minimal example\n\n**webpack.config.js**\n\n```js\nconst ExtractCssChunks = require('extract-css-chunks-webpack-plugin');\n\nmodule.exports = {\n plugins: [\n new ExtractCssChunks({\n // Options similar to the same options in webpackOptions.output\n // all options are optional\n filename: '[name].css',\n chunkFilename: '[id].css',\n ignoreOrder: false, // Enable to remove warnings about conflicting order\n }),\n ],\n module: {\n rules: [\n {\n test: /\\.css$/,\n use: [\n {\n loader: ExtractCssChunks.loader,\n options: {\n // you can specify a publicPath here\n // by default it uses publicPath in webpackOptions.output\n publicPath: '../',\n hmr: process.env.NODE_ENV === 'development',\n },\n },\n 'css-loader',\n ],\n },\n ],\n },\n};\n```\n\n### The `publicPath` option as function\n\n**webpack.config.js**\n\n```js\nconst ExtractCssChunks = require('extract-css-chunks-webpack-plugin');\n\nmodule.exports = {\n plugins: [\n new ExtractCssChunks({\n // Options similar to the same options in webpackOptions.output\n // both options are optional\n filename: '[name].css',\n chunkFilename: '[id].css',\n }),\n ],\n module: {\n rules: [\n {\n test: /\\.css$/,\n use: [\n {\n loader: ExtractCssChunks.loader,\n options: {\n publicPath: (resourcePath, context) => {\n // publicPath is the relative path of the resource to the context\n // e.g. for ./css/admin/main.css the publicPath will be ../../\n // while for ./css/main.css the publicPath will be ../\n return path.relative(path.dirname(resourcePath), context) + '/';\n },\n },\n },\n 'css-loader',\n ],\n },\n ],\n },\n};\n```\n\n### Advanced configuration example\n\nThis plugin should be used only on `production` builds without `style-loader` in the loaders chain, especially if you want to have HMR in `development`.\n\nHere is an example to have both HMR in `development` and your styles extracted in a file for `production` builds.\n\n(Loaders options left out for clarity, adapt accordingly to your needs.)\n\n**webpack.config.js**\n\n```js\nconst ExtractCssChunks = require('extract-css-chunks-webpack-plugin');\nconst devMode = process.env.NODE_ENV !== 'production';\n\nmodule.exports = {\n plugins: [\n new ExtractCssChunks({\n // Options similar to the same options in webpackOptions.output\n // both options are optional\n filename: devMode ? '[name].css' : '[name].[hash].css',\n chunkFilename: devMode ? '[id].css' : '[id].[hash].css',\n }),\n ],\n module: {\n rules: [\n {\n test: /\\.(sa|sc|c)ss$/,\n use: [\n {\n loader: ExtractCssChunks.loader,\n options: {\n hmr: process.env.NODE_ENV === 'development',\n },\n },\n 'css-loader',\n 'postcss-loader',\n 'sass-loader',\n ],\n },\n ],\n },\n};\n```\n\n### Hot Module Reloading (HMR)\n\nThe `extract-css-chunks-webpack-plugin` supports hot reloading of actual css files in development.\nSome options are provided to enable HMR of both standard stylesheets and locally scoped CSS or CSS modules.\nBelow is an example configuration of `extract-css-chunks` for HMR use with CSS modules.\n\nWhile we attempt to hmr css-modules. It is not easy to perform when code-splitting with custom chunk names.\n`reloadAll` is an option that should only be enabled if HMR isn't working correctly.\nThe core challenge with css-modules is that when code-split, the chunk ids can and do end up different compared to the filename.\n\n**webpack.config.js**\n\n```js\nconst ExtractCssChunks = require('extract-css-chunks-webpack-plugin');\n\nmodule.exports = {\n plugins: [\n new ExtractCssChunks({\n // Options similar to the same options in webpackOptions.output\n // both options are optional\n filename: '[name].css',\n chunkFilename: '[id].css',\n }),\n ],\n module: {\n rules: [\n {\n test: /\\.css$/,\n use: [\n {\n loader: ExtractCssChunks.loader,\n options: {\n // only enable hot in development\n hmr: process.env.NODE_ENV === 'development',\n // if hmr does not work, this is a forceful method.\n reloadAll: true,\n },\n },\n 'css-loader',\n ],\n },\n ],\n },\n};\n```\n\n### Minimizing For Production\n\nTo minify the output, use a plugin like [optimize-css-assets-webpack-plugin](https://github.com/NMFR/optimize-css-assets-webpack-plugin).\nSetting `optimization.minimizer` overrides the defaults provided by webpack, so make sure to also specify a JS minimizer:\n\n**webpack.config.js**\n\n```js\nconst TerserJSPlugin = require('terser-webpack-plugin');\nconst ExtractCssChunks = require('extract-css-chunks-webpack-plugin');\nconst OptimizeCSSAssetsPlugin = require('optimize-css-assets-webpack-plugin');\n\nmodule.exports = {\n optimization: {\n minimizer: [new TerserJSPlugin({}), new OptimizeCSSAssetsPlugin({})],\n },\n plugins: [\n new ExtractCssChunks({\n filename: '[name].css',\n chunkFilename: '[id].css',\n }),\n ],\n module: {\n rules: [\n {\n test: /\\.css$/,\n use: [ExtractCssChunks.loader, 'css-loader'],\n },\n ],\n },\n};\n```\n\n### Using preloaded or inlined CSS\n\nThe runtime code detects already added CSS via `` or `
![\"Version\"](\"https://img.shields.io/npm/v/extract-css-chunks-webpack-plugin.svg\")
\n \n![\"Build](\"https://travis-ci.org/faceyspacey/extract-css-chunks-webpack-plugin.svg?branch=master\")
\n \n\n \n ![\"Downloads\"](\"https://img.shields.io/npm/dt/extract-css-chunks-webpack-plugin.svg\")
\n \n\n \n ![\"License\"](\"https://img.shields.io/npm/dm/extract-css-chunks-webpack-plugin.svg\")
\n \n \n \n ![\"License\"](\"https://img.shields.io/npm/l/extract-css-chunks-webpack-plugin.svg\")
\n \n