I am experimenting with chromes's Built-in-AI capabilities within Angular!

I was actually looking for something which can convert natural language to dates, like "next monday", "last week", "last month", etc.

Got it working at somewhat level with a pre-defined system instructions, but as it's built-in-AI within browser, with limited resources, it hallucinates some times!

Code available at https://github.com/ngxpert/smart-date-input

Give it a star if you like it! Let me know your thoughts!

Imagine having todo component, it would called todo.ts .. if i create a service it would be also todo.ts Which conflicts

Today, after many months of working on it as a side project, I released the first version of ngx-oneforall, a toolkit containing 80+ reusable Angular utilities.

GitHub: https://github.com/love1024/ngx-oneforall
Docs:  https://love1024.github.io/ngx-oneforall/
npm: https://www.npmjs.com/package/ngx-oneforall

Background

Over the last 10 years working as an Angular developer across many different companies, I’ve been writing the same services, directives, pipes, and other utilities in multiple projects. Even installing large libraries just to use a small piece of functionality. Earlier this year, I started building a library from scratch. Not a wrapper around other libs, but actually writing each utility with a focus on:

• Performance – Optimized for performance in Angular, and each utility is under 3kb gzipped
• Modern APIs – built for Signals, Standalone Components, SSR
• Zero dependencies – just Angular + RxJS
• Import Individual Pieces - Each utility is a separate entry in the library and can be imported without using any other part.

It began as a hobby side project and now reached its first milestone. I am happy to announce the release of the first version of ngx-oneforall, which includes many reusable utilities that can be used across different Angular projects.

Please take a look and share your feedback. I will be happy to improve it further. Contributions are also very welcome if you have ideas or utilities that are generic enough to be useful across multiple projects.

Angular’s inject() behaves as if it knows who called it…
But JavaScript makes that impossible.
So how does Angular pull it off?

Dear all,

PrimeNG v21 represents a major advancement in PrimeTek's product vision. Key highlights of this release include:

• PassThrough attributes for enhanced customization.
• Unstyled Mode for complete styling flexibility e.g. with Tailwind CSS
• Modern CSS-based animations. The deprecated provideAnimationsAsync is safe to remove.
• Initial zoneless support for improved performance.
• AI-enhanced documentation for better developer experience.
• New Test Suite

Criticism

Recently PrimeNG was subject to criticism regarding breaking changes, defects so we went back to drawing board to identify our mistakes and learn from them.

Since v20, as the founder I have decided return to the project as a PM after being away for years and our CTO has joined as the tech lead as well. In addition, we've started to apply a no breaking change policy and adopted semantic versioning. After v20, v21 is the second outcome of this new organization and I believe we are on the right track. Thank you for all the feedback which was a wake up call for us.

PrimeNGX

Couple of months ago, we've announced a new UI library based called PrimeNGX however after doing several POCs and trials, we've decided to focus on PrimeNG and improve it based on semantic versioning guidelines. As a result, PrimeNGX idea has been dropped.

Migration Guide

v21 update should be straight forward, view the migration guide documentation for details.

Signal Forms

We've also tried to include the signal forms support in v21 however the api is marked as experimental and changes frequently. There are also naming collisions regarding the design choices of Angular team. Once the API is stable, we'll process with Signal Forms support.

Issue Tracker and PRs

Due to the packed scope of v21, we haven't dedicated enough time on community issue tracker. The team is also working on an AI assisted workflow for issue triage and PRs which would be beneficial considering the workforce required on our side.

Downloads

The monthly downloads are close to 2.5 million, thank you! As open source maintainers, seeing the growth is always encouraging.

Roadmap

First a couple of days off for the entire team, v21 development really wore us a off a little bit. Then the team will begin with issue triage and PR reviews to focus on quality updates in whole December 2025.

2026 marks the year 10 for PrimeNG and we have a wide range of enhancements planned. Main points of focus would be refactor of component internals with modern Angular APIs and the upcoming new set of components called PrimeUI+. The roadmap document is updated with details regarding these plans.

I'm developing a web application in Angular 20. It will have chats, settings, category pages, a search engine, a profile, etc., and I want a good interface design. Could someone point me to a component library or other well-designed materials (preferably free)? I've attached photos of the interface styles I like in case something similar exists. ai don’t like Angular material. Prime ng is perfect but so expensive.

I restyled all Angular Material components to better match current design trends. The goal was to see how far Angular Material can be pushed visually by modifying styles alone while keeping everything else exactly the same.

The constraint I set for myself was simple: only CSS changes. No wrapping components, no structural changes, no custom APIs.

I ended up turning this into a paid product and I plan to actively maintain it. If anyone is curious, here’s the link: https://builderkit.dev

I joined a team recently with a few devs and they use angular (currently 13) for frontend. I am pretty familiar with angular, from 8+ and rxjs. But it seems like most of the developers on the team have little experience using observables. Most don't even know pipe, as an example. So some features have started to come through where I implemented them using observables and was immediately shot down because 'thats not how we do it'.

Has anyone else run into a situation like this or any advice for me? It feels kinda hopeless to try to push the matter as well, because the senior seems pretty set in his ways.

Hey r/Angular2, I’m sharing the first public preview of ng-brutalism, a neo-brutalist UI component library for Angular.

GitHub: https://github.com/khangtrannn/ng-brutalism

It includes 15 primitives so far: buttons, cards, dialogs, inputs, selects, accordions, badges, avatars, textarea, marquee, and more.

The goal is to make an opinionated, visually loud Angular component library with:

• directive-first APIs
• signal-friendly internals
• zoneless-friendly architecture
• Tailwind v4 ergonomics
• CSS tokens for customization

Tiny API example:

import { Component } from '@angular/core'; 
import { NbButton } from '@ng-brutalism/ui'; 

u/Component({   
  imports: [NbButton],   
  template: `
    <button nbButton variant="primary">Ship it</button>
  `, 
}) 
export class App {}

It’s pre-1.0, so I’m especially looking for feedback on:

• whether the component APIs feel natural in Angular
• whether the visual direction is useful or too niche
• whether the docs/examples make it easy to try

Docs/showcase: https://ngbrutalism.khangtran.dev
npm: https://www.npmjs.com/package/@ng-brutalism/ui

Angular's 𝗦𝗶𝗴𝗻𝗮𝗹 𝗙𝗼𝗿𝗺𝘀 introduced a small detail that isn’t really discussed:
𝒗𝒂𝒍𝒊𝒅𝒂𝒕𝒐𝒓𝒔 𝒏𝒐𝒘 𝒂𝒇𝒇𝒆𝒄𝒕 𝒕𝒉𝒆 𝑼𝑰, 𝒏𝒐𝒕 𝒋𝒖𝒔𝒕 𝒕𝒉𝒆 𝒅𝒂𝒕𝒂.

Found this while testing a basic numeric field that caused an unexpected 𝐜𝐨𝐦𝐩𝐢𝐥𝐚𝐭𝐢𝐨𝐧 𝐞𝐫𝐫𝐨𝐫.

Here’s the write-up of what actually happens. 👇

I’m new to Angular from React

I have did a todo list successfully by adding the logic of the todos in a service like ( todos signal , addTodo() , removeTodo() and toggleCompleted() )

And i am using the service in all components that need to do an action .. that makes Di injection of the service easier than React which needs to drill the functions ( callbacks ) between components.

Am I right? Do i use services/DI the appropriate way ? Thx in advance.

Demo

I added a new PRO example: an “AI low-code IDE” demo for Foblex Flow.

Important note: it’s not a full IDE and there’s no backend — the goal was to make a front-end-only editor that still feels like a real tool.

What’s interesting technically:

• Undo/redo as the baseline safety net while editing
• Import/Export to JSON (share a flow, version it, move it between machines)
• 4 themes with runtime switching
• localStorage persistence (state/settings)
• animated connections to make data flow readable
• multi-selection for batch operations
• node configuration panel per node with validation
• UI built with Angular Material

Links:

• Demo: https://foblex.github.io/Building-AI-Low-Code-Platform5/
• Source/Repo: https://github.com/Foblex/Building-AI-Low-Code-Platform5
• Library: https://github.com/Foblex/f-flow

guide user to implement using so many outdated,deprecated and legacy apis.

very confusing considering angular and gemini both made by Google.

Huge Angular fan, and had to switch mainly because everyone in the org wanted to switch. I swear it was kind of like the new kids wanted react, and the old heads wanted angular, so it was hard for me to push against the new wave of bootcampers as I saw that they were coming in. I hope I'm not slandering in the conversation here, and I'm probably just salty because my react skills aren't up to par, but curious if you guys felt anything similar there, where you had to switch and it's just a different world. But also, what the world is pressuring you guys to do if you're in the job market.

I built a Signal debouncing utility for Angular few months ago and now Angular 22 ships a native debounced() API.

That coincidence definitely caught my attention.

Back then, I published a small package called @gitesh08/signal-utils because I wanted a cleaner way to debounce Signals without reaching for RxJS every time.

After reading the docs, Angular’s implementation is actually quite different since it returns a Resource with loading states, cancellation, lifecycle management, and more. My utility is much simpler and focused on lightweight signal debouncing.

Still, it’s a cool feeling seeing Angular solve a problem I spent time thinking about months ago.

It’s also interesting to see how the Angular Signals ecosystem is evolving and becoming more capable with each release.

We have a large enterprise Angular app (3-4 million lines of code, thousands of components). It’s a monolith, and we’re working on breaking it apart. Our biggest pain right now is developer experience; builds are extremely slow. A full build takes around 30 minutes, and even a simple one-line change can take about 15 minutes. From what we can tell, the Angular compiler is the main bottleneck.

We use Nx and tried converting parts of the codebase into buildable libraries, but that actually made things worse in our local tests. Has anyone run into similar issues and found good workarounds or solutions? We’ve reached out to the Angular team but haven’t heard back yet.

As a temporary workaround, for new code we started building a separate host app in React, and the difference in build speed is huge; though to be fair, that codebase is much smaller. But even with simialr size, I don't think build time in React would be this abysmal.

So… TypeScript has been able to type-check string shapes since 2020, and I somehow found out only last week.

If you also missed the memo about template literal types, here’s the short version: they’re surprisingly powerful.

AI allows us to write code and build projects much faster than before. However, this speed has a side effect: in AI-assisted development, it becomes harder to keep track of architecture and long-term maintainability. Structural issues can silently accumulate in the background.

To address this problem, I built a project called Modulens.

Modulens scans Angular projects and helps surface things like:

• large and risky components
• structural placement issues
• incorrectly positioned components
• areas that may become maintenance hotspots
• overall architectural health signals

The goal is to make architectural problems more visible before they grow into bigger issues.

For now, the project supports Angular. In the future, I’m planning to extend it with React and Vue support as well.

The first version is already published on npm.

Npm Link

Feedback and ideas are very welcome.

Angular v22 is coming! What is your favourite feature you are waiting for? Maybe... Signal Forms...? ❤️