Learn More
Resend Email
1
Lasoloz
1y

Today was the first time I've tried out `pnpm` (after using both `npm` and `yarn` in the past).

It's safe to say that it will also be the last time at least for this year.

The damned thing randomly crashed my builds on `vercel` (which I also set up today for the first time, and which uses `pnpm` by default).

Then, it continued to mess with me by randomly breaking the TSX transpilation locally.

So, it might be the fastest and nicest package manager for the JS world, but it surely shouldn't cause me trouble twice on the same day and get me 2+ hours of debugging.

rant
Favorite
Ranter
Comments
  • 2
    1y
    Ah, I remember the days of alternatives to npm. It’s kind of funny when I still see people using yarn lol
  • 2
    1y
    @chonky-quiche it's still kinda random for me: sometimes I use npm, sometimes I use yarn. I'm way too lazy to check which one is better (and at this point I don't even care). I wouldn't even have yarn on my device, if it wasn't for a previous workplace project.
  • 2
    1y
    @Lasoloz yeah true ur right it doesn’t matter too much. Unless there is a yarn.lock and package-lock.json and they don’t match deps 🥲
  • 3
    1y
    I think we can all agree that the solution here is to make a new package manager for nodejs :)
  • 0
    1y
    @ars1 new as in really new or just another iteration of yarn, pnpm, npm, ...?

    If you mean new as in new concept (no node_modules) I would welcome that idea.
  • 0
    1y
    @IntrusionCM I was just poking fun at Node and JS in general.
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment