Skip to content

The PowerShell script doesn’t include the required $env:NODE_PATH change #6

Closed
@ExE-Boss

Description

@ExE-Boss

Turns out that the PowerShell script I added in #5 doesn’t include the $env:NODE_PATH change from 68dc8ce, as I just ported the commit from npm#27, without paying much thought to all the changes that needed to be done, and it slipped by testing, as it worked in all scenarios I threw at (except for the case when depending on dependencies which are using pluggable packages with plugins, which I discovered only after pnpm 2.11 was released), then they may break in odd ways.

The issue with this is that the PowerShell script may be run on either Windows or Linux (where Windows uses ; as PATH separators, but Unix uses :, so that will need to be handled from inside the PowerShell script)

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