Use other package managers (e.g yarn or pnpm)?

[khaosdoctor]

Question

We've started seeing some errors in the QLTY builds because it tries to install packages with npm install --force --no-package-lock, but we don't use npm, we use yarn. Usually this is not an issue, but since our project is a monorepo project using Yarn workspaces, both package managers are incompatible.

We do, however, have the packageManager key in the package.json that would allow Corepack to install yarn and use it, but it's not being done. And I haven't found any straightforward way of changing the default installer in QLTY's docs.

How to reproduce (optional)

1. Create a yarn workspaces project
2. Try to run it in QLTY

Expected behavior (optional)

The packages are installed and the build executes

CLI Version

qlty 0.558.0 linux-x64 (b0a3def 2025-07-27)

Information about Qlty configuration and environment (optional)

We don't have anything set up

[brynary]

Hi @khaosdoctor -- Thank you for this report. Support for other JS package managers beyond NPM is something that we would consider for the future.

One technique that we often recommend is using a separate package.json file specifically for your JS static analysis tools. The advantage of this is that Qlty will be faster (since it won't need to install app dependencies), and also it guarantees that a static analysis tool update will never cause an app bug (due to e.g. a shared dependency change). So you might try Yarn for your app and NPM just for Qlty.

We'll provide an update here if / when we add support for other package managers.

Best, -Bryan

[khaosdoctor]

Thanks @brynary, we'll be waiting, right now we are using the CircleCI orb, but it'd be amazing if we could remove it from the CI and use the app instead. I'll be waiting :)