Skip to content

fix: use nearest pkg to resolved for moduleSideEffects#12628

Merged
patak-cat merged 1 commit intomainfrom
fix/use-nearest-pkg-to-resolved-for-moduleSideEffects
Mar 28, 2023
Merged

fix: use nearest pkg to resolved for moduleSideEffects#12628
patak-cat merged 1 commit intomainfrom
fix/use-nearest-pkg-to-resolved-for-moduleSideEffects

Conversation

@patak-cat
Copy link
Member

@patak-cat patak-cat commented Mar 28, 2023

Description

@bluwy checked that this is how it works in rollup. And it is also how it already works inside tryNodeResolve.

close #6740
close #7979


What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@patak-cat patak-cat added the p3-minor-bug An edge case that only affects very specific usage (priority) label Mar 28, 2023
Copy link
Member

@sapphi-red sapphi-red left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

I tested with #6740, #7979 and both of them was fixed 🎉

@patak-cat patak-cat merged commit 1dfecc8 into main Mar 28, 2023
@patak-cat patak-cat deleted the fix/use-nearest-pkg-to-resolved-for-moduleSideEffects branch March 28, 2023 13:01
@patak-cat
Copy link
Member Author

Thanks a lot for testing these issues @sapphi-red 💚

@bluwy
Copy link
Member

bluwy commented Mar 28, 2023

A bit late, but it would be nice to add tests for this to prevent future regressions. Thanks for fixing this though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

p3-minor-bug An edge case that only affects very specific usage (priority)

Projects

None yet

3 participants