Description

lacolaco

opened on Sep 27, 2017

Issue body actions

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Desired functionality.

After updated the CLI version, sometimes package.json is updated. Currently package.json is generated at ng new and never do sync to latest dependencies.

I want something like ng doctor to solve it. The use-case images are below:

$ ng doctor # listing up dependency changes
$ ng doctor --write  # auto-patching on _compatible_ version (with semver ?)

Mention any other details that might be useful.

Reacted by Tomasz, Daniel Whitney, Solen Oliviéro-Naturel, CaerusKaru, José Toledo Navarro, 2beers, iamjoyce, DreamPWJ, R., Denis Bendrikov and 2 more

Reacted by Markus Thiel, Andony Núñez, elclanrs, Dmitry Zakharov and PaoloB

Activity

1. filipesilva

   assigned

   hansl

   on Sep 27, 2017
2. filipesilva

   added

   P5The team acknowledges the request but does not plan to address it, it remains open for discussionThe team acknowledges the request but does not plan to address it, it remains open for discussion

   featureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issues

   on Sep 27, 2017
3. lucasvanhalst commented on Sep 27, 2017

   

   lucasvanhalst

   on Sep 27, 2017

   More actions

   You could use this in the meantime which basically does what you described https://github.com/tjunnone/npm-check-updates
4. lacolaco commented on Sep 27, 2017

   

   lacolaco

   on Sep 27, 2017

   ContributorAuthor

   More actions

   I want to know about added and removed dependencies. only existing packages version check is not enough.
5. hansl

   removed their assignment

   on Feb 6, 2018
6. filipesilva

   added

   area: @angular/cli

   on Oct 1, 2019
7. ngbot

   added this to the Backlog milestone on Oct 1, 2019
8. filipesilva

   removed

   P5The team acknowledges the request but does not plan to address it, it remains open for discussionThe team acknowledges the request but does not plan to address it, it remains open for discussion

   on Oct 1, 2019
9. clydin

   added

   triage #1

   on May 27, 2020
10. angular-robot

    added

    feature: votes requiredFeature request which is currently still in the voting phaseFeature request which is currently still in the voting phase

    on Feb 1, 2022
11. angular-robot commented on Feb 1, 2022

    

    angular-robotBot

    on Feb 1, 2022

    Contributor

    More actions

    Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

    Find more details about Angular's feature request process in our documentation.
12. ngbot

    modified the milestones: Backlog, needsTriage on Feb 1, 2022
13. angular-robot commented on Feb 21, 2022

    

    angular-robotBot

    on Feb 21, 2022

    Contributor

    More actions

    Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

    We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

    You can find more details about the feature request process in our documentation.
14. angular-robot

    added

    feature: insufficient votesLabel to add when the not a sufficient number of votes or comments from unique authorsLabel to add when the not a sufficient number of votes or comments from unique authors

    and removed

    feature: votes requiredFeature request which is currently still in the voting phaseFeature request which is currently still in the voting phase

    on Feb 21, 2022
15. alan-agius4

    removed

    triage #1

    on Jun 24, 2022

Issue actions