-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm: command not found after node.js was installed #186
Comments
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? |
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? |
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:/Bluejanis> @mlorenzog
<https:/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:/jonnyzzz> is this plugin still actively
worked on?
—
Reply to this email directly, view it on GitHub
<#186 (comment)>,
or unsubscribe
<https:/notifications/unsubscribe-auth/AAB6TL2AFZOR66WJTNUJRP3VBOLY7ANCNFSM5BFBKLHQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The native alternative, Node.js metarunner, didn't work on my case because or agents are already dockers.
It's not an ideal solution, but it gets the work done |
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
|
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) |
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:
More context:
The text was updated successfully, but these errors were encountered: