-
Notifications
You must be signed in to change notification settings - Fork 89
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
Angular 9 #85
Angular 9 #85
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure what those sha correspond to anymore. But I still see commits related to yarn on Travis that I think are not necessary. What was the commit d50bdcd ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a matter of fact yarn should not be used at all.
@HaithemMosbahi himself introduced package-lock.json
first in 2017 in 6468127 and used it the last time not long ago in 2019 in 4f485d8.
On the other hand yarn.lock
was introduce in 2018 in #33 and was not properly maintained, the last update being in 2018 in #44.
This shows that npm is the preferred package manager for this project and the yarn.lock
file must be deleted. In addition this preference should be specified for Angular CLI by adding the following in angular.json
:
{
"$schema": "./node_modules/@angular/cli/lib/config/schema.json",
+ "cli": {
+ "packageManager": "npm"
+ },
This should go into a different pull-request. I shall file one. |
#87 removes yarn. |
#87 is merged, you can follow with this now. |
I took the liberty to rebase this PR in #91. Hopefully this will help to get it merged. |
Let's follow there then, thanks. |
Thanks for following up on this @PowerKiKi ! |
Thank you too for the initial PR @maguro . |
No description provided.