Closed dwu359 closed 11 months ago
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication
@dwu359 can you add an explanation in the github issue (or pr) for why we want to use pnpm over yarn? have we ensured that pnpm can still install any node dependency we want to use in the future (at least for 90+% of our potential usecases).
@dwu359 can you add an explanation in the github issue (or pr) for why we want to use pnpm over yarn? have we ensured that pnpm can still install any node dependency we want to use in the future (at least for 90+% of our potential usecases).
From what I've read, pnpm is slightly faster than yarn berry and uses up less space than yarn because it utilizes symlinks instead of directly copying packages. That did seem the case for my machine, but I'll need other ppl to try it out also if that is the case. Pnpm was able to install basically anything that I threw at it, since it installs from the npm registry.
Actually if you look at the build times for https://github.com/DSGT-DLP/Deep-Learning-Playground/actions/workflows/node.js.yml, it does seem to be about 20s faster
Works on my laptop
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication
pnpm
What solution does this PR provide?
Switches package management from yarn to pnpm for frontend and serverless.
Also modified the dlp-cli so that it uses pnpm instead of yarn. Also add a --yarn flag in case if anyone is in the process of transitioning from yarn to pnpm.
Also modified node build check workflow to use pnpm instead of yarn.
Testing Methodology Everything was able to be installed via pnpm.
Any other considerations https://github.com/DSGT-DLP/dlp-cli/pull/11