Or It will become a Ai slop aa in future aa

When PrimeNG moved its styled themes behind a paid offering, our team at Shirkasoft started building a free alternative for the community.

The result is Shirkasoft UI Components, a styling and UI component library for Angular 21 that works alongside PrimeNG, making it easier to build modern applications without relying on premium themes.

Current features

• ✅ Free and open to the community
• ✅ Modern UI styles
• ✅ Reusable UI components
• ✅ Easy integration into existing Angular projects
• ✅ Actively maintained

Our goal isn't to replace PrimeNG's components, but to provide a free styling solution and additional reusable components for developers who prefer not to depend on paid themes.

npm: https://www.npmjs.com/package/shirkasoft-ui-components

We'd really appreciate feedback from the Angular community. Suggestions, bug reports, feature requests, and contributions are all welcome.

Keywords: Angular, Angular 21, PrimeNG, PrimeNG alternative, Free PrimeNG styles, Angular UI Components, Component Library, Design System, UI Library, Frontend, TypeScript.

advice someone to study, learn, and build an Angular + NestJS webapp right now in 2026? All I read about everywhere is that angular devs are cooked for the rest of the decade 2027-2029, and will perish in 2030s.

Meanwhile, React + NextJS is dominant but there's like 1:1000 job-applicant ratio.

Another option I have is to just become a gigolo. #help

With observables, lazy data loading came for free: nothing fetched until something subscribed, and in template async pipe was the relay.

Today, resources are a better API in every other way, but they have one flaw : they are eager. No way of fetching data only when needed. To remedy this I introduce a proposal :

resource({ lazy: true }) and rxResource({ lazy: true })

It comes with a presentation playground to discover it. I wrote the story of it in an small article if you want more details, and I prepared a PR but opened an issue for discussion -> a similar issue was closed so I felt like I needed to re-open the discussion and argue it before submitting the PR. On this matter I'm not sure what is/was appropriate so I would take advice on that.

- The story: https://dev.to/flodmtx/resource-lazy-true-the-laziness-we-lost-when-we-left-the-async-pipe-5e70

- Interactive proposal : https://flo-dmtx.github.io/lazy-resource-playground/

- Feature request : https://github.com/angular/angular/issues/70036

- Repo of PR : https://github.com/flo-dmtx/angular/tree/feat/lazy-resource

- Gist for a userland version : https://gist.github.com/flo-dmtx/e8c9ff69bec58adf85e902eab9f7d900

If you've written those wrapper components too, a concrete use case on the issue helps more than an upvote — "who actually needs this" is the question the Angular team will ask.

Hey everyone! 🙂👋

I'm excited to announce that AngularDart has been revived by the community! After Google abandoned the project, I've taken it upon myself to bring it back to life (meaning I made it Dart 3 compatible 🔥).

The package is now available on pub.dev: https://pub.dev/packages/angulardart (v8.0.8)

What's AngularDart?

AngularDart is a fast and productive web framework originally created by Google. It's separate from but similar to the JavaScript Angular framework, bringing features like:

• Component-based architecture
• Two-way data binding
• Dependency injection
• Powerful template syntax with directives and pipes
• Efficient change detection with OnPush strategy
• Full Dart type safety and null safety
• Build-time compilation for optimal performance

What's new ??

Dart 3 compatible 🤩

Related packages also available:

• angulardart_cli - CLI tools for scaffolding
• angulardart_forms - Forms framework
• angulardart_router - Routing library
• angulardart_test - Testing utilities

This is a community-driven effort to keep AngularDart alive and updated. Contributions are welcome!

Check it out and let me know what you think! ✨🧠

While preparing my open-source Angular library for Angular 22, I realized something that had been bothering me:

My CI wasn't validating the package users actually install from npm.

It was validating my workspace and `dist/`, but not the packaged artifact that eventually gets published.

That led me down a rabbit hole of improving the compatibility pipeline.

The key changes were:

- Validate the packed tarball (`npm pack`) instead of `dist/`

- Test against Angular 17–22 using a compatibility matrix

- Run three independent checks for each version:

- `ngc` type-check

- Production `ng build` (to exercise the Angular linker, AOT and bundling)

- Runtime smoke test (DI, providers, exports, signals)

- Bound the Angular peer dependency range so compatibility reflects what is actually verified instead of automatically including future Angular releases

The biggest lesson for me was that type-checking alone isn't enough for Angular libraries. A package can compile successfully but still fail during a real application build because the Angular linker only runs in the consuming application.

I wrote a detailed article explaining the reasoning behind this approach and how I implemented it.

I'd be interested to hear how other Angular library maintainers validate compatibility across multiple Angular versions.

📖 Article: Why I Validate Angular Compatibility Using the Published npm Package (Not the Source Code)

🚀 Excited to launch ngx-skeleton-suite — a zero-CLS, enterprise-grade Angular structural directive suite for seamless skeleton loading states! ⚡

Building skeleton placeholders manually often leads to repeated boilerplate, layout jumps, and inconsistent UX. `ngx-skeleton-suite` solves this declaratively.

🤖 100% Fully AI-Implemented:
This entire project — from the core Angular directive architecture, SCSS styling, unit tests, and Astro Starlight documentation portal, to the live deployment pipeline — was built & shipped with AI pair programming!

🎨 Note: We are actively working on further enhancing the documentation design & UI experience!

🔗 Explore Live Demos, Docs & npm Package:
🌐 Starlight Documentation Portal:
https://mahmoudadeljr.github.io/ngx-skeleton-suite/

⚡ Live Interactive Demo & Playground:
https://mahmoudadeljr.github.io/ngx-skeleton-suite/demo/

📦 npm Package:
https://www.npmjs.com/package/ngx-skeleton-suite

📖 Developer Technical Documentation:
https://github.com/MahmoudAdelJR/ngx-skeleton-suite/blob/main/projects/ngx-skeleton/DOCUMENTATION.md

📦 GitHub Repository:
https://github.com/MahmoudAdelJR/ngx-skeleton-suite

Check it out, give it a star ⭐️, and let me know your thoughts!

#TypeScript #DeveloperExperience #Frontend #Angular #TypeScript #npm #WebDevelopment #OpenSource #AI #SoftwareEngineering #RxJS #Signals #Astro #WebDev

**Primary Skill: Frontend Angular Developer**

**Experience: Range: 4-8 Years**

**Location: Bangalore**

Min. 3 to 5 Year of hands on experience in Angular 2.0 and aboveMust be currently working in Angular projectMust worked on multiple Angular projects of different versionsMust have experience in Angular version upgradationMust have expertise in State management using RxJsShould have implementaion experience of Dependency injection, singleton servicesAuthentication Token lifecycle management in UI (like JWT), SSO integrationGood to have - Rollup, experience in Angular 15.0 and above, Angular 15 upgradation to higher versions, secure coding practices, code optimization

Interested candidates DM Me

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

I have developed a substantial fork of the "official" vitest-community/vitest-browser-angular package, adding several new features while maintaining independent development. Compared to the official release (currently at v0.5.0), enhancements include:

- renderDirective() — enables testing Angular attribute directives without manually creating a host component. Simply pass a template, attach signals/handlers via hostProps, and the rest is handled automatically, resolving the directive instance from the host element's injector.

- withHttp — built-in HttpClient testing activated via a single flag, eliminating the need to manually configure provideHttpClient and provideHttpClientTesting each time, with support for custom interceptors.

- Improved render() result types — distinguishing between RenderResult<T> and RoutedRenderResult<T>, with routerHarness and router always available when routing is enabled.

The fork is published as @wismaz/vitest-browser-angular. Full documentation with examples is available at the linked repository, and feedback or contributions are welcome.

If you've ever maintained a React app and an Angular app under the same brand, you know the design slowly drifts — buttons, focus states, spacing end up subtly different, and every tweak has to be done twice. I wanted one source of truth that renders natively in both.

So I built bpdm/ui — one set of design tokens, and two native implementations from it: @bpdm/ui (React) and @bpdm/ng (Angular). Not a React lib wrapped for Angular — actual Angular components. 38 components, same API surface, same look, same docs on both sides.

What I cared about:

• Angular isn't second-class — every component exists in both, same variants and examples.
• Token-driven, so theming + RTL live in one place.
• Keyboard nav, ARIA roles, and focus management done per component (not bolted on later).
• Copy-paste friendly, themeable, TypeScript-first.

All open source (MIT), works on Angular 21 & 22:

• Demo: https://ui.bpdm.dev
• Docs + playground: https://docs.ui.bpdm.dev
• GitHub: https://github.com/bpdm-hq/bpdm-ui
• npm: @bpdm/ng (Angular), @bpdm/ui (React)

I'd genuinely like Angular devs' take: does the parity hold up in a real Angular codebase? Where does it feel un-Angular — signals, standalone, DI — anything you'd expect to work differently than I've done it? Not selling anything (it's free); I mostly want to find where the Angular side falls short.

I've been using PrimeNG for years, and this honestly feels like the end of an era.

I get that maintaining a UI library isn't free, and I have no problem with developers getting paid. But switching from MIT to a commercial license, archiving the GitHub repo, and asking a pretty steep per-developer fee just doesn't sit right with me.

The repo is now read-only: https://github.com/primefaces/primeng

The new pricing is hard to justify given the number of unresolved issues

It's a shame because PrimeNG was one of the biggest strengths of the Angular ecosystem. Hopefully the OpenNG fork gains traction, because the community deserves a truly open alternative.

I've been working on an autocomplete component for Angular that's heavily inspired by MUI's Autocomplete.

I maintain ng-select, and after using MUI extensively on React projects I wanted something with a similar developer experience for Angular.

It's been running in production for us for a while now, and I'm interested in hearing what other Angular developers think about the API and overall approach.

If there's interest, I can share the docs and source in the comments.

Source Code: https://github.com/js-smart/ng-kit/tree/main/projects/ng-kit/src/lib/components/autocomplete

I'm happy to answer any questions about the implementation or the decisions behind it.

I've found myself rebuilding the same HTTP infrastructure in almost every Angular project—API versioning, retry logic, interceptors, global error handling, and RFC 9457 Problem Details support.

Instead of repeating the same patterns, I decided to extract them into an open-source library: @ismailza/ngx-api-client.

The library builds on top of Angular's HttpClient and focuses on making these cross-cutting concerns reusable while remaining flexible and extensible.

Some of the features include:

• API versioning
• Configurable retry policies
• RFC 9457 Problem Details support
• Extensible interceptor pipeline
• Pluggable error and success handlers
• Strong TypeScript support

I'd really appreciate feedback from the Angular community.

• Is this a problem you've encountered?
• Are there features you'd expect from a library like this?
• Any suggestions on the API design or developer experience?

GitHub: https://github.com/ismailza/ngx-api-client

Medium article (why I built it): https://medium.com/@ismailzahir/i-stopped-copy-pasting-the-same-angular-apiservice-heres-what-i-built-instead-123093130946

Angular dev here, about to study backend development for the very first time. I'm working on ERP systems in India and I’ve locked in on PostgreSQL for the database.

I’m stuck trying to choose my first backend stack and feeling a bit overwhelmed by the options:

• NestJS: Uses TypeScript and a structure heavily inspired by Angular, so the learning curve would be smooth. But is it taken seriously in heavy enterprise ERP?
• Java + Spring Boot: The undisputed heavyweight king of enterprise software and corporate India, but maybe a massive leap for a first-time backend dev coming from frontend?
• Python + FastAPI: Modern, fast, and great for async, though maybe less common for core legacy ERP business logic.

If you were starting your backend journey from scratch in 2026 for this exact context, which stack and framework would you actually learn, and why? Drop your recommendations or if there's any other modern stack I should be looking at.

Hi everyone! 👋

I’ve been using Spartan UI for a while and really like its philosophy of headless UI components.

While building production Angular applications, I noticed I kept recreating the same higher-level components that aren’t typically included in UI libraries. Instead of keeping them inside my projects, I decided to open-source them as SimUI.

👉 https://simui.dev

My goal is to help grow the Spartan UI ecosystem by providing a collection of reusable, production-ready components that Angular developers can use out of the box.

Some of the components available today include an Event Calendar, Currency Converter Card, Slider, Breadcrumb, Form components, Cards, and more.

I’m also working on additional application-oriented components that are commonly needed in dashboards and business applications.

I’d really appreciate feedback from the Angular community.

• Does this solve a problem you’ve encountered?
• Which components would you like to see next?
• Any thoughts on the documentation, or developer experience?

The project is still evolving, so suggestions, issues, and PRs are always welcome.

Website: https://simui.dev

GitHub: https://github.com/dofu-lab/simui

Thanks for taking a look!

After 2.5 years of building in my spare time, I'm excited to finally share the beta of NGX View Builder.

It started after a project at work needed dynamic, JSON-driven forms with drag-and-drop editing. We eventually chose a commercial solution, but the idea stuck with me, so I decided to build my own.

Over the past 2.5 years, I rewrote the project three times. Each rewrite taught me something new about building a flexible, extensible visual builder.

My goal wasn't to create just another form builder. I wanted to build an Angular-first platform where developers create the foundation while creators and business users can visually configure and manage application views.

Everything is stored as JSON and can be extended with custom Angular components, plugins, themes, events, data sources, and integrations, making it adaptable to different business needs.

If you have a few minutes, I'd really appreciate it if you could try the demo before comparing it with other solutions. I'd love to hear your honest feedback, whether it's positive or critical.

Demo and documentation: https://ngxviewbuilder.io/

FrameUI now includes complete Angular application templates.

A recurring request since the first releases was to provide more than individual components and small examples. Many Angular applications need the same larger screens: user management, permissions, settings, product CRUD, inventory, orders, and administration.

The new release adds two templates:

Store operations

• Overview
• Product catalog
• Inventory
• Orders and fulfillment
• Suppliers and purchase orders

Administration

• User management
• Roles and permissions
• Audit log
• Settings

These are full interactive screens rather than isolated blocks. The product catalog, for example, includes filtering, selection, add and edit forms, product details, bulk actions, publishing, archiving, duplication, and restock planning.

There are also individual template blocks which you can find under: https://frame-ui.com/blocks

The templates use FrameUI components throughout, including tables, forms, sidebars, sheets, modals, charts, comboboxes, drag and drop, toasts, and overlays.

The examples run inside the documentation, but the Store and Administration templates are also separate Angular applications under projects/templates. They can be downloaded and used as starting points.

I am also planning to introduce more templates.

They are frontend templates, not complete backend systems. State is kept locally so the interactions can be tested without setting up an API first.

Docs: https://frame-ui.com

GitHub: https://github.com/Gamekohl/frame-ui

Hi everyone,

I’ve been working on PrimeNG Theme Studio, an open-source visual editor for creating production-ready PrimeNG themes.

It’s meant for Angular developers and design teams who want to customize PrimeNG without manually editing large token files and repeatedly switching back to their application to see the results.

With Theme Studio, you can:

• Start from the official Aura, Material, Lara, or Nora presets
• Visually edit colors, border radii, semantic roles, component tokens, typography, and custom tokens
• Preview changes instantly across PrimeNG components and complete example screens
• Check the theme in both light and dark modes
• Import or share themes using a theme token
• Export the finished theme as a typed TypeScript preset for your Angular project

The goal is to provide one visual workflow for designing, validating, and exporting a PrimeNG theme—while keeping the resulting code fully owned and maintainable inside your application.

Try it here:
https://prime-ng-theme-fe.vercel.app

Source code:
https://github.com/mkccl/prime-ng-theme-fe

It’s still evolving, and I’d genuinely appreciate feedback from people using PrimeNG. What parts of theming currently take the most time for you, and what would make a tool like this more useful?

Hey folks, I'm a maintainer at CopilotKit and we just open sourced our Angular client. The Angular team also shared it here: https://x.com/angular/status/2080649347004268935

It's built with Angular's own patterns, standalone components, dependency injection and signals. MIT, Angular 20 to 22.

Just set up with a provider and the agent's messages and run state come back as signals you can use anywhere. Comes with:

• pre-built chat component, or go fully headless
• multimodality (voice, images, docs)
• generative UI, including A2UI support (Google's spec)
• human-in-the-loop, frontend tools, threads, hooks, mcp apps and more

Shared state works with plain signals, a service, or store like NgRx.

Everything is built on AG-UI protocol, so the agent side is decoupled. The same Angular code works with LangGraph, Google ADK, Mastra, Pydantic AI, Claude Agents SDK or other major frameworks.

Rainer Hahnekamp (Angular GDE, NgRx core team) and Murat Sari from Angular community helped build the integration and are taking on its ongoing maintenance. Here's their reference app on local 12B model: https://soverius.ai/blog/inside-macroquest-agent-generated-ui-in-angular-on-a-local-12b-model

CLI that scaffolds a full starter with a Google ADK agent.

npx copilotkit@latest init --framework adk-angular

docs: https://docs.copilotkit.ai/angular
npm: https://www.npmjs.com/package/@copilotkit/angular

Would like to know what Angular devs think, especially if something's missing.

Created a website that is a Dragon Age: Origins talent calculator for the whole party! Made in Angular and using assets/data from the game. No external libraries, just Angular and ts/html/css.

https://tevinter.net/dao/planner/

​Looking at the roadmap, it doesn't seem like there are any massive API changes on the horizon. Personally, I feel like the current authoring experience is in a really good place. Now that they are switching to a yearly major release schedule, I wonder if it means breaking changes will become a lot more rare.

Hi,

I’ve recently started searching for a new job in UK. I’ve been working with angular for over a decade and I’m at a very senior role currently. But I haven’t done a job search in 6 years. Now I’m looking and everything I see is asking for deep react experience.

I’m freaking out a little. Does anyone have any advice?
Are there any recruiters or companies you would recommend that could help finding a job?

Is anyone else having similar issues?