npmpackage.info

Gathering detailed insights and metrics for @prepair/extract-css-chunks-webpack-plugin

@prepair/extract-css-chunks-webpack-plugin - 4.9.1 | npmpackage.info

@prepair/extract-css-chunks-webpack-plugin

Extract CSS from chunks into multiple stylesheets + HMR

4.9.1

MIT

JavaScript

78.19 kB

1,558 1.7

Installations

npm install @prepair/extract-css-chunks-webpack-plugin

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Min. Node Version

>= 6.9.0

Node Version

14.15.1

NPM Version

6.14.9 Score

61.3

Supply Chain

64.7

Quality

78.6

Maintenance

100

Vulnerability

99.6

License

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Languages

JavaScript

CSS

HTML

JavaScript (88.13%)

CSS (6.38%)

HTML (5.48%)

Developer

prepair

Download Statistics

Total Downloads

1,558

Last Day

Last Week

Last Month

Last Year

282

GitHub Statistics

MIT License

515 Commits

1 Forks

6 Branches

5 Contributors

Updated on Dec 15, 2020

Bundle Size

290.26 kB

Minified

78.19 kB

Minified + Gzipped

Bundlephobia

Maintainers

View All 5 Contributors

Package Meta Information

Latest Version

4.9.1

Package Id

@prepair/extract-css-chunks-webpack-plugin@4.9.1

Unpacked Size

63.11 kB

Size

17.21 kB

File Count

NPM Version

6.14.9

Node Version

14.15.1

Total Downloads

Cumulative downloads

Total Downloads

1,558

Last Day

Compared to previous day

Last Week

Compared to previous week

Last Month

-44.4%

Compared to previous month

Last Year

31.8%

282

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

If you like our work, check out our Redux-based router redux-first-router or its sucessor which, Rudy

extract-css-chunks-webpack-plugin

🍾🍾🍾It's our absolute pleasure to announce Webpack 4 Support 🚀🚀🚀

HEADLINES (May 2018): Now Independently supports Webpack 4: 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!

So... why did we rebuild extract-css-chunks-webpack-plugin? What does it offer?

It's got all the goodness of mini-css-extract-plugin but with 2 gleaming, sought after benefits.

Compared to the existing loaders, we are offering a single solution as opposed to needing to depend on multiple loaders to cater for different features:

Perks

HMR: It also has first-class support for Hot Module Replacement across ALL those css files/chunks!!!
cacheable stylesheets
smallest total bytes sent compared to "render-path" css-in-js solutions that include your CSS definitions in JS
Faster than the V2!
Async loading
No duplicate compilation (performance)
Easier to use
Specific to CSS
SSR Friendly development build, focused on frontend DX
Works seamlessly with the Universal family
Works fantastically as a standalone style loader (You can use it for any webpack project! with no extra dependencies!)
Async styles do not render block webkit browsers, if you use the insert option

Additionally, if you are already a user of the universal family -- we will be waving goodbye to the mandatory window.__CSS_CHUNKS__.

The 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.

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2
3module.exports = {
4  plugins: [new ExtractCssChunks()],
5  module: {
6    rules: [
7      {
8        test: /\.css$/i,
9        use: [ExtractCssChunks.loader, 'css-loader'],
10      },
11    ],
12  },
13};

Options

`publicPath`

Type: String|Function Default: the publicPath in webpackOptions.output

Specifies a custom public path for the target file(s).

`String`

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2
3module.exports = {
4  plugins: [
5    new ExtractCssChunks({
6      // Options similar to the same options in webpackOptions.output
7      // both options are optional
8      filename: '[name].css',
9      chunkFilename: '[id].css',
10    }),
11  ],
12  module: {
13    rules: [
14      {
15        test: /\.css$/,
16        use: [
17          {
18            loader: ExtractCssChunks.loader,
19            options: {
20              publicPath: '/public/path/to/',
21            },
22          },
23          'css-loader',
24        ],
25      },
26    ],
27  },
28};

`Function`

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2
3module.exports = {
4  plugins: [
5    new ExtractCssChunks({
6      // Options similar to the same options in webpackOptions.output
7      // both options are optional
8      filename: '[name].css',
9      chunkFilename: '[id].css',
10    }),
11  ],
12  module: {
13    rules: [
14      {
15        test: /\.css$/,
16        use: [
17          {
18            loader: ExtractCssChunks.loader,
19            options: {
20              publicPath: (resourcePath, context) => {
21                return path.relative(path.dirname(resourcePath), context) + '/';
22              },
23            },
24          },
25          'css-loader',
26        ],
27      },
28    ],
29  },
30};

`esModule`

Type: Boolean Default: false

By default, extract-css-chunks-webpack-plugin generates JS modules that use the CommonJS modules syntax. There are some cases in which using ES modules is beneficial, like in the case of module concatenation and tree shaking.

You can enable a ES module syntax using:

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2
3module.exports = {
4  plugins: [new ExtractCssChunks()],
5  module: {
6    rules: [
7      {
8        test: /\.css$/i,
9        use: [
10          {
11            loader: ExtractCssChunks.loader,
12            options: {
13              esModule: true,
14            },
15          },
16          'css-loader',
17        ],
18      },
19    ],
20  },
21};

Examples

Minimal example

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2
3module.exports = {
4  plugins: [
5    new ExtractCssChunks({
6      // Options similar to the same options in webpackOptions.output
7      // all options are optional
8      filename: '[name].css',
9      chunkFilename: '[id].css',
10      ignoreOrder: false, // Enable to remove warnings about conflicting order
11    }),
12  ],
13  module: {
14    rules: [
15      {
16        test: /\.css$/,
17        use: [
18          {
19            loader: ExtractCssChunks.loader,
20            options: {
21              // you can specify a publicPath here
22              // by default it uses publicPath in webpackOptions.output
23              publicPath: '../',
24              hmr: process.env.NODE_ENV === 'development',
25            },
26          },
27          'css-loader',
28        ],
29      },
30    ],
31  },
32};

The `publicPath` option as function

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2
3module.exports = {
4  plugins: [
5    new ExtractCssChunks({
6      // Options similar to the same options in webpackOptions.output
7      // both options are optional
8      filename: '[name].css',
9      chunkFilename: '[id].css',
10    }),
11  ],
12  module: {
13    rules: [
14      {
15        test: /\.css$/,
16        use: [
17          {
18            loader: ExtractCssChunks.loader,
19            options: {
20              publicPath: (resourcePath, context) => {
21                // publicPath is the relative path of the resource to the context
22                // e.g. for ./css/admin/main.css the publicPath will be ../../
23                // while for ./css/main.css the publicPath will be ../
24                return path.relative(path.dirname(resourcePath), context) + '/';
25              },
26            },
27          },
28          'css-loader',
29        ],
30      },
31    ],
32  },
33};

Advanced configuration example

This plugin should be used only on production builds without style-loader in the loaders chain, especially if you want to have HMR in development.

Here is an example to have both HMR in development and your styles extracted in a file for production builds.

(Loaders options left out for clarity, adapt accordingly to your needs.)

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2const devMode = process.env.NODE_ENV !== 'production';
3
4module.exports = {
5  plugins: [
6    new ExtractCssChunks({
7      // Options similar to the same options in webpackOptions.output
8      // both options are optional
9      filename: devMode ? '[name].css' : '[name].[hash].css',
10      chunkFilename: devMode ? '[id].css' : '[id].[hash].css',
11    }),
12  ],
13  module: {
14    rules: [
15      {
16        test: /\.(sa|sc|c)ss$/,
17        use: [
18          {
19            loader: ExtractCssChunks.loader,
20            options: {
21              hmr: process.env.NODE_ENV === 'development',
22            },
23          },
24          'css-loader',
25          'postcss-loader',
26          'sass-loader',
27        ],
28      },
29    ],
30  },
31};

Hot Module Reloading (HMR)

The extract-css-chunks-webpack-plugin supports hot reloading of actual css files in development. Some options are provided to enable HMR of both standard stylesheets and locally scoped CSS or CSS modules. Below is an example configuration of extract-css-chunks for HMR use with CSS modules.

While we attempt to hmr css-modules. It is not easy to perform when code-splitting with custom chunk names. reloadAll is an option that should only be enabled if HMR isn't working correctly. The core challenge with css-modules is that when code-split, the chunk ids can and do end up different compared to the filename.

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2
3module.exports = {
4  plugins: [
5    new ExtractCssChunks({
6      // Options similar to the same options in webpackOptions.output
7      // both options are optional
8      filename: '[name].css',
9      chunkFilename: '[id].css',
10    }),
11  ],
12  module: {
13    rules: [
14      {
15        test: /\.css$/,
16        use: [
17          {
18            loader: ExtractCssChunks.loader,
19            options: {
20              // only enable hot in development
21              hmr: process.env.NODE_ENV === 'development',
22              // if hmr does not work, this is a forceful method.
23              reloadAll: true,
24            },
25          },
26          'css-loader',
27        ],
28      },
29    ],
30  },
31};

Minimizing For Production

To minify the output, use a plugin like optimize-css-assets-webpack-plugin. Setting optimization.minimizer overrides the defaults provided by webpack, so make sure to also specify a JS minimizer:

webpack.config.js

1const TerserJSPlugin = require('terser-webpack-plugin');
2const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
3const OptimizeCSSAssetsPlugin = require('optimize-css-assets-webpack-plugin');
4
5module.exports = {
6  optimization: {
7    minimizer: [new TerserJSPlugin({}), new OptimizeCSSAssetsPlugin({})],
8  },
9  plugins: [
10    new ExtractCssChunks({
11      filename: '[name].css',
12      chunkFilename: '[id].css',
13    }),
14  ],
15  module: {
16    rules: [
17      {
18        test: /\.css$/,
19        use: [ExtractCssChunks.loader, 'css-loader'],
20      },
21    ],
22  },
23};

Using preloaded or inlined CSS

The runtime code detects already added CSS via <link> or <style> tag. This can be useful when injecting CSS on server-side for Server-Side-Rendering. The href of the <link> tag has to match the URL that will be used for loading the CSS chunk. The data-href attribute can be used for <link> and <style> too. When inlining CSS data-href must be used.

Extracting all CSS in a single file

Similar to what extract-text-webpack-plugin does, the CSS can be extracted in one CSS file using optimization.splitChunks.cacheGroups.

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2
3module.exports = {
4  optimization: {
5    splitChunks: {
6      cacheGroups: {
7        styles: {
8          name: 'styles',
9          test: /\.css$/,
10          chunks: 'all',
11          enforce: true,
12        },
13      },
14    },
15  },
16  plugins: [
17    new ExtractCssChunks({
18      filename: '[name].css',
19    }),
20  ],
21  module: {
22    rules: [
23      {
24        test: /\.css$/,
25        use: [ExtractCssChunks.loader, 'css-loader'],
26      },
27    ],
28  },
29};

Extracting CSS based on entry

You may also extract the CSS based on the webpack entry name. This is especially useful if you import routes dynamically but want to keep your CSS bundled according to entry. This also prevents the CSS duplication issue one had with the ExtractTextPlugin.

1const path = require('path');
2const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
3
4function recursiveIssuer(m) {
5  if (m.issuer) {
6    return recursiveIssuer(m.issuer);
7  } else if (m.name) {
8    return m.name;
9  } else {
10    return false;
11  }
12}
13
14module.exports = {
15  entry: {
16    foo: path.resolve(__dirname, 'src/foo'),
17    bar: path.resolve(__dirname, 'src/bar'),
18  },
19  optimization: {
20    splitChunks: {
21      cacheGroups: {
22        fooStyles: {
23          name: 'foo',
24          test: (m, c, entry = 'foo') =>
25            m.constructor.name === 'CssModule' && recursiveIssuer(m) === entry,
26          chunks: 'all',
27          enforce: true,
28        },
29        barStyles: {
30          name: 'bar',
31          test: (m, c, entry = 'bar') =>
32            m.constructor.name === 'CssModule' && recursiveIssuer(m) === entry,
33          chunks: 'all',
34          enforce: true,
35        },
36      },
37    },
38  },
39  plugins: [
40    new ExtractCssChunks({
41      filename: '[name].css',
42    }),
43  ],
44  module: {
45    rules: [
46      {
47        test: /\.css$/,
48        use: [ExtractCssChunks.loader, 'css-loader'],
49      },
50    ],
51  },
52};

Module Filename Option

With the moduleFilename option you can use chunk data to customize the filename. This is particularly useful when dealing with multiple entry points and wanting to get more control out of the filename for a given entry point/chunk. In the example below, we'll use moduleFilename to output the generated css into a different directory.

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2
3module.exports = {
4  plugins: [
5    new ExtractCssChunks({
6      moduleFilename: ({ name }) => `${name.replace('/js/', '/css/')}.css`,
7    }),
8  ],
9  module: {
10    rules: [
11      {
12        test: /\.css$/,
13        use: [ExtractCssChunks.loader, 'css-loader'],
14      },
15    ],
16  },
17};

Long Term Caching

For long term caching use filename: "[contenthash].css". Optionally add [name].

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2
3module.exports = {
4  plugins: [
5    new ExtractCssChunks({
6      filename: '[name].[contenthash].css',
7      chunkFilename: '[id].[contenthash].css',
8    }),
9  ],
10  module: {
11    rules: [
12      {
13        test: /\.css$/,
14        use: [ExtractCssChunks.loader, 'css-loader'],
15      },
16    ],
17  },
18};

Remove Order Warnings

For projects where css ordering has been mitigated through consistent use of scoping or naming conventions, the css order warnings can be disabled by setting the ignoreOrder flag to true for the plugin.

webpack.config.js

1const ExtractCssChunks = require('extract-css-chunks-webpack-plugin');
2
3module.exports = {
4  plugins: [
5    new ExtractCssChunks({
6      ignoreOrder: true,
7    }),
8  ],
9  module: {
10    rules: [
11      {
12        test: /\.css$/i,
13        use: [ExtractCssChunks.loader, 'css-loader'],
14      },
15    ],
16  },
17};

insert

Type: Function Default: head

By default, the extract-css-chunks-plugin appends styles (<link> elements) to document.head of the current window.

However in some circumstances it might be necessary to have finer control over the append target or even delay link elements instertion. For example this is the case when you asynchronously load styles for an application that runs inside of an iframe. In such cases insert can be configured to be a function or a custom selector.

If you target an iframe make sure that the parent document has sufficient access rights to reach into the frame document and append elements to it.

`insert` as a function

Allows to override default behavior and insert styles at any position.

⚠ Do not forget that this code will run in the browser alongside your application. Since not all browsers support latest ECMA features like let, const, arrow function expression and etc we recommend you to use only ECMA 5 features and syntax.

⚠ The insert function is serialized to string and passed to the plugin. This means that it won't have access to the scope of the webpack configuration module.

1new ExtractCssChunksPlugin({
2  insert: function insert(linkTag) {
3    const reference = document.querySelector('#some-element');
4    if (reference) {
5      reference.parentNode.insertBefore(linkTag, reference);
6    }
7  },
8});

A new <link> element will be inserted before the element with id some-element.

Media Query Plugin

If you'd like to extract the media queries from the extracted CSS (so mobile users don't need to load desktop or tablet specific CSS anymore) you should use one of the following plugins:

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

SAST

Determines if the project uses static code analysis.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Reason

98 existing vulnerabilities detected

Details

Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
Warn: Project is vulnerable to: GHSA-6chw-6frg-f759
Warn: Project is vulnerable to: GHSA-v88g-cgmw-v5xw
Warn: Project is vulnerable to: GHSA-whgm-jr23-g3j9
Warn: Project is vulnerable to: GHSA-93q8-gq69-wqmw
Warn: Project is vulnerable to: GHSA-fwr7-v2mv-hh25
Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
Warn: Project is vulnerable to: GHSA-x9w5-v3q2-3rhw
Warn: Project is vulnerable to: GHSA-w8qv-6jwh-64r5
Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
Warn: Project is vulnerable to: GHSA-w573-4hg7-7wgq
Warn: Project is vulnerable to: GHSA-3wcq-x3mq-6r9p
Warn: Project is vulnerable to: GHSA-ff7x-qrg7-qggm
Warn: Project is vulnerable to: GHSA-r9p9-mrjm-926w
Warn: Project is vulnerable to: GHSA-434g-2637-qmqr
Warn: Project is vulnerable to: GHSA-49q7-c7j4-3p7m
Warn: Project is vulnerable to: GHSA-977x-g7h5-7qgw
Warn: Project is vulnerable to: GHSA-f7q4-pwc6-w24p
Warn: Project is vulnerable to: GHSA-fc9h-whq2-v747
Warn: Project is vulnerable to: GHSA-vjh7-7g9h-fjfh
Warn: Project is vulnerable to: GHSA-6h5x-7c5m-7cr7
Warn: Project is vulnerable to: GHSA-rv95-896h-c2vc
Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
Warn: Project is vulnerable to: GHSA-74fj-2j2h-c42q
Warn: Project is vulnerable to: GHSA-pw2r-vq6v-hr8c
Warn: Project is vulnerable to: GHSA-jchw-25xp-jwwc
Warn: Project is vulnerable to: GHSA-cxjh-pqwp-8mfp
Warn: Project is vulnerable to: GHSA-ww39-953v-wcq6
Warn: Project is vulnerable to: GHSA-765h-qjxv-5f44
Warn: Project is vulnerable to: GHSA-f2jv-r9rf-7988
Warn: Project is vulnerable to: GHSA-43f8-2h32-f4cj
Warn: Project is vulnerable to: GHSA-c7qv-q95q-8v27
Warn: Project is vulnerable to: GHSA-qqgx-2p2h-9c37
Warn: Project is vulnerable to: GHSA-78xj-cgh5-2h22
Warn: Project is vulnerable to: GHSA-2p57-rm9w-gvfp
Warn: Project is vulnerable to: GHSA-896r-f27r-55mw
Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
Warn: Project is vulnerable to: GHSA-76p3-8jx3-jpfq
Warn: Project is vulnerable to: GHSA-3rfm-jhwj-7488
Warn: Project is vulnerable to: GHSA-hhq3-ff78-jv3g
Warn: Project is vulnerable to: GHSA-p6mc-m468-83gw
Warn: Project is vulnerable to: GHSA-29mw-wpgm-hmr9
Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
Warn: Project is vulnerable to: GHSA-7wpw-2hjm-89gp
Warn: Project is vulnerable to: GHSA-r6rj-9ch6-g264
Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
Warn: Project is vulnerable to: GHSA-xvch-5gv4-984h
Warn: Project is vulnerable to: GHSA-5rrq-pxf6-6jx5
Warn: Project is vulnerable to: GHSA-8fr3-hfg3-gpgp
Warn: Project is vulnerable to: GHSA-gf8q-jrpm-jvxq
Warn: Project is vulnerable to: GHSA-2r2c-g63r-vccr
Warn: Project is vulnerable to: GHSA-cfm4-qjh2-4765
Warn: Project is vulnerable to: GHSA-x4jg-mjrx-434g
Warn: Project is vulnerable to: GHSA-5fw9-fq32-wv5p
Warn: Project is vulnerable to: GHSA-8g77-54rh-46hx
Warn: Project is vulnerable to: GHSA-hj48-42vr-x3v9
Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
Warn: Project is vulnerable to: GHSA-rhx6-c78j-4q9w
Warn: Project is vulnerable to: GHSA-h7cp-r72f-jxh6
Warn: Project is vulnerable to: GHSA-v62p-rq8g-8h59
Warn: Project is vulnerable to: GHSA-566m-qj78-rww5
Warn: Project is vulnerable to: GHSA-hwj9-h5mp-3pm3
Warn: Project is vulnerable to: GHSA-7fh5-64p2-3v2j
Warn: Project is vulnerable to: GHSA-hrpp-h998-j3pp
Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
Warn: Project is vulnerable to: GHSA-44c6-4v22-4mhx
Warn: Project is vulnerable to: GHSA-4x5v-gmq8-25ch
Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
Warn: Project is vulnerable to: GHSA-g4rg-993r-mgx7
Warn: Project is vulnerable to: GHSA-4rq4-32rv-6wp6
Warn: Project is vulnerable to: GHSA-64g7-mvw6-v9qj
Warn: Project is vulnerable to: GHSA-c9g6-9335-x697
Warn: Project is vulnerable to: GHSA-vx3p-948g-6vhq
Warn: Project is vulnerable to: GHSA-4wf5-vphf-c2xc
Warn: Project is vulnerable to: GHSA-jgrx-mgxx-jf9v
Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
Warn: Project is vulnerable to: GHSA-7p7h-4mm5-852v
Warn: Project is vulnerable to: GHSA-38fc-wpqx-33j7
Warn: Project is vulnerable to: GHSA-9m6j-fcg5-2442
Warn: Project is vulnerable to: GHSA-hh27-ffr2-f2jc
Warn: Project is vulnerable to: GHSA-rqff-837h-mm52
Warn: Project is vulnerable to: GHSA-8v38-pw62-9cw2
Warn: Project is vulnerable to: GHSA-hgjh-723h-mx2j
Warn: Project is vulnerable to: GHSA-jf5r-8hm2-f872
Warn: Project is vulnerable to: GHSA-wr3j-pwj9-hqq6
Warn: Project is vulnerable to: GHSA-4v9v-hfq4-rm2v
Warn: Project is vulnerable to: GHSA-9jgg-88mc-972h
Warn: Project is vulnerable to: GHSA-j8xg-fqg3-53r7
Warn: Project is vulnerable to: GHSA-6fc8-4gx4-v693
Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
Warn: Project is vulnerable to: GHSA-p9pc-299p-vxgp

Score

1.7

/10

Last Scanned on 2025-06-30

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More

@prepair/extract-css-chunks-webpack-plugin

Installations

Developer Guide

Yes

CommonJS

>= 6.9.0

14.15.1

6.14.9

Score

Pull Requests

0

0

0

Issues

0

0

0

Releases

Unable to fetch releases

Languages

Developer

prepair

Download Statistics

GitHub Statistics

Bundle Size

290.26 kB

78.19 kB

Maintainers

Package Meta Information

Total Downloads

1,558

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

Peer Dependencies

Dev Dependencies

extract-css-chunks-webpack-plugin

🍾🍾🍾It's our absolute pleasure to announce Webpack 4 Support 🚀🚀🚀

Perks

Options

publicPath

String

Function

esModule

Examples

Minimal example

The publicPath option as function

Advanced configuration example

Hot Module Reloading (HMR)

Minimizing For Production

Using preloaded or inlined CSS

Extracting all CSS in a single file

Extracting CSS based on entry

Module Filename Option

Long Term Caching

Remove Order Warnings

insert

insert as a function

Media Query Plugin

10

10

0

0

0

0

0

0

0

0

1.7

/10

`publicPath`

`String`

`Function`

`esModule`

The `publicPath` option as function

`insert` as a function