5

I innocently fired up my angular project, updated everything and got the infamous window not defined error. Huh? Everything is set to Client side rendering? Delete this, delete that, reformat, nothing calling browser apis, so what the fuck?

Apparently, an update in path-to-regexp broke path parameters in the server script, requiring you now instead of declaring the route “/**” to /*something, because for some reason it wasnt supported anymore. Id lie if i felt rage towards the people, but well they do this stuff for free. But Angular, wtf?

Comments
  • 5
    Stuff like this is why the tech and package managers for frontend are all memes. The node folder, the randomly broken deps, the new version every week, the new tech-stack every month...
  • 1
    Frontend still less spicy then backend. We get the org on our backs. 🙂‍↔️
    Wanna trade?
  • 3
    @rootshell haha you wish. Fuck frontend man, why cant i just shove these apes the messagepacks right in their skulls.

    Srsly though, touching typescript / anything close to UI feels so frustrating. I worked with angular almost a year, and the same activity rarely had the same output.
  • 0
    @Hazarth I never have this kind of issue. React is sane. Node_module is a bit shit, granted, but minimize dependancy and you'll never have an issue.
  • 0
    @Chewbanacas it's just angular.

    It gave me suicidal thought.
  • 0
    I hate Angular
Add Comment