Skip to content

Commit

Permalink
Correction of the webpack-merge configuration
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
prod3v3loper authored and evenstensberg committed Feb 5, 2019
1 parent 4df0000 commit 2ed8c60
Showing 1 changed file with 9 additions and 3 deletions.
12 changes: 9 additions & 3 deletions SCAFFOLDING.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,11 +60,17 @@ As with a regular webpack configuration, this property behaves the same. Inside
```js
this.options.env.configuration.dev.webpackOptions = {
entry: '\'app.js\'',
output: {....},
merge: 'myConfig'
output: {....}
};
```
If you want to use `webpack-merge`, you can supply `webpackOptions` with the merge property, and the configuration you want to merge it with.

### `myObj.merge` (optional)

If you want to use `webpack-merge`, you can supply `merge` with the merge property, and the configuration you want to merge it with.

```js
this.options.env.configuration.dev.merge = 'myConfig';
```

### `myObj.topScope`(optional)

Expand Down

0 comments on commit 2ed8c60

Please sign in to comment.