-
-
Notifications
You must be signed in to change notification settings - Fork 26.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
InlineChunkHtmlPlugin works with empty publicPath #6735
InlineChunkHtmlPlugin works with empty publicPath #6735
Conversation
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed. If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
Co-Authored-By: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
n.b. for other reviewers, this is not a bug. It only affects users who eject from Create React App or use our plugins in non-CRA applications. |
I mean, it is a bug. It just happens to only affect people who eject from CRA (like my case). Still, it's not less of a bug :) |
@Timer any update on this? When can it be merged? |
Ping :) |
Thanks! |
The
InlineChunkHtmlPlugin
plugin didn't work when thepublicPath
variable is empty or unset (e.g. when I want to use relative URLs).Before:
publicPath
was unset or wasn't a string, webpack would throw an errorpublicPath
was an empty string, the plugin would fail to inline a chunkNow: the plugin behaves as expected even with empty or unset
publicPath
.