Can this be generalized so it doesn't need to maintained as versions get updated?

you mean in a variable? we can't just pick any node version since it needs to be one that emsdk shipped.

I mean use a regex to match on the existing version (not a hardcoded version but one that has a simple version pattern) defined in the JSON file and replace it with the new value, referencing an ENV value that could be defined.

I'm not sure why that'd be necessary given that emsdk 3.1.34 will always ship with node 14.18.2 and as mentioned in #1281 we can't upgrade the emsdk version.

or do you mean the replacement version?

I'm referring to both versions so that neither have to be hardcoded on this line.

emsdk 3.1.34 will always ship with node 14.18.2

So when the emsdk version is updated, that requires knowing what the node version is and having to update this line with that value. My aim here is to reduce the amount of work needed to rev the versions.

So when the emsdk version is updated, that requires knowing what the node version is and having to update this line with that value.

No, what I'm saying is the emsdk version is frozen for net8, we can't update it. And this logic is gone in net9+

Ok, got it. Thanks