4

A react package has a transient dependency on another library (date-fns), well that transient library is used throughout the code base. Now I need a slightly newer version of date-fns. Everything runs fine, create PR, build fails. Have a look, react package doesn't import date-fns properly, ok well lets update it, spent the morning updating a shitty date picker component, that is wrapped in a shitty wrapper that doesn't keep the generic/union exclude info so now it has type issues. Finally fix that, everything looks fine.

Runs build:
 ELIFECYCLE  Command failed with exit code 3221225501.

Why is it always with react that these issues exist

Comments
  • 2
    It's because shortly before react was open sourced, Zuckerberg licked it all over whilst crooning a weird little song about cows and macadamia nuts, and made it promise to awaken and do his bidding if it ever heard the song again.
  • 1
    I noticed every job post for JavaScript is react and I actually don't like react

    react was a mistake. when react happened I hoped it would go away. I was wrong in thinking that would happen. stupid political clout -.-

    though if people equate their react hate with JavaScript it would make sense. but they're not saying that
  • 1
    @jestdotty this have nothing to do with react and everything to do with node and npm.

    Use deno
  • 0
    @antigermgerm Or Bun I guess, but the snek bots I have run using deno, and it has been pretty nice to work with.

    I hope react 19 will have less of these issues, we'd upgrade, but PM is a coward
Add Comment