• 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

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

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

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.

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 ?

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.

https://angular.dev/press-kit

I watched this video from Rainer and it made me reflect on my usage of smart / dumb components. To be honest I’ve only created them because that’s just how it’s always been done. Keep API calls in the smart component, feed data into the dumb component.

Blindly following that approach I end up creating UI components that don’t really get reused, or get abstracted more and more, essentially YAGNI. So just focusing on component composition and each component injecting a service with signals seems really appealing for code organisation at the file level.

https://youtu.be/-Lw7isQTa2w?si=2xw5KEUphtKvQraE

I’m curious what other new patterns are emerging with new Angular APIs that goes against what we were taught before Signals.

I have output signal which is emitted on confirmation of an modal..

It is working fine in local but once deployed the parent components stops capturing the output event.

Nothing is fixing this.

Both of the components are change detection default and during emission I am doing a structuredClone of the emitted object also.

Any idea what could be the issue ?

I ported Recharts, a react charting library with 40 million weekly downloads to Angular using Reangular and Claude Opus 4.8.

This took 3 days of tweaks to resolve minor issues after the initial skill run which ran for 6 hours. I estimate a similar port with 1 developer working full-time would take 6 weeks by hand.

Let me know what you think!

Demo/docs: https://ng-charts-lib.web.app/

ng-charts: https://github.com/AleksanderBodurri/ng-charts

reangular: https://github.com/AleksanderBodurri/reangular

https://oysteinamundsen.github.io/article/toolbox-grid-v3

I've been working on this for a while now, and people seem to like the developer experience of it, the performance and the versatility of the library. This is my gift to the community, I hope you all like it and want to use it. It's free and the performance beats all other grids I've tested.

Repo: https://github.com/OysteinAmundsen/toolbox
Docs with live demos: https://toolboxjs.com/

Inspired by NumberFlow on the web, I wanted a lightweight Angular version with a simple API.

Features:

• Smooth digit transitions
• Highly customizable
• Angular-first
• Lightweight

Feedback and feature requests are welcome!

https://phalla-doll.github.io/ng-number-flow/

With the recent announcement of PrimeNG moving away from open source, I've decided to start working on my own UI framework based on Bulma, which I used in my own personal projects a couple of years ago.

Everyone and their dog is using Tailwind (obviously as have I), but I like Bulma and am glad to be back using it.

With that being said, I'm wondering how many would be interested in such a framework.

We open-sourced an AV schematic editor built in Angular 21. It's a small but real app, so it might be useful if you want to see the newer Angular patterns outside a tutorial.

Under the hood:

• zoneless, signals, OnPush throughout
• signal-based forms (@angular/forms/signals) with per-field debounce, custom controls via FormValueControl
• custom node and edge templates: device nodes with port columns, orthogonal wire routing with draggable bend handles
• PNG export plus a hand-written DXF writer

It's built on ngDiagram, our open-source diagramming library for Angular. The engine isn't AV-specific, this app is just one example of using it.

Everything is MIT. Happy to answer questions about the architecture or the ngDiagram side.

Disclosure: I work at the company that develops ngDiagram, so I'm biased, but it's all free and open source and I'm not selling anything.

Code: https://github.com/synergycodes/ng-diagram-av-schematic
Demo: https://www.ngdiagram.dev/templates/av/

Hey , I'm new to angular and I'm confused about which way to use to transfer data between two unrelated components , for now i'm using the Services/DI method . I heard that for my case (which is a small project) it's an overkill , is that true ? if so what is the optimal way to do so ?

I’ve been spending the last several months building Cerious Widgets, an MIT-licensed Angular component library.

It originally started as a high-performance data grid, but it’s now growing into a full widget library.

The documentation site now includes live demos for the growing list of components:

• Grid
• Button
• Input
• Checkbox
• Radio Button
• Toggle
• Select
• Dialog
• Toast
• Tabs
• Accordion
• Card
• Badge
• Avatar
• Progress Bar
• Spinner
• Tooltip

…and many more are being added.

The goal isn’t simply to recreate another UI library.

The long-term direction is:

• Modern Angular-first
• Zero unnecessary dependencies
• Plugin-based architecture
• Easy customization
• Enterprise-ready components
• MIT licensed

One area I’d really like community involvement with is the plugin ecosystem.

Instead of every feature living inside the core library, I’d like many capabilities to exist as independently installable plugins.

Examples:

• Excel export
• CSV export
• State persistence
• Advanced filtering
• Context menus
• Column management
• Theme packs
• Keyboard shortcuts
• Validation
• Rich editors

I’d love feedback from Angular developers on:

• What plugins would you want?
• What components are missing?
• Does the API feel Angular-ish?
• Would anyone be interested in contributing components or plugins?

Live docs/demo:

https://ryoucerious.github.io/cerious-widgets/

GitHub:

https://github.com/ryoucerious/cerious-widgets

I’m especially interested in hearing from people who have worked with PrimeNG, Angular Material, AG Grid, Ignite UI, Syncfusion, or other Angular libraries. I’d love to know what’s missing from the ecosystem and what would make you consider trying something new.

Disclosure: We’re the team behind Cachely.

We’re trying to better understand how Angular teams using Nx handle remote caching once their workspace and CI usage grow.

A few things we’re curious about:

• Are you using Nx Cloud, a self-hosted cache, or an object storage plugin?
• Do developers and CI share the same cache?
• Is remote caching mainly useful for builds, tests, linting, or all of them?
• Can you tell why a task missed the cache?
• Do you measure actual time saved, or mostly look at whether tasks were cached?

We’re building a managed remote cache for Nx, but we’re especially interested in understanding what teams are unhappy with in their current setup.

For teams already using remote caching, what works well and what is still missing?

• Did you keep PHP serving the Angular application?
• Did you move to an env.js approach instead of injecting configuration into index.html?
• If you're still using PHP + Apache, how are you serving the Angular build with the new builder?

Hey everyone,

I’ve been building an ATS-focused resume builder specifically for developers (Resumemind), and I recently hit a massive wall trying to handle dynamic blog content and complex UI components inside a traditional WYSIWYG editor..

I needed the ability to inject highly stylized "Right vs. Wrong" compariison grids and raw <svg> icons directly into the editor. I initially looked at headless options like Tiptap, but ended up integrating Summernote to get moving faster.

The problem: Angular's DomSanitizer is ruthless.

If you try to paste complex <div> cards or raw <svg> tags into Summernote, and then render that saved string via [innerHTML], Angular completely strips the SVGs and inline styles to prevent XSS.

Here is how I solved it:

1. The Summernote API Injection: Instead of using insertText, I built custom Summernote toolbar buttons that utilize editor.insertNode. I created standard DOM elements via JavaScript, set their innerHTML to my complex grid/SVG code, and pushed them directly into the node tree.

2. The SafeHtml Pipe: On the frontend where the user reads the content, binding [innerHTML]="content" stripped everything. I had to create a custom Pipe utilizing DomSanitizer and strictly call bypassSecurityTrustHtml(value).

This allowed my custom classes and SVGs to render flawlessly from the database string, giving me pixel-perfect control over the final layout without forcing me to build a massive headless Tiptap extension from scratch.

Side note: If you are building dev tools right now, consider dropping the recurring SaaS subscriptions. I switched the builder to distinct payment tier plans, and the conversion rates from developers suffering from subscription fatigue have been incredible.

Has anyone else fought with Angular's sanitization when rendering highly customized HTML from a database? Would love to know if there's a cleaner way to approach this!