Skip to content
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

fix(nm): optimize hoisting by treating peer deps same as other deps #6517

Merged
merged 3 commits into from
Sep 24, 2024

Conversation

akwodkiewicz
Copy link
Contributor

@akwodkiewicz akwodkiewicz commented Sep 24, 2024

What's the problem this PR addresses?

Fixes #6516

How did you fix it?

Simplified the sorting algorithm in getHoistIndetMap.

Checklist

  • I have set the packages that need to be released for my changes to be effective.
  • I will check that all automated PR checks pass before the PR gets reviewed.

akwodkiewicz and others added 2 commits September 24, 2024 12:23
…nces

Until now the peerDependencies had a higher preference that could lead to
unoptimal hoisting behaviour.

Thanks to @larixer for pointing out to this particular snippet.

Co-Authored-By: Victor Vlasenko <victor.vlasenko@sysgears.com>
@akwodkiewicz akwodkiewicz changed the title Fix/nm hoisting algorithm fix(nm): optimize hoisting by treating peer deps same as other deps Sep 24, 2024
@larixer larixer added this pull request to the merge queue Sep 24, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 24, 2024
@larixer larixer added this pull request to the merge queue Sep 24, 2024
Merged via the queue into yarnpkg:master with commit d63d411 Sep 24, 2024
32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug?]: Inverse hoisting behaviour
3 participants