Skip to content

Commit 2ed8c60

Browse files
prod3v3loperevenstensberg
authored andcommitted
Correction of the webpack-merge configuration
After several attempts and my question on stackoverflow https://stackoverflow.com/questions/54350271/webpack-scaffold-webpackoptions-merge-not-work-why I found the problem in the file https://github.com/webpack /webpack-cli/blob/eb06af8c2994cd1fea8d2c687de16bbf2f10095a/packages/utils/modify-config-helper.ts merge will not be passed to the webpackOptions but stand alone, like topScope for example.
1 parent 4df0000 commit 2ed8c60

1 file changed

Lines changed: 9 additions & 3 deletions

File tree

SCAFFOLDING.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -60,11 +60,17 @@ As with a regular webpack configuration, this property behaves the same. Inside
6060
```js
6161
this.options.env.configuration.dev.webpackOptions = {
6262
entry: '\'app.js\'',
63-
output: {....},
64-
merge: 'myConfig'
63+
output: {....}
6564
};
6665
```
67-
If you want to use `webpack-merge`, you can supply `webpackOptions` with the merge property, and the configuration you want to merge it with.
66+
67+
### `myObj.merge` (optional)
68+
69+
If you want to use `webpack-merge`, you can supply `merge` with the merge property, and the configuration you want to merge it with.
70+
71+
```js
72+
this.options.env.configuration.dev.merge = 'myConfig';
73+
```
6874

6975
### `myObj.topScope`(optional)
7076

0 commit comments

Comments
 (0)