CLI: Use closest lockfile to determine package manager #20464
Merged
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: #20463
What I did
Sometimes people have a
yarn.lock
file in their home directory accidentally, and if they do, Storybook CLI uses yarn, even if their package is using pnpm and has a pnpm lock file.With this change, instead of looking for yarn.lock and pnpm-lock.yaml independently, we look for both at the same time, and
find-up
returns the closest one (falling back to yarn if there are multiple in the same directory).How to test