yarn/npm/node not in Path

Joram van den Boezem's Avatar

Joram van den Boezem

05 Feb, 2020 10:13 AM

Hi there,

Previously, yarn, npm and node where available from the Path environment variables. The Path environment variable currently contain these paths:

C:\Users\appveyor\AppData\Roaming\npm
C:\Users\appveyor\AppData\Local\Yarn\bin
C:\Program Files\nodejs

These paths seem to not exist (anymore?), and the programs reside in these folders:

C:\Program Files (x86)\Yarn\bin
C:\Program Files (x86)\nodejs

I don't know if this was recently changed, but we started observing errors in our pipeline expecting node and yarn to be available from the Path recently (since a couple of days ago).

We're observing this behaviour in both the Visual Studio 2017 and 2019 images.

Is this a known error, and if so, will the previous behaviour be restored, or should we build a work-around?

Best,
Joram

  1. Support Staff 1 Posted by Feodor Fitsner on 05 Feb, 2020 07:57 PM

    Feodor Fitsner's Avatar

    Hi Joram,

    I'm looking at Visual Studio 2019 image currently: https://ci.appveyor.com/project/FeodorFitsner/nuget-test/builds/305...

    and I see the following paths in PATH:

    C:\Program Files (x86)\nodejs\
    C:\Program Files\nodejs
    C:\Users\appveyor\AppData\Roaming\npm
    C:\Program Files (x86)\Yarn\bin\
    

    The last one for Yarn is used to be in Program Files (x86) as we install Yarn from MSI.

    Are you sure you are not changing the PATH during the build?

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac