Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about CollectivesStack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalBoth answers above are correct and are based on the same approach that is the de-facto way as of today.
There are plans from Angular CLI to add an update feature in one of the coming releases.
To update your additional dependencies there is an elegant way by moving them to a second package.json. You can use Yarn Workspaces or package-json-merge for that. More info on my website: https://www.rainerhahnekamp.com/en/updating-angular-cli-dependencies/
Both answers above are correct and are based on the same approach that is the de-facto way as of today.
There are plans from Angular CLI to add an update feature in one of the coming releases.
To update your additional dependencies there is an elegant way by moving them to a second package.json. You can use Yarn Workspaces or package-json-merge for that. More info on: https://www.rainerhahnekamp.com/en/updating-angular-cli-dependencies/
Both answers above are correct and are based on the same approach that is the de-facto way as of today.
There are plans from Angular CLI to add an update feature in one of the coming releases.
To update your additional dependencies there is an elegant way by moving them to a second package.json. You can use Yarn Workspaces or package-json-merge for that. More info on my website: https://www.rainerhahnekamp.com/en/updating-angular-cli-dependencies/
Both answers above are correct and are based on the same approach that is the de-facto way as of today.
There are plans from Angular CLI to add an update feature in one of the coming releases.
To update your additional dependencies there is an elegant way by moving them to a second package.json. You can use Yarn Workspaces or package-json-merge for that. More info on: https://www.rainerhahnekamp.com/en/updating-angular-cli-dependencies/
