@firstname.lastname@example.org foreach sounds like a package that you shouldnt need with Array.prototype.forEach
@Johann150 yes, that's true. It made it into ECMAScript 5.1
Now if you've for _some_ weird reason a system that requries some _older_ build target you get a polyfill.
That was provided by packages like this and should be helluvEOL nowadays. There are better suited and highly automated polyfills.
Anyway, the issue is very real. This happened before and will happen again.
It's also the very same for most language depending package managers out there and this is why version pinning is a thing.
@valhalla @clacke @federico3 @bekopharm @Sandra @lrvick @technicallypossible @ruffni @Johann150 @RyunoKi also, since with the first layer you have to re-audit with every update, you may as well vendor that dependency (as in, put a copy of a specific version in your repo), so arguably github could be enough as the first layer
There's a series of articles starting from:
Most of the time you just need an ephemeral run akin to running chroot.
Welcome to the 8th Layer of Madness
Most topics are related to Linux, Anime, Music, Software and maaaany more