search

webcompat / webcompat-reporter-extensions

Browser extensions to help report site compatibilty issues.
26 stars 21 forks source link

Determine the feasibility of using a single webpack.config file to build all extensions #126

Closed laghee closed 6 years ago

laghee commented 6 years ago

Having four separate files means a lot of repeated code and four files to update going forward.

magsout commented 6 years ago

my 2 cent, @laghee did you look webpack-merge?

laghee commented 6 years ago

@magsout I did -- that was my original impulse. But then I messed around with it for a while, and it almost seemed like it would wind up being more complicated rather than less. Since the config files are so similar, with differences evenly distributed throughout, I was having trouble finding enough to even make a common base file.

I saw a few examples of one-file merge configs, but almost all of them follow production/development divisions, which is relatively simple since it only means adding in a discrete plugin or loader or whatever. Here it's individual bits within the plugin, and that basically stalled me since every time I tried to split up the plugin it just added more complexity.

Totally possible that there's a better way!