Actually, Glitch provides a way to choose it but within a limited versions list.
Is there a real reason behind that limitation?
When we really need a newer version, we need to wait the version “approval” by the Glitch team… or getting around by a NPM script which works but costing in memory/time.
Hum, I don’t share the Choose Node Version idea, because it also pushes to a limited versions list.
My proposal is to simply replace the install behavior (which is already installing node based on the engine property, but with a true version choice), based by example on nave.
Docker containers are able to mount read-only volumes in a manner such that they may be shared across multiple container instances. An ideal solution to software versioning on Glitch would be to strip Node.js, Git, etc., out from the container image, which must be huge considering how many utilities are installed in general, and move them to those kind of volumes along with additional versions of those utilities.
With regards to implementation, users could select whatever software versions they wish to use via some user-facing interface while a utility such as Environment Modules handles environment modification behind the scenes.