-
Notifications
You must be signed in to change notification settings - Fork 193
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
Including yarn #82
Comments
Yep – still on the cards. A decent workaround is just downloading it as the first step in your build. |
yeah I was thinking that, but my builds are already approaching 5m as it is, for now I'm just using the npm equivalent commands so everything is working dandy 👍 |
Oh, the downloading would add only literally a couple of seconds to your build – network speed is fast from Lambda – so I wouldn't worry about that aspect. |
Going to close this – I think just installing this in your build is the best bet – yarn actually has some issues with disk usage that's made me avoid it on Lambda anyway. |
I've had trouble downloading yarn as my first build step using these commands;
Is there a working example that could help guide me? |
Use that in a # manual install yarn
curl -o- -L https://yarnpkg.com/install.sh | bash
# enable yarn in cli
export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
yarn install |
I saw that you mentioned you were thinking of including in yarn in #71
Just wondering if there has been anymore thought into this?
It would be useful for my particular use case at the moment
The text was updated successfully, but these errors were encountered: