3 ms·
OK so it seems too good now, what are the downsides?
by dvfjsdhgfv 1y ago
OK so it seems too good now, what are the downsides?
- c-hendricks 1y agoIf you relied on hoisting of transitive dependencies, you'll now have to declare that fact in a project's .npmrc Small price to pay for all the advantages already listed.
- no_wizard 1y agoThey’re moving all that to the pnpm-workspace.yaml file now
- nawgz 1y ago‘pnpm’ is great, swapped to it a year ago after yarn 1->4 looked like a new project every version and npm had an insane dependency resolution issue for platform specific packages pnpm had good docs and was easy to put in place. Recommend
- TheRoque 1y agoPersonally, I didn't find a way to create one docker image for each of my project (in a pnpm monorepo) in an efficient way
- no_wizard 1y agoThat’s not really a pnpm problem on the face of it
- mirekrusin 1y agoDownside is that you have to add "p" in front, ie. instead of "npm" you have to type "pnpm". That's all that I'm aware of.
- Nathanba 1y agoA few years ago it didn't work in all cases when npm did. It made me stop using it because I didn't want to constantly check with two tools. The speed boost is nice but I don't need to npm install that often.