Replies: 4 comments 3 replies
-
|
What worries me is that dependabot doesn't support pnpm. I'll try and see what I can do with Renovate |
Beta Was this translation helpful? Give feedback.
-
|
dependabot seems to have a temporal workaround, might work might not |
Beta Was this translation helpful? Give feedback.
-
|
Well, I'm confused. I imported pnpm's workflow and it works just fine until it tries to perform the login sequence, which idfk why wouldn't work |
Beta Was this translation helpful? Give feedback.
-
|
somewhat found the issue, autoeat for some reason is broken. i can't be bothered to check now, but at least the github workflow runs |
Beta Was this translation helpful? Give feedback.
-
|
#32 If Encho wants, he can merge it. There are some changes to do to the wiki I think, I'm not too sure and I can't be bothered to check right now |
Beta Was this translation helpful? Give feedback.
-
|
I agree 100% with migrating to pnpm, the |
Beta Was this translation helpful? Give feedback.
-
|
Oh! I never thought of it that way. You're very right about it |
Beta Was this translation helpful? Give feedback.
-
pnpm is a fast, disk space efficient alternative to other more common package managers like npm and yarn.
There are some reasons why one would like to switch @ pnpm.io/motivation and pnpm.io/feature-comparison, but TL:DR, it stores packages for all pnpm projects in the same place and symlinks those dependencies to the project's node_modules folder, which saves a lot of space since you won't be constantly redownloading the same dependencies for each project, and also makes initial installs a lot faster since you for the same reason.
The migration is pretty easy to do, replace the existing package-lock.json file with pnpm's pnpm-lock.yaml, and that's it.
I could do a PR for it, also rewriting the README and wiki pages to reflect the changes, though I'm not too sure on whether Encho would like it
Beta Was this translation helpful? Give feedback.
All reactions