🛠️ 📚💡 This is a detailed and carefully made template for your GitHub projects. It's based on the wide knowledge and practical experience of the engineering community within NHS England. The template includes helpful suggestions, standards and practices - it's something you should consider using for all your repositories.
MIT License
30
stars
12
forks
source link
`asdf` can only install Yarn Classic, not the latest LTS. Change how `yarn` is managed to be up to date. #126
Yarn changed how it was distributed after v1, and the 1.X line went into maintenance mode in 2020. It is now managed per-project, and the asdf-yarn installer doesn't handle it at all.
Yarn should be configured on project setup, once the user has opted into a NodeJS project type.
What is the feature that you are proposing to solve the problem?
No idea.
What alternatives have you considered?
If we want yarn, we need not to be installing a version that's going to go EOL. The alternatives are:
No yarn
An up to date yarn
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Sensitive Information Declaration
[X] I confirm that neither PII/PID nor sensitive data are included in this form
regularfry
commented
1 year ago
What is the problem this feature will solve?
Yarn changed how it was distributed after v1, and the 1.X line went into maintenance mode in 2020. It is now managed per-project, and the
asdf-yarninstaller doesn't handle it at all.Yarn should be configured on project setup, once the user has opted into a NodeJS project type.
What is the feature that you are proposing to solve the problem?
No idea.
What alternatives have you considered?
If we want
yarn, we need not to be installing a version that's going to go EOL. The alternatives are:yarnyarnCode of Conduct
Sensitive Information Declaration