angular-update-guide VS angular-cli

update.angular.io *

Hello, i work as a software developer and these days we got a project with the angular in the version 7, one of my tasks is to migrate from 7 to more recent versions, the ideal is the 17. I am trying to follow the step-by-step guide from here:https://update.angular.io/ to go from v7.2 to v8 but i cant even do that. I dont have familiarity with Angular,started to study last week because of this project i mainly work as a backend or with react/next, could you tell what could be the best approach?

Recently, I found myself in charge of upgrading our Angular application from version 12 to 15. In my current role, which I've held for just over a year, most of my focus has been on the backend, and I hadn't even touched the frontend apps until now. I've got to be honest; this upgrade process turned out to be a tougher nut to crack than I initially thought. It's not a knock on the Angular team's Angular Update Guide, though; they did a solid job. The real challenge came from the fact that we had a bunch of custom-made components that didn't quite follow the best practices playbook.

I really recommend the Angular update tool which you can find here: https://update.angular.io

I would like to update Angular from version 5.0 to version 6.1. The instructions at https://update.angular.io/ suggest using ng update @angular/core to update. However this updates directly to version 7 instead of version 6.

Make sure to use https://update.angular.io/ for the upgrade steps and do the upgrade by 1 major version at a time, test if everything works, make a commit and then go for the next version. You may want to go up.

> Every version essentially breaks the previous one.

This is simply not true. It might have been true in the early Angular v2 days, but since v6 or so, updates are relatively trivial.

https://update.angular.io has your back extremely well. The trick is to ensure whatever third party libs you're using have also been updated, otherwise you're application may break.

CLI has improved over the years, enabling smooth migrations between Angular versions. Check out https://update.angular.io/

Just go to https://update.angular.io/ and follow the instructions

module.exports = async (util, rule, host, injector) => { let list = await util.changeList([ { type: 'copy', source: 'git', from: { url: 'https://github.com/angular/angular-cli.git', match: '/packages/schematics/angular/directive/files', output: '/packages/schematics/angular/directive/files', }, pathTemplate: '@angular-devkit', contentTemplate: '@angular-devkit', pathTemplateSuffix: '.template', templateContext: { name: 'hello', standalone: true, selector: 'hello', 'if-flat': (input) => '' }, to: './hello-directive' }, ]); await util.updateChangeList(list); };

Well, scream though I have, the Angular team desperately needs to Remove NodeJS Dependencies, as it has already fallen behind from all frameworks concerning deployment. I'm still waiting for the response on this... 🦗 🦗 🦗 🦗

PR: feat(@angular-devkit/build-angular): add define build option to application builder

The new ssr CommonEngine source code

Source: https://github.com/angular/angular-cli/issues/25134

I'm not sure how to solve this but here's something that looks similar to your issue - https://github.com/angular/angular-cli/issues/24373

Sass errors after migrating from Angular 13 to 15 / Node 14 to 18

Edit: Found it at Github https://github.com/angular/angular-cli/issues/25574. So it seems to be a problem

Remove Dependencies for NodeJs

Is it possible to teach llm to read issues and answer questions such as how do I get angular 17 to output to dist instead of dist/browser with you can't do this with angular. However, in your CI CD pipeline, you can do a mv or robocopy or bla bla bla depending on context?

https://github.com/angular/angular-cli/issues/26028

It would be very useful because there are so many edge cases that aren't covered in the docs but are probably available in some kind of WON'T FIX issues.