> "Sure, I should setup a complex and huge dependency for just one of the many problems I highlighted. What a great idea" This too, demonstrates the point I ra

> "Sure, I should setup a complex and huge dependency for just one of the many problems I highlighted. What a great idea" This too, demonstrates the point I raised earlier. Instead of using a mature, widely adopted and battle-tested system which allows you to efficiently share code across multiple languages without introducing runtime hits - you instead discard it as some "huge dependency" and insist on having JS everywhere, using the latest hype of the week, consequences be damned. Why actually spend the time to solve a problem in a mature way, when I can just add this week's shiniest NPM package to imports.json?