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

UA issue when pnpm is used alongside with Lerna #51

Open
dwiyatci opened this issue Nov 3, 2023 · 0 comments
Open

UA issue when pnpm is used alongside with Lerna #51

dwiyatci opened this issue Nov 3, 2023 · 0 comments

Comments

@dwiyatci
Copy link

dwiyatci commented Nov 3, 2023

Hi, here's my setup:

  • pnpm-lock.yaml file sits side-by-side with lerna.json
  • npmClient in my lerna.json is set to pnpm
  • npm.resolveDependencies=true and npm.resolveLockFile=true in my wss-unified-agent.config

According to https://docs.mend.io/bundle/unified_agent/page/unified_agent_configuration_parameters.html#JavaScript:

If a Lerna.json file is identified, then Lerna’s npmClient will determine if to run npm or yarn resolution.

The pnpm-lock.yaml file will be resolved if it is the only lock file identified next to the package.json file.

When the scan runs, though, the UA seems to prioritise lerna.json over pnpm-lock.yaml. Thing is, the UA doesn't seem to support pnpm as Lerna's npmClient because it keeps complaining that package-lock.json file is not there when resolving the dependencies. My expectation is either:

  • pnpm-lock.yaml takes precedence over lerna.json, or
  • pnpm is supported as Lerna's npmClient when lerna.json is used.

Thoughts? Thank you.

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

No branches or pull requests

1 participant