webpackMerge 0.8.3 unsafe to call twice

[sullivanpt]

Don't know if this is by design or a bug in webpack merge, but attempting to call it twice in a row as in the example results in the 'Client' getting some configuration data from the 'Server'.

module.exports = [
  // Client
  webpackMerge({}, defaultConfig, commonConfig, clientConfig),

  // Server
  webpackMerge({}, defaultConfig, commonConfig, serverConfig)
]

[PatrickJS]

I have to replace webpack-merge with something like extends or create webpack-default

[sullivanpt]

I solved it by wrapping with "_.cloneDeep(webpackMerge(..."

[PatrickJS]

@sullivanpt can you make a PR and use https://www.npmjs.com/package/lodash.clonedeep

[sullivanpt]

I haven't been able to reproduce with webpack-merge@0.7.3 (which is what universal-starter currently depends on) so I'm inclined to consider it a bug in @0.8.3. Needs more investigation I think.

[sullivanpt]

Closing this in favor of survivejs/webpack-merge#12