Skip to content

Issue With PATH Ordering #36

Open
Open
@andrewburgess

Description

@andrewburgess

I'm not sure if I've misconfigured something, but the PATH environment variable seems to be putting /usr/bin in the middle, before the N_PREFIX directory, which means the system level version of node is used instead of the one just downloaded via n

Output of $PATH after n activates the version requested

/home/strider/builds/data/${project-branch}/node_modules/.bin
/home/strider/builds/data/node_modules/.bin
/home/strider/builds/node_modules/.bin
/home/strider/node_modules/.bin
/home/node_modules/.bin
/node_modules/.bin
/usr/bin
/home/strider/app/node_modules/strider-node/node_modules/n/bin
/home/strider/builds/data/${project-branch}/.n/bin
/home/strider/app/node_modules/strider-node/node_modules/.bin
/home/strider/builds/data/${project-branch}/${job-id}.globals/node_modules/.bin




/usr/local/sbin
/usr/local/bin
/usr/sbin
/usr/bin
/sbin
/bin

I'm not sure where that /usr/bin comes from in the middle, but I'm wondering if maybe https://github.com/Strider-CD/strider-node/blob/master/worker.js#L82 needs to be flipped so that the new paths are prepended to ret.path instead of appended.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions