Skip to content

Conversation

@bdwain
Copy link
Contributor

@bdwain bdwain commented Jan 18, 2017

This changes the behavior of the --open flag to open the browser to the --public url if it is specified. (the default will be the host like before).

The original issue is #739 , though it will also address #725 by letting you specify localhost as the --public url.

This is not a breaking change.

This is also addressed for version 1 with #748

});

if(options.inline !== false) {
const devClient = [`${require.resolve("../client/")}?${options.public ? `${protocol}://${options.public}` : domain}`];
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this line behaves the same, but domain is also used on line 375 to calculate the url that gets opened, and that's where the behavior changes

@bdwain
Copy link
Contributor Author

bdwain commented Jan 22, 2017

@SpaceK33z Is there anything else you wanted done for this?

@SpaceK33z
Copy link
Member

@bdwain, I am planning to merge this after the 2.2 release (2.2 has been published but not yet with the latest tag). So it's fine!

@bdwain
Copy link
Contributor Author

bdwain commented Jan 22, 2017

cool!

@SpaceK33z SpaceK33z merged commit 2cf2939 into webpack:master Feb 1, 2017
@SpaceK33z
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants