Angular - Policy for Framework version (in package.json) #630

New Issue

fergalmoran · 2025-08-09T17:17:02Z

fergalmoran commented

2025-08-09 17:17:02 +00:00

Originally created by @fredrik-lundin on 6/26/2017

What's the plan when it comes to keeping the @angular/* packages up to date in the template? I noticed that they are hard coded to specific versions (4.1.2 as of today).

Some options:

Could it be considered to use the package: ^version syntax, like the Angular CLI team is doing?
Could it be considered to accept PR's from the community with updated Angular versions when they are released?
Would it be preferred that the maintainer manage it on his/her own?

*Originally created by @fredrik-lundin on 6/26/2017* What's the plan when it comes to keeping the `@angular/*` packages up to date in the template? I noticed that they are hard coded to specific versions (4.1.2 as of today). Some options: - Could it be considered to use the `package: ^version` syntax, like the Angular CLI team is doing? - Could it be considered to accept PR's from the community with updated Angular versions when they are released? - Would it be preferred that the maintainer manage it on his/her own?

fergalmoran closed this issue

2025-08-09 17:17:02 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#630