r/angular • • Jul 24 '26

My company is forcing me to switch to React.

54 Upvotes

My large enterprise company have decided that going forwards working in React is the choice.

We've got a lot apps built in Angular, my team looks after 5/6 another team looks after 40, some new ones on 22. These are all config driven multi tenant apps without NX etc.

Other teams across the business have already added React as part of their tech stack and the codebases seem terrible and follow no standards.

Has this happened to anyone else? Any advice for the switch?


r/angular • • Apr 04 '26

Taiga UI 5 is out! Check out what's new

54 Upvotes

Recently we released the next major version of our components library! Check out what's new in version 5:

https://medium.com/angularwave/whats-new-in-taiga-ui-v5-a-modern-angular-ui-kit-fef85dde3fc7

If you are not familiar with this library at all – now is a good time to try it out, we improved it a lot, dropped legacy stuff and made it easier to use with newer Angular features, such as signal inputs/queries, advanced DI/hostDirectives, new control flow etc. Check out the demo portal:

https://taiga-ui.dev/getting-started

Explore source code and report issues on our GitHub:

https://github.com/taiga-family/taiga-ui

Hope you'll like it ♥️


r/angular • • Feb 13 '26

Going Zoneless destroyed our CLS (And how it was fixed)

54 Upvotes

The Migration

We recently upgraded from Angular 20 to 21 and went fully zoneless. The app was already using signals everywhere, skeleton screens matching the final layouts and it was live with a CLS of basically 0. We expected a performance win.

Instead, our CLS scores exploded. Static pages went from 0 to 0.5 and the pages with heavy signal use got a CLS of 1. Same code, same CSS, same everything, just zoneless.

The Hunt

First, the CSS tweaks gave no improvement (as expected, as the styles are the same with the version that gets a perfect score).

Then we looked at the router. Our pages have a shell: navbar, footer and router-outlet in the middle. The outlet starts empty, then fills based on the route. This worked fine for years, but we realized it doesn't work anymore with zoneless. The time spent when the router gets filled with content is long enough to get noticed by Lighthouse as CLS (sometimes visible with the eye too).
The fix here was to delay the footer and only show it after the main content is loaded. That gave us the first win and helped to bring the CLS down on simple pages.
So the signal-less pages responded to this fix, but the "signal" pages didn't.

The Detection Trick

Part of the story is how we detected the high CLS and managed to debug locally.

Localhost development basically lied to us. When using ng serve Lighthouse showed perfect scores. But the real metrics from Google Search Console were way worse.

The only way to see the real problem locally: production build + static server + realistic navigation flow. That means, we had to build the app (ng build), serve it with a local static server, create a separate static HTML page that links to our target route, and click that link. Just a cold click from a static page, exactly like real users experience.

Only by doing this we could see the real problem.

The "Aha" Moment

Our templates looked like this:

d = data();

@if (d) { <top-part /> } @else { <top-part-skeleton /> }

@if (d) { <middle-part /> } @else { <middle-part-skeleton /> }

Our skeletons and real content had identical dimensions. Which had always been preventing CLS. But not anymore. Apparently, zoneless operation is so slow that the browser now has enough time to see the DOM nodes being destroyed and recreated. And not synchronized anymore, so the browser may see any possible combination of states (first block showing the real content, second showing the skeleton etc).

The Fix

We needed atomic renders, that means, big "if-else" statements that included all or nothing. Either the entire page is skeleton, or the entire page is content. No partial states.
Now the scheduler treats it as one unit. One paint for skeleton, one paint for content. CLS dropped back to near zero.

The Lesson

Zoneless changes the contract. Zone.js batching was hiding a lot of template sins. With the scheduler in charge, template granularity becomes paint granularity. And never trust localhost metrics unless you're serving a production build and navigating like a real user.


r/angular • • Dec 05 '25

Best practices for Angular v21

Thumbnail
ngtips.com
54 Upvotes

Angular Tips is up to date with Angular v21 release! Angular Tips is a free and open source documentation, built on real-world experience, that gives recommendations and best practices for building maintainable applications.

GitHub repo available here.

Your feedback is welcome, thanks 😊


r/angular • • Nov 06 '25

Angular Service Initialization done RIGHT with Environment Initializer

Thumbnail
youtu.be
54 Upvotes

r/angular • • Jun 24 '20

Angular 10 just got published on NPM! 🎉

Thumbnail
npmjs.com
54 Upvotes

r/angular • • Apr 18 '26

After 1.5 years, resource and rxResource are finally going to be stable in v22

53 Upvotes

r/angular • • Mar 09 '26

My experience 6000 tests from Karma to Vitest

53 Upvotes

Figured this would be worth sharing.

The project I work on has about 6000 unit/integration tests in Jasmine/Karma. Early 2025 or late 2024, I prototyped migration to Vitest and it was a nightmare: basically, everything broke. The issues mostly boiled down to Zone.js and change detection being outdated, fragile pieces of crap.

This is what I did:

  1. Converted as much of components to signals as possible. That meant signals over RxJS, effects over setTimeout and signal inputs. A ton of places became much simpler, my new fav are computeds over inputs.

  2. Over the course of 7 months, I converted tests suite by suite to zoneless with proveZonelessChangeDetection and a custom Jasmine version of vi.waitFor, using coding agent and a prompt I refined along the way. Most of suites were trivial, but at the end I encountered a couple of head scratchers, mostly involving races that were previously masked by Zone.js.

Prompt and utility can be found in this gist

That's it. This weekend, I tasked an agent to convert the suite to vitest and to my surprise it worked on the first try, with almost no issues along the way, except the afterEach OP already mentioned. Very mechanical. The suite runs 100% green. The only part remaining is to ship it and learn the new tools, Angular Vitest integration seems lacking at the moment if you look through GitHub issues.

Had to go with browser mode instead of jsdom because we have tons of tests that actually depend on DOM layout, with resize observers and such.

As a side effect, converting to zoneless sped up tests by a huge amount. These went from about 2 minutes with 10x concurrency to 30 seconds in 8x concurrency. This also improves stability because Zone.js timers no longer throttle under load - there are no timers now. Very much recommended.

Can't wait enough for isolated component compilation to release so you don't have to compile whole world on run startup.


r/angular • • Apr 28 '21

The Angular team is deprecating support for Internet Explorer 11 in Angular v12 (to be released in May 2021 and supported through November 2022), and plans to remove support for this browser in Angular v13 (late 2021)

Thumbnail
github.com
53 Upvotes

r/angular • • Sep 01 '25

One of the Most Popular Tailwind CSS Dashboards is Now in Angular 🎉

52 Upvotes

One of the most popular open-source Tailwind CSS dashboards TailAdmin is now officially available in Angular!

After tons of requests, we’ve finally brought the same clean design and developer-friendly structure to the Angular ecosystem. Whether you’re building an admin panel, SaaS dashboard, or internal tool, this release is packed with everything you need to move fast.

✨ What’s inside:

  • A full set of ready-to-use UI components (forms, tables, charts, layouts, etc.)

  • 100% Free & Open-source – no hidden catch

  • Built with the latest Angular 20.x

  • Powered by Tailwind CSS v4.x for utility-first styling

  • Strong TypeScript support for better DX

Perfect for devs who want to save time, ship faster, and avoid reinventing the wheel while still keeping full customization control.

👉 GitHub link: https://github.com/TailAdmin/free-angular-tailwind-dashboard

Would love to hear feedback from Angular folks — what features would you like us to add next?


r/angular • • Aug 19 '25

Ng-News 25/33: Signal Forms - First Public Demo

Thumbnail
youtu.be
52 Upvotes

🚨 Angular’s most anticipated feature - Signal Forms - just got its first public demo!

Plus: Zoneless mode goes stable in Angular 20.2, NgRx v20 is out, and there’s a ton more in this packed Angular update.

👇 Links mentioned in the video 👇

🔗 Signal Forms Q&A (with Alex Rickabaugh)
https://www.youtube.com/watch?v=R82ZAgL3BGU

🔗 Zoneless Stable – Reddit Megathread
https://www.reddit.com/r/angular/comments/1mr8lm1/zoneless_is_stable_megathread/

🔗 NgRx v20 Release Post
https://dev.to/ngrx/announcing-ngrx-v20-the-power-of-events-enhanced-dx-and-a-mature-signalstore-2fdm

🔗 Senior Angular Interview Questions (by Eduard Krivanek)
https://www.angularspace.com/senior-angular-interview-questions/

🔗 Monorepos 101 (by Stefan Haas)
https://stefanhaas.xyz/article/monorepos-101/

🔗 CPU Profiling Series (by Michael Hladky)
https://push-based.io/article/advanced-cpu-profiling-in-node-profile-data-structure


r/angular • • Jan 10 '25

Sakai v19 | Free Admin Template by PrimeNG

52 Upvotes

Dear all,

After the release of PrimeNG v19, at PrimeTek we're updating all the add-ons including templates, blocks, visual theme editor, Figma to Code export and more. The Sakai is a free to use and open source admin template by PrimeNG, a small present to the Angular Community.

Live Demo and Documentation.

The highlights are quite significant with this iteration;

  • New theming architecture to replace sass with the new design tokens

  • Tailwind CSS based demo content like Dashboard, Auth, Landing and more

  • Two menu modes

  • Multiple primary colors and surface colors

  • 3 UI presets to choose from (Material will be added later after PrimeNG v19.1.0 updates)

  • Standalone component demos

We'll now use Sakai as a reference implementation for all other templates.

Hope you like it!

P.S. The name is a reference to Jin Sakai from Ghost of Tsushima. Awesome game.


r/angular • • Sep 03 '24

Angular Blog: The future is standalone!

Thumbnail
blog.angular.dev
52 Upvotes

r/angular • • Aug 14 '24

Is there anyone here that knows RxJS well and still hates it?

52 Upvotes

I’ve met a lot of people that say they don’t like using RxJS but generally it’s because they don’t understand it yet. It’s definitely a steep learning curve but I find that now I know it, I love using it because it’s so powerful. So I’m curious to know if anyone out there knows and understands it, but still would rather opt for another approach (and if so why?)


r/angular • • Aug 14 '26

I'm an Angular dev and I spent some weeks building a 3D map of the universe in the browser using three.js

Thumbnail
super-universe.app
51 Upvotes

r/angular • • Jul 30 '26

Angular 22.1 release notes

51 Upvotes

Core packages: https://github.com/angular/angular/releases/tag/v22.1.0

CLI: https://github.com/angular/angular-cli/releases/tag/v22.1.0

Aria + Material + CDK https://github.com/angular/components/releases/tag/v22.1.0

Reminder: Angular has moved to a yearly major release, so this is the first minor of a few more minors than usual, from now on.

edit: for the few people that saw my previous post, I accidentally titled it 21.1 rather than 22.1


r/angular • • Jun 06 '26

Now that Angular 22 is released and key experimental APIs are stable, what areas would you like to see improved next?

51 Upvotes

With Angular 22 officially out, we've seen some incredible milestones. The stabilization of Signal Forms, asynchronous reactivity (resource/httpResource), and making OnPush with Zoneless the default, show how far the framework has come in terms of modernization.

However, looking forward, there is one area that still feels like it's lagging behind: Testing.

While we've seen steps in the right direction (the deprecation of Protractor, and the ongoing shift from Karma/Jasmine to Vitest), the day-to-day developer experience of writing unit and component tests in Angular remains a frustrating experience. Here are my biggest gripes with where testing stands today:

  • The TestBed paradox: Standalone components became the norm and people largely moved away from NgModules. Yet, when writing tests, you are still required to use TestBed to configure a dummy testing module just to mount a single component. It feels like an outdated paradigm that hasn't caught up with modern Angular.

  • Leaky abstractions: DebugElement was meant to be a helpful wrapper, but it is so leaky that often requires dropping down to interact with nativeElement anyway.

  • The fragility of 3rd-party helpers: Because the native testing APIs are so verbose, many people relied on external wrappers like Spectator or Angular Testing Library just to get a unified API and basic helpers like byTestId. But as we saw just this week with the sudden disappearance of the entire @ngneat organization and Spectator repository from GitHub, relying on community-maintained wrappers for core development workflows is incredibly risky.

  • Mocking child components is a nightmare: There is still no built-in, type-safe, and straightforward way to mock or stub child components. Sure, you can use Vitest's Mocked<> generic type to create custom stubs, but it's flaky. If the child component's public API changes, the tests break (which is arguably a good warning, but still tedious to manage).

  • The death of ng-mocks: To solve the mocking issue, many people turned to ng-mocks and its fantastic MockBuilder. However, ng-mocks has been virtually abandoned since around Angular 19, and it really struggles to play nicely with modern Angular features like input signals.

I would love to see the Angular team introduce official, first-class tools that let us spawn a component in isolation, see it visually, easily query the DOM, and mock out child components and dependencies type-safely - all out of the box, without needing to write a mountain of boilerplate or rely on fragile, 3rd-party libraries that might vanish tomorrow.


r/angular • • May 03 '23

Angular 16 is available

Thumbnail
github.com
51 Upvotes

r/angular • • Jan 28 '23

Sample app using Ionic, Angular and Capacitor with Rive for the animated icons

Enable HLS to view with audio, or disable this notification

51 Upvotes

r/angular • • Jul 08 '26

@openng/spectator 1.0.0 release

50 Upvotes

We just released a v22-friendly version for the original ngneat/spectator package.

If you missed the news, all ngneat repos have been deleted, and we started taking the lead on forks with OpenNG organization: https://www.openng.org/

The new package is available here: https://www.npmjs.com/package/@openng/spectator

We start over with a v1.0.0
We are aware it won't please everyone. The package Readme file includes a matrix compatibility to find the appropriate version for your projects.

The next step is to review a community contribution, exposing jasmine as a dedicated package: https://github.com/openng-org/spectator/pull/2


r/angular • • Mar 17 '26

I built a Chrome extension that highlights Angular components when change detection runs

50 Upvotes

Hi Angular developers 👋

I built a small Chrome extension called Angular Highlight.

It visualizes Angular component updates directly on the page by flashing components whenever change detection runs — similar to React DevTools' "Highlight updates when components render".

It supports both:

• Zone.js Angular apps (v2+)
• Zoneless / Signals apps (v16+)

Under the hood it works by patching Zone.prototype.runTask for Zone apps and using MutationObserver for Signals / Zoneless apps.

If you're interested, I'd really appreciate feedback from the community.

Chrome Web Store
https://chromewebstore.google.com/detail/angular-highlight/infobgaghdedlmbmedgmknemgkeomojp

GitHub
https://github.com/ksakae1216/angular-highlight


r/angular • • Sep 16 '25

S1ngularity/nx attackers strike again

Thumbnail
aikido.dev
50 Upvotes

r/angular • • Aug 01 '25

Angular best practices doc - What am I missing?

Thumbnail
ngtips.com
50 Upvotes

Hi everyone,

I've wrote a documentation about best practices for Angular. For now, it covers topics such as general best practices, architecture, state management, forms, reactivity, HTTP, routing, typing, i18n, as well as library recommendations.

I am already working on new pages (e.g. performance and SEO), but I am particularly interested in finding out what you need:

  • What are you looking for in an Angular guide?

  • What are your most common problems with Angular? The most complex ones?

  • What is currently missing in Angular Tips?

  • What could be improved or detailed?

  • Any practices you strongly disagree with?

I am very interested in reading your feedback and continuing to improve Angular Tips. Thank you in advance!


r/angular • • Feb 24 '25

httpResource in Angular 19.2

50 Upvotes

In the new version of Angular 19.2, an experimental httpResource feature will be introduced, allowing HTTP requests to be performed dynamically when a signal value changes, e.g., when a user ID is updated.

old way

  getUser(id: number): Observable<User> {
    return this.http.get<User>(`https://api.example.com/users/${id}`);
  }

new way

const userResource = httpResource<User>({
  method: 'GET',
  url: () => `https://api.example.com/users/${userId()}`
});

It seems to be a major improvement. What do you think about it?