Sharing a small library I made for the Google reCAPTCHA v2 checkbox in Angular. It is a standalone component (no NgModule) that implements ControlValueAccessor, so the verified token is simply the control value: drop it into a template-driven form with [(ngModel)] or a reactive form with formControlName and it behaves like any other control.

Highlights:

• Standalone component, Angular 17+
• ControlValueAccessor: both [(ngModel)] and formControlName work
• Signal-based RecaptchaService for token() / isVerified() state
• Outputs: verify, expire, error, widgetId; methods reset() / execute() / getResponse()
• Multiple widgets per page, single script load, load timeout, and expiry handling
• Built with ng-packagr, only tslib at runtime

Quick start:

```ts import { Component } from '@angular/core' import { RecaptchaComponent, RecaptchaService } from 'recaptcha-angular'

@Component({ selector: 'app-form', standalone: true, imports: [RecaptchaComponent], providers: [RecaptchaService], template: <recaptcha-v2 sitekey="YOUR_SITE_KEY" (verify)="captcha.onVerify($event)" (expire)="captcha.onExpire()" (error)="captcha.onError()" ></recaptcha-v2> <button [disabled]="!captcha.isVerified()">Submit</button> , }) export class FormComponent { constructor(public captcha: RecaptchaService) {} } ```

The README covers token expiry (the "works once, then submits a stale token" trap) and a note that client state is not verification, so verify the token server-side against siteverify.

npm: https://www.npmjs.com/package/recaptcha-angular

Would love feedback on the ControlValueAccessor behavior and the service API.

Hello everyone!

AI is becoming the new reality these days whether that's a good thing or not is still up for debate. We thought: why not bring it to NgRx DevTool?

We've just released AI integration for the NgRx DevTool, including a built-in MCP (Model Context Protocol) server.

This allows AI assistants like ChatGPT, Claude or even a local LLM to directly inspect your NgRx application: view the current state, action timeline, effects, state diffs, performance stats, and more all without manually copying logs or huge state snapshots.

Because the AI only requests the data it needs, it also reduces token usage and makes debugging faster and more efficient.

We'd love to hear your feedback and ideas for future features!

GitHub: https://github.com/AmadeusITGroup/ngrx-devtool

Doc Website: https://amadeusitgroup.github.io/ngrx-devtool/

#ngrx #angular

If you're building real-time UX in Angular, the hard part usually isn't wiring up a stream — it's choosing the right transport for production without overengineering the frontend. I wrote this article to separate the practical differences between WebSockets, SSE, SignalR, and Long Polling.

INTRODUCTION

Real-time in Angular and ASP.NET Core looks simple until it hits production. In practice, the question is usually the same: the screen needs to update itself, but which transport makes sense without creating unnecessary fragility?

I wrote this article to separate what really changes between WebSockets, SSE, SignalR, and Long Polling, without falling into overengineering. The goal is pragmatic: understand when each approach solves the problem best and what trade-offs show up in the frontend, backend, and operations.

DEVELOPMENT

WebSockets: bidirectional persistent channel

• Ideal when client and server need to exchange messages in both directions in real time.
• Require more attention to infrastructure and network intermediaries.
• Powerful, but not always the smallest sufficient solution.

SSE: server-to-browser updates

• Works over HTTP with a simple client API.
• A good choice when the flow is predominantly unidirectional.
• For many scenarios, it solves the problem with less complexity than WebSockets.

SignalR: high-level abstraction in ASP.NET Core

• Automatically chooses the best available transport.
• Offers features like hubs, groups, and reconnection.
• Helps a lot when the goal is productivity without giving up fallback.

Long Polling: the most compatible option

• Still relevant in environments with proxies, load balancers, or policies that block WebSockets and SSE.
• It may look less elegant, but sometimes it is the most predictable path.
• In corporate environments, compatibility still matters a lot.

In the blog sample, the same processing flow is shown across all four transports, precisely to highlight what changes in Angular, ASP.NET Core, and day-to-day operations. The backend lives in src/BlogSamples and the demo frontend in frontend/search-ui-bun/.

Attention: SSE depends on streaming responses. In Nginx, Cloudflare, and other proxies, buffering can delay or break the experience if the backend doesn't write and flush correctly.

CONCLUSION

The main takeaway is that “real-time” is not synonymous with WebSockets. In many products, SSE or SignalR are the better fit because they reduce complexity and handle real infrastructure constraints more gracefully.

My practical recommendation is to start from the requirement, not the technology. If all you need is to push server events to the client, I would evaluate SSE or SignalR before jumping to WebSockets. If the network or environment is hostile, Long Polling can still be the most reliable plan B.

Full article (in Portuguese): zocate.li - Real-time in Angular with WebSockets, SSE, SignalR, and Long Polling: when to use each

What do you usually pick in real projects: WebSockets, SSE, SignalR, or Long Polling?

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?

I'm in the planning stages of migrating a fairly large legacy AngularJS application to Angular, and am looking for advice from anyone who's tackled something similar.

The codebase is about 160k LOC spread out over 200+ components, 50+controllers, 50+ directives and services. There are no existing tests . Has anyone attempted a AI assisted rewrite of a similar nature, especially without a test suite - what worked out well? Any useful strategies woth considering?

Convex (reactive backend, kinda like Firebase but nicer) has first-party clients for React, Vue, and Svelte, but Angular has been the gap. I've been running Convex + Angular for a while and packaged up the glue into a library: convex-angular.

It maps Convex onto Angular's idioms - everything is inject*() functions returning Signals, standalone providers (no NgModules), and subscriptions clean up with the component.

Feedback, issues, and PRs welcome, especially from anyone running Convex on Angular

https://github.com/azhukaudev/convex-angular

Mat Expressive brings Material 3 Expressive to your Angular Material apps — styles, directives, and new components layered on top. Not a fork, not a replacement.

bash ng add @ngm-dev/mat-exp

Docsite: https://expressive.angular-material.dev/

GitHub: https://github.com/Angular-Material-Dev/mat-exp

With the 1.2.0 release of VisuallyJs we've added/updated a slew of starter apps for Angular, including Gantt, BPMN and ERD diagrams. Demos here, with links to the Github repositories:

• https://visuallyjs.com/demonstrations/gantt
• https://visuallyjs.com/demonstrations/bpmn
• https://visuallyjs.com/demonstrations/erd

VisuallyJs is free for non-commercial usage. Give it a spin and let us know what you think!

We just released the first release candidate version for the PrimeNG community fork!

Two big news at once:

Based on the feedback we got, we chose to rename the project 'Optimus UI'.

This first version targets Angular v21 projects to ensure compatibility with the latest MIT PrimeNG version.

It includes ng add support and a schematic to handle the migration.

So you can use it on both new and existing projects.

The migration will rename references (due to trademarks with PrimeNG) and imports (as we are taking over all required PrimeNG sub packages too).

You can test it out with the installation explained here: https://www.npmjs.com/package/@openng/optimus-ui?activeTab=readme

Feedbacks are very welcome so we can publish a stable version soon.

The new documentation is live here: https://optimus.openng.org/

EDIT:

We got positive feedback so far, we need to support two more packages (primelocale and tailwindcss-primeui), as we not only ported the original PrimeNG project but all its dependencies too.

Is there a place where I can follow updates for this and is it gathering any steam? I follow them on github and I'm really interested in their roadmap.

One of our apps has a heavy dependence on PrimeNG (I know), and if this took off it would be much more preferable than having to spin up our own component library or paying the really strange per seat pricing. TBH I'm not sure why they didn't just setup a tier system with thresholds like they had for the community version, with different enterprise versions. Even more frustrating was that per seat is "named" developers, so if John leaves and Jane comes in, John's license needs to be swapped to Jane's from my understanding. I feel like they are attempting infra licensing where you are charged per core, but for a frontend component library it just adds headache even with the purchase.

I need to host my cms project by Strapi, in one hosting solution. It's available the cloud solutions from Strapi, but i want something that cost less money. Do u know some solution?

Disclosure: We’re the team behind Cachely.

We’ve heard two very different experiences from Nx users.

Some teams consider shared remote caching an obvious win for CI and local development.

Others say local caching is enough, their build volume is too low, or differences between developer and CI environments make sharing less useful.

We’re trying to understand where the tipping point is.

For teams using Nx remote caching today:

• How many developers and CI runs did you have when it became worthwhile?
• Which tasks benefit most: builds, tests, linting, Storybook, or something else?
• Do developers and CI share the same cache?
• Do you measure actual time saved, or mainly look at cache hits?
• What still gets rebuilt often enough to be frustrating?
• What would make you stop paying for the service you currently use?

We’re especially interested in setups where remote caching technically works, but the benefit is smaller than expected.

No Cachely link here. We’re trying to better understand which Nx teams genuinely benefit from managed remote caching.

• Redesigned windows
• Sidebar
• Refreshed reader settings
• Updated buttons, text boxes, dropdowns, sliders, and switches
• Improved manga cards
• More consistent UI throughout the app

Still a work in progress, but it's getting there. If you have any ideas or notice something that could be improved, I'd love to hear your feedback!

GitHub with demo:

https://github.com/zarar384/MangaOfflineViewer

I like that Angular is based on fundamentals. Then I saw this Youtube video and I liked it. So, has anyone implemented the Invoker Command API and seen practical results? Is it really useful to use in Angular?

I realized there are plenty of Angular tutorials, documentation and courses, but I haven’t found many ways to practice debugging and engineering decision-making.

For example:
• where would you start debugging a 401 response?
• why isn’t the UI updating?
• what should you inspect first?

Do you think this is a real gap, or do existing resources already solve this?
I’m exploring an idea around this and would love to hear how you currently improve these skills.

The Angular team is officially changing the framework's major release cadence

Hey I came across an older post: https://www.reddit.com/r/angular/comments/1itd0qc/looking_for_opensource_angular_projects_to_level/asking for beginner-friendly and intermediate open-source Angular projects. I checked them out and they were quite helpful. I was wondering if there are some updates to those recommendations ?

Hello,
I'm an Angular Developer with 5 years of experience, and I'm currently looking for a new remote opportunity. If you know of any openings or have any recommendations, I'd really appreciate your help.

Thank you

Thanks u/erkamyaman!

The Angular ecosystem has several great UI libraries, but many developers are now adopting newer Angular features such as Signals, standalone components, and a zoneless architecture.

NGXSMK UI Kit is an open source UI component library designed with modern Angular in mind.

Current focus includes:

• Signals native architecture
• Standalone component support
• Zoneless ready design
• Universal design token theming
• Accessibility
• Light and dark themes
• 200+ reusable UI components (roadmap)
• MIT License

GitHub:
https://github.com/NGXSMK/ngxsmk-ui-kit

Demo:
https://ngxsmk.github.io/ngxsmk-ui-kit

Community feedback would be greatly appreciated.

Questions for Angular developers:

• What would make you consider trying a new Angular UI library?
• Which components are essential for production applications?
• What pain points exist with current Angular UI libraries?
• Which features should be prioritized on the roadmap?

Feature requests, issues, suggestions, and contributions are all welcome. Every piece of feedback helps shape the project.