Node 18 Ate My Website

[swatcoder]

There's a teaching moment in here about the downside of engineeeing a project like a quilt made of other people's code.

The more disparate dependencies you adopt, the more of this kind of headache and chaos you invite into your future. You may gain some development speed, or get to put off having to think through and implement something in a domain that intimidates you, but you do set yourself up for major synchronization and migration problems that look a lot like this.

I've mostly given up trying to convince people to use fewer dependencies, to know them each better, and to shim them aggressively so that they can be trivially replaced -- but I hope people are at least starting to recognize the tradeoffs they accept when they don't.

[qiller]

The pace of javascript ecosystem is annoying at times. The first issue is due to deprecation of md4 hash and can at least can be worked around which may allow to avoid upgrading _some_ dependencies - https://stackoverflow.com/a/72219174

[lukefernandez]

Thanks for sharing this! That's a clever workaround that I hadn't come across.

[johnz]

I had a very similar experience a few years ago and decided to switch from Next to Astro [0].

[0] https://astro.build/