You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**What's the problem this PR addresses?**
<!-- Describe the rationale of your PR. -->
<!-- Link all issues that it closes. (Closes/Resolves #xxxx.) -->
`Configuration.findProjectCwd` is written to support both a `lockfile`
lookup (which is kind of a mixed lookup anyways) and a `manifest`
lookup. `Configuration.find` supports both these lookups and also
`ProjectLookup.NONE`, which only looks inside the current folder.
`ProjectLookup.MANIFEST` isn't used anywhere, and `ProjectLookup.NONE`
is only used inside `@yarnpkg/doctor`, but it should never get to run
because `findLockfileWorkspace` runs first and it does a regular mixed
lookup which already succeeds even if there's no lockfile but there's a
manifest.
**How did you fix it?**
<!-- A detailed description of your implementation. -->
I simplified all of this and got rid of the lookups. Now everything does
a mixed ("lockfile") lookup by default.
**Checklist**
<!--- Don't worry if you miss something, chores are automatically
tested. -->
<!--- This checklist exists to help you remember doing the chores when
you submit a PR. -->
<!--- Put an `x` in all the boxes that apply. -->
- [X] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).
<!-- See
https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
for more details. -->
<!-- Check with `yarn version check` and fix with `yarn version check
-i` -->
- [X] I have set the packages that need to be released for my changes to
be effective.
<!-- The "Testing chores" workflow validates that your PR follows our
guidelines. -->
<!-- If it doesn't pass, click on it to see details as to what your PR
might be missing. -->
- [X] I will check that all automated PR checks pass before the PR gets
reviewed.
0 commit comments