An Angular HTTP interceptor that automatically shows customizable spinners during HTTP requests.
ng-http-loader is an Angular library that automatically displays loading spinners during HTTP requests. It intercepts HTTP calls made via Angular's HttpClient and shows a visual indicator until the request completes, improving user experience by providing feedback during data fetching.
Angular developers building applications with HTTP data fetching who need a simple, automated way to show loading states.
Developers choose ng-http-loader because it eliminates manual spinner management, offers extensive customization options, and integrates seamlessly with Angular's HttpClient with minimal configuration.
:dango: Smart angular HTTP interceptor - Intercepts automagically HTTP requests and shows a spinkit spinner / loader / progress bar
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates seamlessly with Angular's HttpClient to automatically show spinners during all HTTP requests without manual setup, as demonstrated in the basic usage example.
Allows customization of spinner types, timing, colors, and even replacement with custom components, with detailed configuration attributes like debounceDelay and entryComponent.
Enables exclusion of specific requests by URL patterns, HTTP methods, or headers using filteredUrlPatterns, filteredMethods, and filteredHeaders, providing precise control.
Includes SpinnerVisibilityService for programmatically showing and hiding spinners, useful for complex operations outside HTTP requests, as outlined in the manual control section.
Only works with Angular's HttpClient, making it incompatible with other HTTP clients or direct fetch API usage, as stated in the requirements.
Limited to HTTP requests, so additional solutions are needed for loading states during WebSocket communications or other async events, which isn't addressed.
Bundles multiple SpinKit spinner components by default, which can unnecessarily increase application size if custom spinners are preferred or only one type is used.