DOC: Improves clarity around publicPath usage in workers #7730
+11
−1
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.
issue #6716
Summary
This PR improves the Web Workers guide by clarifying when setting
__webpack_public_path__from within a worker is required and why this pattern is necessary in certain runtime setups. The changes aim to reduce confusion for users encountering this advanced use case.What kind of change does this PR introduce?
docs
This PR only updates documentation and does not change any runtime behavior.
The PR adds contextual documentation explaining when dynamic
publicPathhandling is required for Web Workers and clarifies the scope of the Node.js section.