npmAuthenticate task needs migration from Node 6 to Node 10

[tobiasmarciszko]

Type: Bug

Enter Task Name: npmAuthenticate

Environment

• Server - Azure Pipelines

Issue Description

npmAuthenticate needs migration from node 6 to node 10

Task logs

Starting: npmAuthenticate
==============================================================================
Task         : npm authenticate (for task runners)
Description  : Don't use this task if you're also using the npm task. Provides npm credentials to an .npmrc file in your repository for the scope of the build. This enables npm task runners like gulp and Grunt to authenticate with private registries.
Version      : 0.179.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/package/npm-authenticate
==============================================================================
##[warning]This task uses Node 6 execution handler, which will be deprecated soon. If you are the developer of the task - please consider the migration guideline to Node 10 handler - https://aka.ms/migrateTaskNode10. If you are the user - feel free to reach out to the owners of this task to proceed on migration.
Adding authentication to the .npmrc file at /home/vsts/work/1/s/frontend/.npmrc
SYSTEMVSSCONNECTION exists true
SYSTEMVSSCONNECTION exists true
SYSTEMVSSCONNECTION exists true
Adding credentials for a local registry
Finishing: npmAuthenticate

[anatolybolshakov]

Hi @tobiasmarciszko thanks for reporting!
We are going to disable Node 6 deprecation warnings in ticket and make sure that all in-the-box tasks will be migrated in time - so there is no need to worry about in-the-box tasks.

[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