-
Notifications
You must be signed in to change notification settings - Fork 5
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
Broken async chunk URLs from resetting public path #11
Comments
I have the same problem. I searched two days for the problem! https://webpack.js.org/configuration/output/#outputpublicpath Why do you set the publicPath to '' ? Here is my complete mix file:
|
@speniti Are there plans for tackling this issue? Currently, the plugin has become unusable for any project with a custom public path. If the two suggested fixes above won't work, we can keep exploring options. |
I've published a fork of this library to npm that fixes the issue with broken outputs paths of async chunks. |
Describe the bug
Starting in v0.1.3, this plugin resets the
publicPath
config key to solve an issue with duplicate slashes. However, this will break loading async chunks in projects that define a custompublicPath
and which don't load their assets from the root/
but some subfolder like/dist/assets/
.Expected behavior
The plugin shouldn't modify any previously set publicPath.
Suggested fix
I've previously fixed the double-slash issue by adding a manifest transform. Maybe adding this as a default transform makes resetting the public path unnecessary. OTOH, you'd need to be smart about merging the default transform with any user-supplied transform array.
The text was updated successfully, but these errors were encountered: