Forcing the server to always open to the publicPath isn't always what I want. In my case, I want my webpack bundle served from http://localhost/build, but run the server from http://localhost. I have webpack configured with a publicPath: '/build/ but want, webpack-browser-plugin to open the server page to /.
Can you make the options.publicPath object in webpack-browser-plugin take priority over the webpack publicPath configuration so I can override it (similar to how openOptions works)?
I am currently using 1.0.12 to achieve what I need.
Forcing the server to always open to the
publicPathisn't always what I want. In my case, I want my webpack bundle served fromhttp://localhost/build, but run the server fromhttp://localhost. I have webpack configured with apublicPath: '/build/but want,webpack-browser-pluginto open the server page to/.Can you make the
options.publicPathobject inwebpack-browser-plugintake priority over the webpackpublicPathconfiguration so I can override it (similar to howopenOptionsworks)?I am currently using 1.0.12 to achieve what I need.