Skip to content
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

Closed
wants to merge 4 commits into from
Closed

Angular 9 #85

wants to merge 4 commits into from

Conversation

maguro
Copy link
Contributor

@maguro maguro commented Feb 19, 2020

No description provided.

@odahcam odahcam linked an issue Feb 20, 2020 that may be closed by this pull request
Copy link
Contributor

@PowerKiKi PowerKiKi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a few commits that seems unrelated (maybe entirely unnecessary ?). Could you rebase and keep only the strictly necessary commit to Angular 9 upgrade so that the PR is easier to review please ?

From what I can see only b93ff1f and maybe 5b7af4d is really required.

@maguro
Copy link
Contributor Author

maguro commented Mar 4, 2020

From what I can see only b93ff1f and maybe 5b7af4d is really required.

iiuc, d50bdcd is needed as well. I can delete 05669a9, d933a62, and d79e3b8.

@PowerKiKi
Copy link
Contributor

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 ?

Copy link
Contributor

@PowerKiKi PowerKiKi left a 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"
+   },

@maguro
Copy link
Contributor Author

maguro commented Mar 4, 2020

As a matter of fact yarn should not be used at all.

...

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.

@maguro
Copy link
Contributor Author

maguro commented Mar 5, 2020

#87 removes yarn.

@PowerKiKi PowerKiKi mentioned this pull request Mar 18, 2020
@odahcam
Copy link
Collaborator

odahcam commented Apr 8, 2020

#87 is merged, you can follow with this now.

@PowerKiKi PowerKiKi mentioned this pull request Apr 13, 2020
@PowerKiKi
Copy link
Contributor

I took the liberty to rebase this PR in #91. Hopefully this will help to get it merged.

@odahcam
Copy link
Collaborator

odahcam commented Apr 13, 2020

Let's follow there then, thanks.

@odahcam odahcam closed this Apr 13, 2020
@maguro
Copy link
Contributor Author

maguro commented Apr 16, 2020

Thanks for following up on this @PowerKiKi !

@odahcam
Copy link
Collaborator

odahcam commented Apr 16, 2020

Thank you too for the initial PR @maguro .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update dependencies to Angular 9.0
3 participants