18

Fucking React Scripts, "yOu hAvE mUlTiPlE VErSiOnS oF bAbEL-JeSt, Use nPm Ls Jest To TrACk It Down"

Ok you dumb fucks:

npm ls babel-jest
react-typescript@1.0.0 /Users/chris/Downloads/8sleu4
└─┬ react-scripts@4.0.3
├── babel-jest@26.6.3
└─┬ jest-circus@26.6.0
└─┬ jest-runner@26.6.3
└─┬ jest-config@26.6.3
└── babel-jest@26.6.3

OH LOOK THEY ARE BOTH IDENTICALLY 26.6.3 STOP BUILDING AN OPINIONATED PILE OF GARBAGE IN YOUR COCONUT TREE FUCKED UP FALSE PARADISE YOU CALL SILICON VALLEY!!!!!!! I'VE NEVER SEEN SUCH A BUNCH OF GARBAGE!!!! I'D PREFER A TOOL WRITTEN BY KINDERGARTNERS IN CRAYON!!!!! AAAAAAAAAAAAAAAA

EVERY

SINGLE

TIME

REACT SCRIPTS

BREAKS

Comments
  • 1
    Does pnpm work? Npm can't resolve packages properly
  • 1
    CRA is an awful framework. The library itself is good because it's meant to be unopinionated and flexible, and every feature that isn't built in this fashion such as Suspense and streaming ends up shit. Why would my fetch wrapper talk to Suspense? Why would my fetch wrapper even know React exists? And why does Lazy expect a default field in the return value when there are no real technical advantages to implying that I'll be loading an ES module? Just let me pass an async component function or an async data function and stop assuming where those things come from.
Add Comment