npm: command not found after node.js was installed

Question

npm: command not found after node.js was installed

Bluejanis opened this issue 3 years ago · comments

I am getting an error "npm: command not found" when running npm install, even though node-js was installed in the first build step.
I am using TeamCity Professional 2021.1.1 (build 92714)

The error:

[npm install] /opt/buildagent/temp/agentTmp/wrapper157115028716706048.sh: line 2: npm: command not found
[Step 2/6] Process exited with code 127

More context:

Manuel Lorenzo · Answer 1 · Fri Nov 26 2021 23:25:58 GMT+0800 (China Standard Time)

Same here, builds were working in an older versions of TeamCity but after updating to 2021.2 (build 99542) the same error happened to us.

Di you found any solution?

mattdjones · Answer 2 · Thu Mar 24 2022 06:32:36 GMT+0800 (China Standard Time)

hey @Bluejanis @mlorenzog did either of you ever find a solution?

I'm seeing pretty much the same kind of error, when I install a node version with the plugin it is ignored by subsequent steps.

@jonnyzzz is this plugin still actively worked on?

Eugene Petrenko · Answer 3 · Thu Mar 24 2022 06:36:57 GMT+0800 (China Standard Time)

The plugin is not actively maintained. In fact, quite similar features are now implemented in the fresh builds of TeamCity. That is sad, anyways, I'd be happy to accept a PR

…

On Wed, Mar 23, 2022 at 11:32 PM mattdjones ***@***.***> wrote: hey @Bluejanis <https://github.com/Bluejanis> @mlorenzog <https://github.com/mlorenzog> did either of you ever find a solution? I'm seeing pretty much the same kind of error, when I install a node version with the plugin it is ignored by subsequent steps. @jonnyzzz <https://github.com/jonnyzzz> is this plugin still actively worked on? — Reply to this email directly, view it on GitHub <#186 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB6TL2AFZOR66WJTNUJRP3VBOLY7ANCNFSM5BFBKLHQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Manuel Lorenzo · Answer 4 · Thu Mar 24 2022 16:09:17 GMT+0800 (China Standard Time)

The native alternative, Node.js metarunner, didn't work on my case because or agents are already dockers.
Instead we made it work by installing NVM in our agents and add this at the start of the command line step:

. ~/.nvm/nvm.sh
nvm use $NODE_VERSION || nvm install $NODE_VERSION

It's not an ideal solution, but it gets the work done

Eugene Petrenko · Answer 5 · Thu Mar 24 2022 16:48:22 GMT+0800 (China Standard Time)

That is interesting. As long as you use docker, why can’t you just bundle the necessary npm in the image?-- Best regards, Eugene Petrenko https://jonnyzzz.com

Manuel Lorenzo · Answer 6 · Thu Mar 24 2022 16:56:49 GMT+0800 (China Standard Time)

That's what we did, but instead of bundling a specific NPM version we installed NVM in our agents. That way we can select which version of node we want for each project or build, we just need to source the NVM file (to have access to the nvm command at that build step) and use the version that we need (or fallback if it hasn't be installed yet)