ahmed.jeddah19@gmail.com

Angular v19 brings a game-changing update to server-side rendering: Route-Level Render Modes. This powerful feature gives developers fine-grained control over how each route in their application is rendered—whether it’s on the server, pre-rendered at build time, or handled entirely on the client. This new flexibility is a huge win for developers building dynamic, performance-critical applications. […]

With Angular v19, transitioning from traditional decorators like @Input, @Output, and @ViewChild to the new Signals API is easier than ever! Angular now provides dedicated migration commands to help you modernize your codebase with improved performance and reactivity. 🔧 Migration Commands ✅ Migrate Decorators One by One • @Input to Signals ng generate @angular/core:signal-input-migration •

Angular has always had great tools for building interactive, scalable apps — and if you’ve been working with it for a while, you’re probably no stranger to the classic banana-in-a-box syntax: [(value)]. 🍌 But in 2025, Angular is leveling up again — introducing the new model() function, making two-way binding simpler and more declarative than

If you’re building Angular apps in 2025, here are some practical, performance-oriented patterns you should definitely be using — from Signals and Change Detection to Storybook integration and template composition with ng-content. ⚡ Signals for Reactive State Management Signals are the go-to reactive primitive in Angular for change detection and improved performance. Declaring a Signal

Angular just got a lot more template-friendly. The new @let feature brings a much-needed way to define and reuse variables directly in your HTML templates — no more cluttered expressions or awkward workarounds. If you’ve ever wished for a cleaner way to avoid repeating the same logic in multiple bindings, @let is the answer. Let’s

In modern web development, performance is everything — and Angular’s new @defer syntax is a game-changer for optimizing load time and user experience. It gives you a simple, declarative way to lazy-load parts of your UI that aren’t needed right away, helping cut down on initial bundle size and boosting metrics like Largest Contentful Paint

Angular’s effect() function is a powerful tool — but like any powerful tool, it can be misused. One key rule to remember is this: Only use effects when you need to do something outside the template that can’t be done with standard data binding. Keep Angular’s Auto-Tracking in Mind One of the important things to

While exploring Angular’s Signals system, I came across something that initially felt a bit redundant — linkedSignal. At first glance, it seems like you could just use computed() to handle state that depends on other signals. For example: This works fine if all you need is a reactive read of the first shipping option. But

If you’re upgrading your Angular project to the release candidate of Angular v19 using the CLI, you might run into a flood of Sass deprecation warnings during build or serve. You’ll probably see messages like: These warnings are triggered by deprecated Sass functions like darken() and stem from updates in the Sass compiler used under

Why Choose RxJS for Managing State in Angular? RxJS is a reactive programming library that’s deeply integrated into Angular. It allows you to work with asynchronous data as streams, making it easier to handle state changes over time. When you use RxJS for managing application state, you gain several advantages: Key RxJS Concepts for Managing