-
Notifications
You must be signed in to change notification settings - Fork 224
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
Installs an ancient version of yarn by default #98
Comments
On the basis that Node.js ships with |
I think removing it completely is a good idea, but we have to worry about backward compatibility. Perhaps, we can start printing a warning and then remove it 6 months later. What do you think? |
I may be misunderstanding but I strongly disagree that there is "zero benefit to using Yarn on Heroku" -- some projects use yarn to lock, others use npm to lock, and Heroku supports both. @jesseshieh Is your proposal simply to remove the default version of yarn so that it must be specified in the buildpack settings? |
Sorry yes, my proposal is just to remove the default version. |
The default config specifies an ancient version of
yarn
to install by default:This should instead be unset to allow for the latest version of
yarn
to be installed.The text was updated successfully, but these errors were encountered: