Load existing webpack.config.js file... don't require 'webpack' entry.

[burtonator]

I'm a bit confused by how the webpack config is specified.

I think it's generating it's own if you don't' specify it in karma.conf.js

The problem is that my webpack is super complicated, loads plugins, etc.

I'd rather it be simple but it's not.

I can't 'require' the webpack as karma-webpack then gives me an error saying the configuration isn't valid.

I'm not sure the right strategy here. The existing config might not be readable as JSON so you can't really change it directly.

I'm REALLY trying to avoid repeating myself in my config as I have far far too many duplicate config files as it is.

[codymikol]

You should not specify an entry point as this is something that happens internally. I made an issue over here about handling this invalid field in configuration. Do you think that would solve your issue?

[codymikol]

closing due to inactivity