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?

I’ve just published a small npm package called  @modyra/core  that came out of a very specific pain: handling “slightly complex” app state in frontend projects without ending up with a mess of context, custom hooks and scattered stores.

The focus of the package is:
• Minimal API, all in TypeScript, no hidden magic
• No heavy runtime: just tools to model the core of your app as a set of state modules
• Designed to plug into React/Angular/vanilla JS without forcing you to rewrite everything

The idea is to treat your app’s domain as a set of “core units” with clear responsibilities: each unit exposes state, actions and rules, and the rest of the app simply consumes them. It came out of a few projects where Redux/Zustand/signals etc. were fine, but started to feel either too verbose or not very close to the actual business domain.

You can find the package on npm here:
 @modyra/core  → https://www.npmjs.com/package/@modyra/core`

If you feel like taking a look and tearing it apart, feedback (including harsh ones) is very welcome: naming, API design, examples – everything is still fresh enough to change. And if you think the approach is worth exploring, a star on GitHub would really help me keep pushing the project forward.

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?

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

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 ?

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.

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/