Include side effects of re-exporters unless they have no moduleSideEffects #4867
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.
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
sideEffects
#4470sideEffects
doesn't seem to be working correctly vitejs/vite#7635sideEffects
plugins#1159Description
If a module with
moduleSideEffects:false
is reexporting from a module withmoduleSideEffects:true
that again is reexporting from another file, currently neither side effects in the first reexporter nor in the second reexporter are included.As this defeats expectations of many, this PR changes the logic so that in this case, side effects of the reexporter with
moduleSideEffects:true
ARE indeed included, hopefully solving the issues that many people had.Note that as before, side effects are always included if the module does not use a reexport but rather imports the value and then directly exports it, independent of the
moduleSideEffects
value.