You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.[Read and sign the CLA](https://cla.js.foundation/webpack/webpack.js.org). This needs to be done only once. PRs that haven't signed it won't be accepted.
2
+
2. Make sure your PR complies with [the writer's guide](https://webpack.js.org/writers-guide/).
3
+
3. Read through the PR diff carefully as sometimes this can reveal issues. The work will be reviewed, but this can save some effort.
4
+
4. Remove these instructions from your PR as they are for your eyes only.
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
***extract:** return an array of loader objects ([#343](https://github.com/webpack/extract-text-webpack-plugin/issues/343)) ([74b86e0](https://github.com/webpack/extract-text-webpack-plugin/commit/74b86e0))
17
+
18
+
19
+
20
+
# Change Log
21
+
22
+
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
The API has changed since version 1. For the webpack 1 version, see [the README in the webpack-1 branch](https://github.com/webpack/extract-text-webpack-plugin/blob/webpack-1/README.md).
4
-
5
-
## Install
6
-
7
-
> You can either install it with [npm](https://nodejs.org/en/) or [yarn](https://yarnpkg.com/)
It moves every `require("style.css")` in entry chunks into a separate css output file. So your styles are no longer inlined into the javascript, but separate in a css bundle file (`styles.css`). If your total stylesheet volume is big, it will be faster because the stylesheet bundle is loaded in parallel to the javascript bundle.
37
-
38
-
Advantages:
49
+
It moves every `require("style.css")` in entry chunks into a separate CSS file. So your styles are no longer inlined into the JS bundle, but separate in a CSS bundle file (`styles.css`). If your total stylesheet volume is big, it will be faster because the CSS bundle is loaded in parallel to the JS bundle.
39
50
40
-
* Fewer style tags (older IE has a limit)
41
-
* CSS SourceMap (with `devtool: "source-map"` and `css-loader?sourceMap`)
42
-
* CSS requested in parallel
43
-
* CSS cached separate
44
-
* Faster runtime (less code and DOM operations)
51
+
|Advantages|Caveats|
52
+
|:---------|:------|
53
+
| Fewer style tags (older IE has a limit) | Additional HTTP request |
54
+
| CSS SourceMap (with `devtool: "source-map"` and `extract-text-webpack-plugin?sourceMap`) | Longer compilation time |
55
+
| CSS requested in parallel | No runtime public path modification |
56
+
| CSS cached separate | No Hot Module Replacement |
57
+
| Faster runtime (less code and DOM operations) | ... |
45
58
46
-
Caveats:
59
+
<h2align="center">Options</h2>
47
60
48
-
* Additional HTTP request
49
-
* Longer compilation time
50
-
* More complex configuration
51
-
* No runtime public path modification
52
-
* No Hot Module Replacement
53
-
54
-
## API
55
-
56
-
```javascript
61
+
```js
57
62
newExtractTextPlugin(options: filename | object)
58
63
```
59
64
60
-
*`options.filename: string`_(required)_ the filename of the result file. May contain `[name]`, `[id]` and `[contenthash]`
61
-
*`[name]` the name of the chunk
62
-
*`[id]` the number of the chunk
63
-
*`[contenthash]` a hash of the content of the extracted file
64
-
*`options.allChunks: boolean` extract from all additional chunks too (by default it extracts only from the initial chunk(s))
65
-
*`options.disable: boolean` disables the plugin
66
-
*`options.id: string` Unique ident for this plugin instance. (For advanced usage only, by default automatically generated)
65
+
|Name|Type|Description|
66
+
|:--:|:--:|:----------|
67
+
|**`id`**|`{String}`|Unique ident for this plugin instance. (For advanced usage only, by default automatically generated)|
68
+
|**`filename`**|`{String}`|Name of the result file. May contain `[name]`, `[id]` and `[contenthash]`|
69
+
|**`options.allChunks`**|`{Boolean}`|Extract from all additional chunks too (by default it extracts only from the initial chunk(s))|
70
+
|**`options.disable`**|`{Boolean}`|Disables the plugin|
71
+
72
+
*`[name]` name of the chunk
73
+
*`[id]` number of the chunk
74
+
*`[contenthash]` hash of the content of the extracted file
75
+
76
+
> :warning:`ExtractTextPlugin` generates a file **per entry**, so you must use `[name]`, `[id]` or `[contenthash]` when using multiple entries.
67
77
68
-
The `ExtractTextPlugin` generates an output file per entry, so you must use `[name]`, `[id]` or `[contenthash]` when using multiple entries.
Creates an extracting loader from an existing loader. Supports loaders of type `{ loader: string; query: object }`.
75
85
76
-
*`options.loader: string | object | loader[]`_(required)_ the loader(s) that should be used for converting the resource to a css exporting module
77
-
*`options.fallbackLoader: string | object | loader[]` the loader(s) that should be used when the css is not extracted (i.e. in an additional chunk when `allChunks: false`)
78
-
*`options.publicPath: string` override the `publicPath` setting for this loader
86
+
|Name|Type|Description|
87
+
|:--:|:--:|:----------|
88
+
|**`options.loader`**|`{String}`/`{Object}`|Loader(s) that should be used for converting the resource to a CSS exporting module _(required)_|
89
+
|**`options.fallbackLoader`**|`{String}`/`{Object}`|loader(e.g `'style-loader'`) that should be used when the CSS is not extracted (i.e. in an additional chunk when `allChunks: false`)|
90
+
|**`options.publicPath`**|`{String}`|Override the `publicPath` setting for this loader|
79
91
80
-
There is also an `extract` function on the instance. You should use this if you have more than one `ExtractTextPlugin`.
81
92
82
-
```javascript
83
-
let ExtractTextPlugin =require('extract-text-webpack-plugin');
93
+
#### Multiple Instances
84
94
85
-
// multiple extract instances
86
-
let extractCSS =newExtractTextPlugin('stylesheets/[name].css');
87
-
let extractLESS =newExtractTextPlugin('stylesheets/[name].less');
95
+
There is also an `extract` function on the instance. You should use this if you have more than one instance of `ExtractTextPlugin`.
Webpack standard Automatic versioning and CHANGELOG management, using GitHub's new squash button and
4
+
the [recommended workflow](https://github.com/conventional-changelog/conventional-changelog-cli#recommended-workflow) for `conventional-changelog`.
5
+
6
+
## Pull requests into `master`
7
+
8
+
1. When you land commits on your `master` branch, select the _Squash and Merge_ option.
9
+
2. Add a title and body that follows the [conventional-changelog-standard conventions](https://github.com/bcoe/conventional-changelog-standard/blob/master/convention.md).
10
+
3. Land It!
11
+
12
+
## Cut a standard release
13
+
14
+
```sh
15
+
# npm run script
16
+
npm run release
17
+
# or global bin
18
+
standard-version
19
+
```
20
+
21
+
_This will increment the package version based on commit history from the last tag, update the changelog accordingly, commits the changes & cuts a **local tag**_
22
+
23
+
### When satisfied with the local tag, push it up to master.
24
+
25
+
```sh
26
+
# commandline
27
+
git push --follow-tags origin master
28
+
```
29
+
30
+
## Cut a pre-release
31
+
32
+
Use the flag `--prerelease` to generate pre-releases:
33
+
34
+
_Example: Given the last version of the package is `1.0.0`, and your code to be committed has `semver: patch` level changes..._
35
+
36
+
```bash
37
+
# npm run script ( name === alpha, beta, rc )
38
+
npm run release -- --prerelease <name>
39
+
```
40
+
41
+
_this will tag the version `1.0.1-alpha.0`_
42
+
43
+
## Cut a target release version imperatively like `npm version`
44
+
45
+
To forgo the automated version bump use `--release-as` with the argument `major`, `minor` or `patch`:
46
+
47
+
Suppose the last version of your code is `1.0.0`, you've only landed `fix:` commits, but
48
+
you would like your next release to be a `minor`. Simply do:
49
+
50
+
```bash
51
+
# npm run script
52
+
npm run release -- --release-as minor
53
+
```
54
+
55
+
_you will get version `1.1.0` rather than the auto generated version `1.0.1`._
56
+
57
+
> **NOTE:** you can combine `--release-as` and `--prerelease` to generate a release. This is useful when publishing experimental feature(s).
58
+
59
+
## Signing commits and tags
60
+
61
+
If you have your GPG key set up, add the `--sign` or `-s` flag to your `standard-version` command.
0 commit comments