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
Kind of both. Feature, but produces hard times for developers
What is the current behavior?
There is no env variables such as $YARN_GLOBAL_BIN and $YARN_GLOBAL_DIR.
If the current behavior is a bug, please provide the steps to reproduce.
No.
What is the expected behavior?
To have, so it won't have problems like jonschlinkert/global-modules#8, where i'm concluding that the only way is to call the yarn cli to get these paths. The fix would be pretty easy - just set values of yarn global bin and yarn global dir as env variables in the postinstall step.
Please mention your node.js, yarn and operating system version.
No matter of the versions, but:
Node v10, same is for 6, 7, 8 and 9...
Yarn latest (1.60, installed through npm 6)
OS: ArchLinux.
The text was updated successfully, but these errors were encountered:
tunnckoCore
changed the title
Proposal for setting ENV variables in postinstall step
Proposal for adding postinstall step that sets ENV variables
May 11, 2018
Do you want to request a feature or report a bug?
Kind of both. Feature, but produces hard times for developers
What is the current behavior?
There is no env variables such as
$YARN_GLOBAL_BIN
and$YARN_GLOBAL_DIR
.If the current behavior is a bug, please provide the steps to reproduce.
No.
What is the expected behavior?
To have, so it won't have problems like jonschlinkert/global-modules#8, where i'm concluding that the only way is to call the yarn cli to get these paths. The fix would be pretty easy - just set values of
yarn global bin
andyarn global dir
as env variables in the postinstall step.Please mention your node.js, yarn and operating system version.
No matter of the versions, but:
The text was updated successfully, but these errors were encountered: