Allow installing Node.js version based on .nvmrc

[plaa]

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Feature

Enter Task Name: Node.js Tool Installer

Environment

• Server - Azure Pipelines
• Agent - Hosted

Issue Description

Please add an option to install the Node.js version defined in .nvmrc. This would be useful for fixing a particular version across development and build pipelines. Currently when the Node version is upgraded, you need to go through all pipelines and update their configuration (and impossible if different branches require different versions). For example App Center has the option of selecting a specific Node version or using .nvmrc.

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[plaa]

I think this is still very relevant and I wouldn't believe it to be too hard to do either.

[betopompolo]

up

[fowl2]

I had a go at this in PR #15615

[fowl2]

Note that the GitHub actions version of this task already supports using a node version file.

[anatolybolshakov]

@plaa @fowl2 thanks for reporting and contribution! We are currently working on more prioritized items at the moment, but will get back to this one once be able to.

[JaydenMaalouf]

Is there any timeline on this deployment?
It would be awesome to have!

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[plaa]

Would still be useful.

[JaydenMaalouf]

Would still be useful.

This has already been deployed and is working as expected on my end!

[dinbtechit]

@JaydenMaalouf How did you get it working? For some reason, it does not pick up the version from .nvmrc during appcenter-post-clone.sh step.

.nvmrc

v16.15.1

From App Center logs:
The node version shows as 18.x

Even manually selecting the node version from the dropdown does not work.

[JaydenMaalouf]

@JaydenMaalouf How did you get it working? For some reason, it does not pick up the version from .nvmrc during appcenter-post-clone.sh step.

.nvmrc

v16.15.1

From App Center logs:

The node version shows as 18.x

Even manually selecting the node version from the dropdown does not work.

Are you invoking the NodeTools@0 step before attempting to run the script?

Simply calling this before anything else (but after checkout):

- task: NodeTool@0
  inputs:
    versionSource: 'fromFile'
    versionFilePath: '.nvmrc'

Should result in your node install matching the version defined in your .nvmrc

[dinbtechit]

Are you invoking the NodeTools@0 step before attempting to run the script?

Simply calling before anything else (but after checkout):

• task: NodeTool@0
  inputs:
  versionSource: 'fromFile'
  versionFilePath: '.nvmrc'
  Should result in your node install matching the version defined in your .nvmrc

How do you invoke NodeTools@0 before running the post clone script... I dont think I came across any documentation that mentions that. Are you able to point me to the App Center documentation that refers about this NodeTools@0? Thanks! 🙏

[JaydenMaalouf]

Are you invoking the NodeTools@0 step before attempting to run the script?

Simply calling before anything else (but after checkout):

• task: NodeTool@0

inputs:

versionSource: 'fromFile'

versionFilePath: '.nvmrc'

Should result in your node install matching the version defined in your .nvmrc

How do you invoke NodeTools@0 before running the post clone script... I dont think I came across any documentation that mentions that. Are you able to point me to the App Center documentation that refers about this NodeTools@0? Thanks! 🙏

Either via your yaml file using the yaml I provided above or if you are using Releases, via the Node task in Azure DevOps with the appropriate parameters

[LuwkasLima]

Hi folks, I would like some guidance on this. I'm trying to make it standard for my team to adopt .nvmrc to ensure consistency between all our applications and also in our CICD pipelines using ADO.

We have implemented Node version enforcement for Web App Service deployments successfully using .nvmrc but I'm not able to do the same with AzureStaticWebApp@0. I do not want them to maintain .nvmrc and package.json configuration.

I've tried the workaround proposed above, adding NodeTool@0 prior to AzureStaticWebApp@0, but it ignores the installation of node v18 and uses v16 to build the Next static application.

AzureStaticWebApp@0 deployment log:

[JaydenMaalouf]

Hi folks, I would like some guidance on this. I'm trying to make it standard for my team to adopt .nvmrc to ensure consistency between all our applications and also in our CICD pipelines using ADO.

We have implemented Node version enforcement for Web App Service deployments successfully using .nvmrc but I'm not able to do the same with AzureStaticWebApp@0. I do not want them to maintain .nvmrc and package.json configuration.

I've tried the workaround proposed above, adding NodeTool@0 prior to AzureStaticWebApp@0, but it ignores the installation of node v18 and uses v16 to build the Next static application.

AzureStaticWebApp@0 deployment log:

That sounds like your engine version is being specified in your package.json

Make sure to update that to match your nvmrc specification

"engines": {
    "node": ">=18.0.0"
}

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days