We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The following test is supposed to check if pnpm-workspace.yaml is present at ./test/pnpm-workspace/pnpm-workspace.yaml:
pnpm-workspace.yaml
./test/pnpm-workspace/pnpm-workspace.yaml
packages/preferred-pm/test/index.js
Lines 38 to 42 in 2b2c832
However, the source is actually looking up for pnpm-lock.yaml:
pnpm-lock.yaml
packages/preferred-pm/index.js
Lines 41 to 47 in 2b2c832
If you delete this monorepo's pnpm-lock.yaml, the test fails.
Ideally, this package should look up the directory tree for either pnpm-lock.yaml or pnpm-workspace.yaml:
const { findUp } = await import('find-up-simple') if (await findUp('pnpm-lock.yaml', { cwd: pkgPath }) || await findUp('pnpm-workspace.yaml', { cwd: pkgPath })) { ... } // alternatively can use findUpSync const { findUpSync } = await import('find-up-simple') if (findUpSync('pnpm-lock.yaml', { cwd: pkgPath }) || findUpSync('pnpm-workspace.yaml', { cwd: pkgPath })) { ... }
Something similar could probably be done for checking for root-level package-lock.json or yarn.lock too.
package-lock.json
yarn.lock
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Problem
The following test is supposed to check if
pnpm-workspace.yaml
is present at./test/pnpm-workspace/pnpm-workspace.yaml
:packages/preferred-pm/test/index.js
Lines 38 to 42 in 2b2c832
However, the source is actually looking up for
pnpm-lock.yaml
:packages/preferred-pm/index.js
Lines 41 to 47 in 2b2c832
If you delete this monorepo's
pnpm-lock.yaml
, the test fails.Solution
Ideally, this package should look up the directory tree for either
pnpm-lock.yaml
orpnpm-workspace.yaml
:Something similar could probably be done for checking for root-level
package-lock.json
oryarn.lock
too.The text was updated successfully, but these errors were encountered: