Azure-devops-docs: Error: Please change your working directory to a valid directory

[ranouf]

Hi,

I added NPM INSTALL to PHASE 1. The Build failed with this error:

2018-05-01T18:19:25.7802426Z ##[section]Starting: npm install
2018-05-01T18:19:25.8020360Z ==============================================================================
2018-05-01T18:19:25.8020587Z Task : npm
2018-05-01T18:19:25.8020724Z Description : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Package Management.
2018-05-01T18:19:25.8020882Z Version : 1.0.15
2018-05-01T18:19:25.8020981Z Author : Microsoft Corporation
2018-05-01T18:19:25.8021099Z Help : More Information
2018-05-01T18:19:25.8021222Z ==============================================================================
2018-05-01T18:19:26.6681290Z [command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" --version"
2018-05-01T18:19:30.7267018Z 3.10.8
2018-05-01T18:19:30.8037891Z ##[error]Error: Please change your working directory to a valid directory
2018-05-01T18:19:30.8072404Z ##[section]Finishing: npm install

Do you know how to fix this issue?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: cb7c2ab6-4ba1-51d5-96bb-38a9ab6b50c3
• Version Independent ID: 415de875-ba1b-476b-f08b-1a61dc7a2747
• Content: Set up your client's npmrc
• Content Source: docs/package/npm/npmrc.md
• Service: unspecified
• GitHub Login: @elbatk
• Microsoft Alias: elbatk

[elbatk]

Adding the package area owner to help out with this! @alexmullans. If you think we need to update the docs let me know, Alex.

[ranouf]

Hi,

To solve the problem, I:

• added "Node Tool Installer" with version "6.9.1"
• added "Npm" with the following custom command "install -g npm@latest"

And then it worked.

[vip3rousmango]

I am also experiencing this issue.

I tried to add Node Tool Installer and it updated the PATH to the directory of where it tries to run the NPM install request but the Npm install still throws the same error...

[narasimaperumal]

Tried today facing the same issue. Also tried the workaround by ranouf, but no luck.

[ranouf]

This the configuration of my Build, I hope it will help you:

[elbatk]

Reopening and retagging @alexmullans for awareness.

[infin8x]

For others encountering this issue, what is the value of the "Working folder with package.json" input in the npm task?

[bhaveshmaniya]

The @ranouf solution works. Thank you!

[elbatk]

Closing this for now as we haven't heard much in a while and it looks like we have a solution for the few that we have heard from.

[marcelostsh]

thank you @ranouf !!!