-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Allow environment variables to be set in .yarnrc.yml #2464
Comments
This comment has been minimized.
This comment has been minimized.
Related #3938 |
The
|
We've added support for environment files so this should be covered by that. |
@rally25rs How did you workaround installing sharp library through prebuilt binaries with current latest yarn release ? |
Describe the user story
I am upgrading from yarn 1 to 2, and am having a hard time porting one of the lines of my older
.yarnrc
file, which is:This prevents puppeteer from trying to reach out to the internet and download chromium, which it can't do in my CI server because we disable network access. It seems that the config format has gotten more strict with yarn v2, and I'm no longer able to set this variable in the config file.
Describe the solution you'd like
It is currently possible to read an environment variable in the .yarnrc.yml, which is pretty awesome, but it would be great if we could set them too. Maybe something like:
Describe the drawbacks of your solution
The
yarn config -v
validation might get trickier, and honestly I'm not really sure if that syntax would break yaml parsing.Describe alternatives you've considered
I could try to make sure I add
PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
every time I run a yarn install, but that's not ideal. I could also create a wrapper script that sets the environment variable before running the actualyarn-berry.js
file, as recommended in #1146 (comment), but that feels a bit hacky too.The text was updated successfully, but these errors were encountered: