TThompson759424 (Community Member) asked a question.
My team was looking into migrating our current JavaScript package manager from Yarn 2 to PNPM and wanted to see if that package manager was able to be configured to use the Agent-Based Scan.
It generates a pnpm-lock.yaml instead of a yarn.lock (Yarn) or a package-lock.json (NPM). The node_modules it creates is also a different "flat-level" layout. Would we be able to migrat to PNPM and still get Agent-Based Scans, or do we need to continue with Yarn to achieve this?
.png){kind=logo}
Hello @TThompson759424 (Community Member) ,
If you are planning on migrating to PNPM, it will not allow you to continue to use the Agent-based scans. Also, please note that Veracode does not have any long-term plans to support PNPM.
Jason
Veracode Support Engineer
My front-end team is also moving to a monorepo strcuture and using pnpm. Has there been any change in the stance of supporting pnpm with the Agent-based scan? If not, can I request this support and escalate this request to the product team?