-
-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
__webpack_public_path__ does not work in webpack 2 #3265
Comments
It does work. Could you add a complete example? Check twice that |
@leaves4j have you been able to verify this, otherwise I'll close this until you come across a concrete example. |
similar issue here. I'm using |
should I open a new issue ? question about
is |
my webpack config. webpack@2.2.0-rc.2
|
@lili21 That's the solution you're looking for: #2776 (comment) And no, that's not a bug, it is known behavior. |
Looks like my issue is related to |
Per https://webpack.js.org/guides/public-path/#set-value-on-the-fly:
However if This then breaks |
Reassigning |
I've been able to remove my workarounds after upgrading to webpack@3 and file-loader@0.11.2. |
@novemberborn Comments seem correct to me but I still have the issue with
But this should be avoided. So shouldn't |
This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days. |
Issue was closed because of inactivity. If you think this is still a valid issue, please file a new issue with additional information. |
I'm submitting a bug report
Webpack version:
2.1.0-beta.25
Please tell us about your environment:
OSX 10.x
Current behavior:
set
__webpack_public_path__
doesn't workExpected/desired behavior:
I set
__webpack_public_path__
= 'assets' in entry.js,then useSystem.import('xxxx')
, the require path doesn't contain 'assetsBrowser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Language: [ES6/7]
The text was updated successfully, but these errors were encountered: