Refactoring a large JS codebase is like painting the proverbial Forth Bridge. By the time you've finished, fashions have changed and it's time to rewrite it all again.
It is exactly what I did with bluebird before async was even part of the language back in 2013, and when async finally arrived all we did was a simple regex replace. So yeah, I am pretty consistent at what I do and everyone who disagrees is just cringe.
Async/await isn't exactly a fad that is going away anytime soon. If refusing to refactor outdated pieces of code is your idea of "fun" then I feel sorry for your coworkers.
What does 'outdated' actually mean here? It's a sign of lazy or fashion-driven thinking. If there's a good reason for refactoring a pice of code, it should be possible to articulate that reason without reference to the date it was written.