Partnership Proposal: ngx-feature-proxy - ModernAngular Integration for Unleash Platform

[zenkiet]

Hello Unleash community!

I've developed ngx-feature-proxy, an open-source Angular library for seamless and type-safe Unleash integration. I'm seeking your feedback and potential collaboration.

🔗 Project Links

• Repository: https://github.com/zenkiet/ngx-feature-proxy

• NPM: https://www.npmjs.com/package/ngx-feature-proxy

• Demo: https://youtu.be/K-2rLjG7qyQ

🎯 Purpose
To provide Angular developers with a robust, type-safe, signal-based, and production-ready integration for Unleash feature flags.

✨ Key Features

• Angular 16+ (signals, standalone components)
• Type-safe directives and route guards
• Minimal setup, built-in debugging
• Comprehensive documentation

🤝 Collaboration Interest

• I'd appreciate:
• Technical review and feedback.
• Consideration for community showcase/official resources.

Guidance on best practices alignment.

💬 Seeking
Your thoughts on the library's architecture, alignment with Unleash principles, potential improvements, and collaboration opportunities.

Thank you!

Maintained by @zenkiet | kietgolx65234@gmail.com

[gastonfournier]

Thank you for putting this Angular client together. After a thorough review we’ve decided not to move forward with the contribution, and I wanted to share the main reasons why.
The library introduces “advanced mode” helpers that accept feature expressions (features(), eval(), the directive and guard integrations). Internally those strings are expanded and executed with new Function, with complex regular-expression checks layered on top. That combination makes the surface area hard to reason about, increases the security risk, and adds maintenance cost we’re not comfortable taking on.
The expression-based APIs fundamentally change the expected usage patterns of the proxy/Frontend API client. We haven’t seen product demand for evaluating multiple flags through Boolean expressions, so we’d be shipping and supporting behaviour that oversteps what the upstream SDK offers.
Some of the lower-level details don’t align with the reference implementation—for example, feature() caches toggle results once and never refreshes them after updates, and the context type omits standard fields such as appName and currentTime. Those gaps would require a redesign to keep the client’s state in sync with Unleash.
Because the divergence is concentrated in core behaviours, we don’t see a path to accept this without major rewrites. There are already two community Angular SDKs (angular-unleash-proxy- client and ngx-unleash-proxy-client) that stay closer to the reference client; if you’re interested in continuing the work, contributing improvements there—or using them as prior art for a thinner wrapper—would likely be the most productive route. Also, would like to know what's the value added of the new implementation you're proposing and how it differs from the existing ones.
We truly appreciate the effort and your interest in extending the ecosystem. Please keep in touch, and don’t hesitate to reach out if you explore a more reference-aligned approach.
Thanks again!