-
Notifications
You must be signed in to change notification settings - Fork 240
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
JFrog CLI support the pnpm to build the nodejs project #2356
Comments
That would be a good plus. |
This is a blocker for our organization that prevents us from using Jfrog for our pnpm projects. |
Any word on adding support? |
Currently Artifactory server does not officially support the pnpm client although it should work utilising our npm APIs and protocols. |
@eyalbe4 Sorry for the double-mention - deleted my previous post after reading properly. As pnpm is pretty popular lately in the Node.js world, I would vote for adding support to the Artifactory server. Is there a feature request for that already, and if not, would it make sense to open one for this specific issue? |
@renet, |
Is there any new update for this feature ? More and more Pnpm users, pointed out that JFrog cli cannot scan the pnpm-lock.yaml file. Other scanning tools already support pnpm projects SCA scan. |
Is your feature request related to a problem? Please describe.
The JFrog CLI supports the npm and the yarn to build the nodejs project but doesn't support the pnpm to build, So wants the JFrog CLI can support the pnpm to run build in nodejs project and can deploy the buildinfo to the Artifactory like npm and yarn.
Describe the solution you'd like to see
Hope the JFrog CLI support the pnpm to build the nodejs project like it support npm and yarn.
Describe alternatives you've considered
Because the JFrog CLI currently supports npm and yarn to build the nodejs projects, the pnpm is not supported now, hope the JFrog CLI can support the use of pnpm to build nodejs projects and upload the buildinfo to Artifactory.
The text was updated successfully, but these errors were encountered: