> Ok, the client is performing this HTTP request, it's missing some parameters, let's fix it... inspector has this handy initiator tab, lemme just BY THE RINGS WHAT THE FUCK IS THIS

I still refuse to believe anyone looked at this burning pile of shit you insist on calling a framework and was like "yeah this deserves to be released"

It's just compiled shit. You can't do window.myFw = this somewhere? I did such stuff working with Vuetify iirc.

@retoor Someone programmatically creates a component with some configuration -some weird custom form builder we have, and someone will have to pay for this someday but I'm not quite there yet- , somewhere in the life cycle of this component it fires this HTTP request. Need to decode where that happens, the call stack of Angular is nested 400 times.

And no, it's not a problem with compilation; if I did that with any sane framework, I wouldn't have to deal with this shit.

@IHateForALiving "BY THE RINGS"?

@Lensflare I said what I said

@IHateForALiving I want to know more ^^

Does angular not have source maps? Are they not configured right?

You don't have this problem with other frameworks because source maps are one of very few technologies in JS land that work nearly perfectly, and the two main hazards are that your compiler doesn't generate them or that your bundler strips them out as comments.

*click*

...

...

...

...

...

...30 minutes later

Initiate HTTP request ... stack overflow

@lorentz this was on one of our staging environments, we don't take source maps there but that's not the problem. The problem is a call stack 20m long for one http request; the kind of stuff you'd be entitled to expect when working with a framework designed by human beings instead of actual retards.

@Lensflare I'm a Halo fan, and I got hooked up with the recent wave of ShinRegis memes. "By the rings" is one of the things the Arbiter says after some particularly bad pun by the Master Chief (EG: https://youtube.com/shorts/...)

@IHateForALiving React has the same shit, as does every mainstream framework, because they all have a custom scheduler. Instead of the really long call stack, React gives you fake bullshit plaintext call stacks, because they conceal the scheduler by logging and then swallowing all errors.