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

One thing JS does great is that everything from the server to the gui to the (extremely flexible) build system is 100% platform independent with very few platform specific bugs. And that's a big deal when a basic setup is 1200 packages from 650+ semi-coordinated people.

Developing front-ends used to be about translating a business use case to an interface. Now I spend days and weeks getting tooling to integrate properly: webpack, babel, React, Vue, SSR, Nuxt, NPM packages, build & CI pipelines, storybooks, and resolving incompatibilities. It's become such a grind I haven't had a single satisfying, productive workday since 4 months.

Looking at vacancies and the JS build tools asked (Babel, Gulp) and then visiting their websites I notice that I don't understand what they are going on about.

"Leverage gulp and the flexibility of JavaScript to automate slow, repetitive workflows and compose them into efficient build pipelines."

What the actual corpo fuck?

The "get started" page expects you already know npm, typescript, and when you look at their pages, well... Where does the circlejerk end and the actual Javascript start?

I've been out of the corporate loop for a few years, seems it's all about build tools these days. I need to get out of this industry pronto.

I’m so sorry if this is the place for questions. I’m terrified of stack overflow and have been searching for a week for a solution and can’t find one. This is for React.js people.

I was tasked to create a webpage with react. The limitation is, they did not wanna adopt the node.js dependency. I said ok, I’ll figure it out. You can inject react, material UI, and babel with script tags in HTML, then put ur lil components in it. I did that and it works beautifully.

However, now I have to write tests for this. I think it’s actually impossible without a way to render React, so I have to use the browser, or node, right? I convinced my boss to allow me to use a node.js container just for testing, which I thought would make my life easier.

I don’t know how to render this thing with node. It’s just an HTML file that pulls react via script tags, and idk how to serve html with node. Additionally, none of the React testing libraries seem to support testing a system that wasn’t designed to be served with node, at least not easily. My gut tells me that the complication with how things are imported contributes at least a little to this (dependencies pulled via script tags in the HTML file and made available to react through global const variables).

I could be wrong about any of this — im fairly new. But how tf do I go about testing these react components? For reference, if you go to Reacts docs, there’s a section called “add react to a page in one minute” that’s pretty much what I did.

Babel fails about 10% of the time, but if I re-run it it works. What the fuck did I even get myself into, and why aren't elements of a modern javascript toolchain completely deterministic? (webpack, babel, typescript, react)

Why building a library of React component should be this hard: I'm sick of Webpack, Babel, Typescript and all the shit which is duct taped together to build some damn widgets.

Behold! This is the first time in my career when Jest and unit testing in general actually helped me 😂

Spent two days moving from a fucking slow piece of crap called Gatsby to Vite, trying to comprehend the difference between TS aliases, Babel aliases and Linaria aliases. Found an answer inside a totally unrelated issue explaining Jest stuff, good job on documentation, Linaria!

Vite is fast. Crazy fast. Forget about Webpack, Parcel and things alike — Vite doesn't even need to bundle JS.

Gatsby was slow to the point of my computer's audio glitching, I'm not even talking about the OS interface lags.

Vite is fast to the point that I don't actually need a new MacBook.