A collection of TypeScript libraries that mimic Angular's APIs for reactive HTTP clients and decorators.
Ngify is a collection of TypeScript libraries that emulate Angular's APIs, particularly its reactive HTTP client and decorator patterns. It allows developers to use Angular-like syntax and reactive programming approaches in non-Angular projects, such as WeChat mini-programs, Taro, or Uni app environments. The project solves the problem of framework lock-in by providing familiar Angular patterns across different JavaScript ecosystems.
Frontend developers working with TypeScript who are familiar with Angular's APIs but need to use them in other frameworks like WeChat mini-programs, Taro, or Uni app. It's also suitable for teams transitioning from Angular to other platforms who want to maintain consistent coding patterns.
Developers choose Ngify because it provides a seamless way to apply Angular's well-designed reactive HTTP client and decorator patterns in environments where Angular isn't available. Its modular architecture and platform-specific adapters offer flexibility without sacrificing the developer experience Angular users appreciate.
Pretend to be using Angular
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Each functionality is available as a separate npm package, such as @ngify/http or @ngify/at, allowing developers to pick only what they need and reduce bundle size.
The reactive HTTP client replicates @angular/common/http with observables and interceptors, providing a familiar interface for developers transitioning from Angular.
Dedicated adapters for WeChat, Taro, and Uni app ensure compatibility in these niche environments, as highlighted in the packages list.
Designed for TypeScript, it supports decorators and type safety, enhancing development experience in non-Angular TypeScript projects.
The @ngify/at library is labeled experimental in the README, indicating potential instability and breaking changes that may not be suitable for production.
Adapters are only available for WeChat, Taro, and Uni app, making it less useful for other ecosystems like React Native or vanilla JavaScript projects.
Full API definitions are on an external site, which might be less accessible or integrated than in-repo docs, as noted in the README's API section.