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
It would be great if salus supported pnpm support in addition to npm and yarn. The output of pnpm audit --json is identical to NPM, so hopefully this is a simple request :)
One caveat to be aware of is that pnpm places the lockfile at the the root of the repository in a monorepo/workspaces setup. For example:
If package-a had its own salus-config.yaml, and we were running the scanner with --repo_path=/some/path/to/package-a, the should_run check would need to recursively look upwards for the folder containing .git and see if pnpm-lock.yaml exists at the same level.
The text was updated successfully, but these errors were encountered:
@apazzolini Apologies, we missed your message earlier, and thank you for describing the caveats.
Unfortunately, this will not be a very simple task. We most likely will not be able to look into pnpm until next year and we might not be able to support it.
It would be great if salus supported pnpm support in addition to npm and yarn. The output of
pnpm audit --json
is identical to NPM, so hopefully this is a simple request :)One caveat to be aware of is that pnpm places the lockfile at the the root of the repository in a monorepo/workspaces setup. For example:
If
package-a
had its ownsalus-config.yaml
, and we were running the scanner with--repo_path=/some/path/to/package-a
, theshould_run
check would need to recursively look upwards for the folder containing.git
and see ifpnpm-lock.yaml
exists at the same level.The text was updated successfully, but these errors were encountered: