You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
ExE-Boss
changed the title
The PowerShell script doesn’t include the required NODE_PATH change
The PowerShell script doesn’t include the required $env:NODE_PATH change
Jul 14, 2018
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)The text was updated successfully, but these errors were encountered: