|
| ▲ | nawgz 5 days ago | parent | next [-] |
| ‘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 |
|
| ▲ | c-hendricks 5 days ago | parent | prev | next [-] |
| If 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. |
| |
|
| ▲ | mirekrusin 5 days ago | parent | prev | next [-] |
| Downside 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 5 days ago | parent | prev | next [-] |
| A 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. |
|
| ▲ | TheRoque 5 days ago | parent | prev [-] |
| Personally, I didn't find a way to create one docker image for each of my project (in a pnpm monorepo) in an efficient way |
| |
