#update packages

3 messages · Page 1 of 1 (latest)

fleet plover
#

I switched to Angular 19.
I ran the npm outdated command and this is the result

Package                            Current   Wanted   Latest  Location                          
@angular/google-maps               18.2.14  18.2.14   19.0.0  node_modules/@angular/google-maps 
@angular/language-service          18.2.12  18.2.12   19.0.0  node_modules/@angular/language-service          angular-19-jest
@angular/localize                  18.2.12  18.2.12   19.0.0  node_modules/@angular/localize                  angular-19-jest
...

there is nothing in red.
but I notice a difference between "current" and "latest"
(1) My question is that I have to change the packages to latest or no need ?
(2) with "latest", that doesn't mean that it will work, that it will be compatible? so the most important thing is “wanted”?

This is a big business project.

azure cargo
#
  1. depends on project but mustly no need.
  2. I think there won't be any compatibility issue between 18.2 and 19.0

I wouldn't update if there is no "must case"