Skip to content
This repository was archived by the owner on Mar 17, 2021. It is now read-only.

fix: allow the usage of an empty string as publicPath #122

Closed
wants to merge 1 commit into from

Conversation

mlegenhausen
Copy link

@mlegenhausen mlegenhausen commented Feb 3, 2017

This pull request enforces a more strict check of publicPath to prevent the interpretation of empty string as false value. This allows to disable the prefixing of publicPath with __webpack_public_path__ without the need to provide a function that simply returns the url as given.

Current work around would be to use

query: {
  publicPath: (url) => url
}

This pull request enforces a more strict check of `publicPath` to prevent the interpretation of empty string as false value. This allows to disable the prefixing of `publicPath` with `__webpack_public_path__` without the need to provide a function that simply returns the `url` as given.

Current work around would be to use

```js
query: {
  publicPath: (url) => url
}
```
@michael-ciniawsky michael-ciniawsky self-assigned this Apr 11, 2017
@michael-ciniawsky michael-ciniawsky changed the title Allow the usage of an empty string as publicPath fix: allow the usage of an empty string as publicPath Apr 11, 2017
@michael-ciniawsky
Copy link
Member

Closed in favour of #145. Thx

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants