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
There is currently no difference but I think we will update this action to install the pnpm binaries instead. So it will be different #18
Also, from pnpm v7, pnpm will not install global packages to the same directory to which npm installs them (pnpm/pnpm#4280). So if you will do just npm i -g pnpm@7, then pnpm i -g eslint will not work.
Using this action adds ~3s to "Set up job" and itself needs ~2s to run, while npm i -g pnpm finishes in <1s. So, you may want to choose the latter if you want to save some seconds1.
I doubt there's any need to do pnpm i -g in the CI.
Out of curiosity, are there any non-syntax/usability benefits to using this action over doing an install with
npm
?:npm i -g pnpm@5 pnpm i --frozen-lockfile # Or `npx pnpm ...`
Or
npx
?:In the case with
npx
, I'm thinking the benefit is simply thatpnpm
can be used multiple times without re-installing.The text was updated successfully, but these errors were encountered: