Fucking cache in browser made me think that code is still working untill I opened it in incognito.

I always leave the dev tools open in chrome with "disable cache" checked in "Network" tab 😉

But today it happened to me too... fixed stuff in code, but it was not working at all. after 10mins I realize the gulp watcher task was not running and thus not transpiling Typescript... 😅

What I usually do, (in Chrome) I open Inspect Element, right click in refresh icon, and click "Empty Cache and Hard reload". Remember, Inspect Element must be open.

window.location.reload(true) to the rescue

@qbasic16 what are the advantages of typescript, coffeescript and the like? Nicer syntax??

It's usually the other way around for me. Starting to question my sanity and if 1+1 still equals 2, and then figure out my fix an hour ago worked just fine, but the browser had the buggy version cached...

I use Typescript a lot because it gives you together with Intellisense (e.g. in VS Code) great speed and readability while developing.
Interfaces are one thing I use heavily, because this way you have well defined datastructures and when creating a variable you always know what has to go in there (object with inteface as type).