Відео

😄 It was a journey!

If you have a GitHub repo I can see, maybe. I haven't seen that particular error message before

Yes you can. When you generate a new app it gives you the option to use Tailwind

Thanks Owen!

With somewhat automated migrations, and newer features moving forward relying on standalone being used, I think this not be the case. Standalone components are simpler to build a mental model around, and when they remove the need for double imports, they will get even better. So I think the tradeoff is worth it. Big corporate codebases will be slow to migrate either way.

@@BrandonRobertsDev Thank you for your thoughts! Will be discussing it with my teammates to project in the mid run a migration to standalones.

Cool! Let me know how it goes

Yes, it follows the same pattern you make any API request with. If you put it in the routes folder, it will be /api/my-route

@@BrandonRobertsDev thanks. That makes sense!

It is Angular and the original logo was released before the logo rebrand. Everything associated with Angular is not required to look the same.

For example using Angular and Drupal

Oh really, how so?

@@BrandonRobertsDev in a hybrid mode, many CMSs would be able to create routes from managed pages directly into a route.

Ahh, I see. Cool

Thanks Ryann!

Good point. Maybe this will start to spread the word

🤝

We can at least explain the numbers better now 👍

😅

Yes, of course 😂

Yeah, found one in an Angular 14 project. Will remove! (it's on Angular 14, because I didn't had time yet to remove flex-layout. That was a sad day when that got deprecated...)

😮

@@larshanisch it was a sad day when flex-layout got deprecated true, I don't know if it still makes sense to use it today but you can check out ngbracket/ngx-layout, this is the currently maintained version

TENET 😂

Kudos to you for working through all those migrations!

Yep. It's because even if you've upgraded along the way, Codelyzer is still in your package.json getting downloaded and in turn downloading its own copy of 9.0.0 because of the hard dependency

eslint/tslint were added later, and they are third-party packages also

I couldn't let it go lol

Interesting! Why every 3 versions? That way you're still in the LTS support window?

@@BrandonRobertsDev I like to update Angular every 3 versions. This way, I can get the latest features without sacrificing project stability. Skipping a version in between gives me time to see if there are any reported bugs or compatibility issues. Of course, if a crucial feature is released in an intermediate version, I'll consider updating for that. Overall, this approach gives me more time between updates, lets me stay within the LTS window, and still get new features without feeling rushed. I'm aiming to migrate to v18 in the coming weeks.

Thanks for the insight!

lol, I'm sure there's a reason it was pinned, but its been skewing the numbers for yearsss 😂

@@BrandonRobertsDev I guess he forgot about it? Did you ask him? :D

Same. This one stands out because we always talk about trying to be on the latest version of Angular, but the downloads have always reflected something different.

Definitely, the 3rd party lib ecosystem needs better tools to handle upgrades also

Surprising for sure!

Hopefully at least your on AngularJS with the .component function? 🙏

@@BrandonRobertsDev yes thank god! I am migrating AngularJS to Angular 17, step by step, pain in the a$$

Me too! ngUpgrade does work though.

Nice. How were the upgrades? Did you upgrade one version at a time?

@@BrandonRobertsDev Sure using the Angular cli update schematics. the app is built from different libraries so I had to teach every team of the company on how to deal with that. The application also still partially relies on UpgradeModule for angular.js. We are still running a few third party dependencies using ngcc. I don't know how it plays out with the router since the company uses a router and a UI toolkit I wrote that's partially built on top of Angular CDK (tables, overlay). Basically our feature libraries are mostly built from this toolkit and Angular core/common. We had some issues with a library that was using Material, mostly due to changes in the sass API but was a niche case. For the core/common parts the cli does a really good job on migrating the code and the configuration unit tests included. The Api is mostly consistent from 8-15 so no issues in that regard. We proceeded by ensuring that all libraries met the requirements (es. ModuleWithProviders with generic type set) then we upgraded the projects to ng15 and the first iteration was using ngcc on each library. We later upgraded all the libraries. The ngcc does a great job, it's only annoying if you need to compile them locally and link them since it does require ngcc to run and you can't just serve and watch from changes as easily as normal. I recommend anyone to jump to 15 since most stuff just works if you ignore peer dependencies requirements that may be outdated. From 16 ngcc is no longer a thing so we still need to upgrade some stuff before looking into beyond 15. We're still on rx.js 6 and we have some issues because also if not correctly stated in the breaking changes, rxjs 7 does no more provide rxjs/operators package and for that we may need to refactor many imports in many libraries.. any suggestions on this?

That sounds like a nightmare to me lol

RxJS still has rxjs/operators in 7.x for backward compatibility. We've stuck to using those in libraries because not everyone is using RxJS 7.,

Netflix series? Yes, please lol And yes, that's correct. I found so many example projects and repos from v9-12 and all of them when downloaded count every week

those would be some cool series :) I would watch

Good to hear. How often do you update?

@@BrandonRobertsDev Not often enough 😔

Thanks Alex!

Thanks. I'm glad to finally get this out of my brain :)

👀 No plans to upgrade or migrate?

@@BrandonRobertsDev Yes, ive been saying it for years. new projects are done in Angular 15, these will beupgraded soon for.

lol that would be something

that would be a lot of work, but if you start I will be supporting you and sending tons of encouragement along the way 😃😇

And will be 😭

no please dont

🤣

you are not cool if you are not using v9 🤣🤣🤣 jk of course

Not yet, but you can still fetch data with HttpClient like you normally do. Just be aware that you need to use the full URL to the resource and not just the resource http.get('localhost/assets/myconfig.json') for example

@@BrandonRobertsDev thanks, As I have been looking at how nuxt 3 do it and they use the $fetch with a path to the resource, so I was wondering if its done in the same way

You missed a good video then. We got the notifications fixed 6 minutes in 😄

RxAngular is a great option also. It's well maintained by very smart people and is very focused on performance around Angular primitives.

If you've followed meta-frameworks, they have a set of features that Angular does not have integrated together. Filesystem-based routing, API routes, hybrid SSR/SSG enabled by default and support for non-node environments. If you want to use Angular SSG and build the rest yourself, that's fine too. Analog is an integrated experience.

Try again with the latest release. It should resolve the timeout npm create analog@latest my-blog