vscode-ng-language-service VS angular-update-guide

If you don't know and what a non flexible solution then take a look at the angular language server Note that this ls have the following bug https://github.com/angular/vscode-ng-language-service/pull/1875 which means you need a language server client that supports LocationLink

I am running angular 13.1.1 but string literals do not autocomplete in the template. I saw the feature request https://github.com/angular/vscode-ng-language-service/issues/1096 And implementation https://github.com/angular/angular/pull/42729 The pr was closed without any further update Does anyone know what happened?

Angular Language Service repo (link)

https://marketplace.visualstudio.com/items?itemName=Angular.ng-template https://github.com/angular/vscode-ng-language-service

👉 Language Service config to enable auto-apply optional chaining on nullable symbol - #1469 🎉

Mmm, I think you are on the good path thinking about a conflict. If you look at angular-ls issues, you find a few problems for HTML related to conflict (for example, https://github.com/angular/vscode-ng-language-service/issues/936). Can you indeed try to have only the angular server working for your buffer? (I do not use html-ls)

However, the actual fix needs to land from language service itself. There is an issue opened around type support for custom directives. The fix should land with first class Ivy Support (which is in preview!)

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