-
-
Notifications
You must be signed in to change notification settings - Fork 257
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be good to write a test (if possible) but I think it's fine.
It already has two to cover the feature in question, just changing how we init publicPath because of the issue mentioned in the PR that broke it. The problem was the strict check for |
Ok, cool. JS. 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@d3viant0ne Thx 👍 😛
@@ -61,7 +61,7 @@ module.exports = function(content) { | |||
} | |||
|
|||
var publicPath = "__webpack_public_path__ + " + JSON.stringify(url); | |||
if (config.publicPath !== false) { | |||
if (config.publicPath !== undefined) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if (!config.publicPath) {}
Maybe even 'safer', but enterily a nitpick
Any news regarding this bug? |
@d3viant0ne @bebraw Is there anything left to do here/blocking this ? :) |
publicPath
to undefined
@michael-ciniawsky Nothing that I know of. |
Please semver patch someone when time :) |
What kind of change does this PR introduce?
bugfix
Did you add tests for your changes?
If relevant, did you update the README?
Summary
Initializing
publicPath
to false was preventing the new option from being used withwebpack-config-validator
See comment in #145
Does this PR introduce a breaking change?
No
Other information
Fixes #158