fix(bundling): fix webpack publicPath: 'auto'
behavior for esm
builds
#13186
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's a lot more detail in the issue I opened, but I'll summarize the output changes here.
When building with webpack and:
output.publicPath
is set toauto
or omitted (it defaults toauto
)module
when injected in the html markup (i.e.esm: true
)The wrong snippet from the webpack AutoPublicPathRuntimeModule template is injected
Current Behavior
Current output uses
document.currentScript
which is not supported fortype="module"
scriptsMinified (note the
currentScript
usage):With minification manually disabled:
Expected Behavior
After this change:
Minified (not
import.meta.url
usage):With minification manually disabled:
Related Issue(s)
Fixes #13185