the tool/node/clean.sh script doesn't work for me on linux desktop as it appears to be looking for a .nvmrc file that was never created by run.sh.
Is this custom build infrastructure still necessary in 2026? Now that package.json has gained the engines and engines.packageManager sections, there's a built-in mechanism to enforce matching versions, and it seems like relying on nvm in general has become much more socialized. I'm not as familiar with how the go ecosystem has changed over that span, however.
the tool/node/clean.sh script doesn't work for me on linux desktop as it appears to be looking for a .nvmrc file that was never created by run.sh.
Is this custom build infrastructure still necessary in 2026? Now that package.json has gained the
enginesandengines.packageManagersections, there's a built-in mechanism to enforce matching versions, and it seems like relying onnvmin general has become much more socialized. I'm not as familiar with how the go ecosystem has changed over that span, however.