Skip to content

publicPath option should be an override of the base webpack configuration #20

@EvHaus

Description

@EvHaus

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions