Is it possible to choose a node version with AddNpmApp() ?

[jepzen]

Is it possible to lock the nodejs version when using AddNpmApp() ?

[davidfowl]

AddNpmApp doesn’t pick the node version, you do it in your package.json

https://docs.npmjs.com/cli/v11/configuring-npm/package-json#engines

[davidfowl]

Are you looking for something like a version manager or are you looking to fail if the wrong version of node is used?

[jepzen]

I am using NVM. It is an old Angular.

If mnaully

nvm use 14
npm i
ng serve

the app runns. But if i start it up through Aspire it fails

Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:79:19)
at Object.createHash (node:crypto:139:10)
at module.exports (/Users/me/source/MasApi/Mas.Angular/node_modules/webpack/lib/util/createHash.js:135:53)
at NormalModule._initBuildHash (/Users/me/source/MasApi/Mas.Angular/node_modules/webpack/lib/NormalModule.js:417:16)
at /Users/me/source/MasApi/Mas.Angular/node_modules/webpack/lib/NormalModule.js:452:10
at /Users/me/source/MasApi/Mas.Angular/node_modules/webpack/lib/NormalModule.js:323:13
at /Users/me/source/MasApi/Mas.Angular/node_modules/loader-runner/lib/LoaderRunner.js:367:11
at /Users/me/source/MasApi/Mas.Angular/node_modules/loader-runner/lib/LoaderRunner.js:203:19
at VirtualFileSystemDecorator.readFile (/Users/me/source/MasApi/Mas.Angular/node_modules/@ngtools/webpack/src/virtual_file_system_decorator.js:47:13)
at processResource (/Users/me/source/MasApi/Mas.Angular/node_modules/loader-runner/lib/LoaderRunner.js:202:11)
at iteratePitchingLoaders (/Users/me/source/MasApi/Mas.Angular/node_modules/loader-runner/lib/LoaderRunner.js:158:10)
at runLoaders (/Users/me/source/MasApi/Mas.Angular/node_modules/loader-runner/lib/LoaderRunner.js:365:2)
at NormalModule.doBuild (/Users/me/source/MasApi/Mas.Angular/node_modules/webpack/lib/NormalModule.js:295:3)
at NormalModule.build (/Users/me/source/MasApi/Mas.Angular/node_modules/webpack/lib/NormalModule.js:446:15)
at Compilation.buildModule (/Users/me/source/MasApi/Mas.Angular/node_modules/webpack/lib/Compilation.js:739:10)
at /Users/me/source/MasApi/Mas.Angular/node_modules/webpack/lib/Compilation.js:981:14 {
opensslErrorStack: [
'error:03000086:digital envelope routines::initialization error',
'error:0308010C:digital envelope routines::unsupported'
],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v22.4.

which is also what i get when i uses v 22.

I added the engines part to the package.json but it still tries with version 22

[davidfowl]

Aspire uses whatever is on the path.

[jepzen]

But it does not load my .zsh profile so I cant tell it to use nvm to change version before running. Eventully i got it working by adding this script

#!/bin/bash
NPM14="/Users/me/.volta/tools/image/node/14.21.3/bin/npm"

export PATH="/Users/me/.volta/tools/image/node/14.21.3/bin:$PATH"

echo "Using Node: $($NODE14 -v)"
$NPM14 run ng serve

and the add this to package.json under

"scripts": {
"ng": "ng",
"start": "./aspire-ng-start.sh",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e"
},

Would be cool if i could just have a
..
"start": "nvm use 14 && ng serve"
..
instead, not relying on a path with my user name

[davidfowl]

Why can't you change your npm app to do that?

[ccremer]

In my case I'm using this snippet for anyone looking for a nvm-managed node installation

nvm alias default $(cat .nvmrc)
sudo ln -sf "$(which node)" /usr/local/bin/node
sudo ln -sf "$(which npm)" /usr/local/bin/npm
sudo ln -sf "$(which npx)" /usr/local/bin/npx