npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

angular-http-loader

v0.1.8

Published

AngularJS HTTP loader

Downloads

12

Readme

HTTP Loader

Angular component which monitors HTTP requests and shows a custom loader element when calls start and hides it when they complete.

Maintainer: Mauro Gadaleta <[email protected]>

Demo

http://wongatech.github.io/angular-http-loader/

Travis Status

Build Status

Installation

NPM:

npm install --save angular-http-loader

Usage

Load angular-http-loader.min.js:

<script src="path/to/angular-http-loader.min.js"></script>

Add the ng.httpLoader module as a dependency in your application:

angular.module('demo', ['ng.httpLoader'])

Whitelist the external domains that you want the loader to show for:

.config([
  'httpMethodInterceptorProvider',
  function (httpMethodInterceptorProvider) {
    httpMethodInterceptorProvider.whitelistDomain('github.com');
    httpMethodInterceptorProvider.whitelistDomain('twitter.com');
    // ...
  }
])

You can whitelist requests to the local server:

.config([
  'httpMethodInterceptorProvider',
  function (httpMethodInterceptorProvider) {
    // ...
    httpMethodInterceptorProvider.whitelistLocalRequests();
    // ...
  }
])

Add an HTML element with the ng-http-loader directive. This will be displayed while requests are pending:

<div ng-http-loader template="example/loader.tpl.html"></div>

Different loaders for different methods

Monitor only GET requests:

<div ng-http-loader methods="GET" template="example/loader.tpl.html"></div>

Monitor POST and PUT requests:

<div ng-http-loader methods="['POST', 'PUT']" template="example/loader.tpl.html"></div>

Adding a title to your template

HTTP loader allows you to pass a title to your template:

<div ng-http-loader title="example" methods="GET" template="example/loader.tpl.html"></div>

And use that in your template:

<span>Loader for {{title}}</span>

Minimum time to live

HTTP loader allows you to pass a ttl in seconds to your template. This tells the loader to be visible at least for the given amount of time, i.e.

<div ng-http-loader ttl="2" methods="GET" template="example/loader.tpl.html"></div>

The loader should be now visible at least 2 seconds, independent of the total http request(s) dispatched. Should the total amount of time of the request(s) be larger than the ttl, the loader will dismiss when the last http request is done.

Contributing

We :heart: pull requests!

To contribute:

  • Fork the repo
  • Run npm install
  • Run grunt workflow:dev to watch for changes, lint, build and run tests as you're working
  • Write your unit tests for your change
  • Run grunt package to update the distribution files
  • Check that the demo app works (acceptance tests to be added)
  • Update README.md and, if necessary, the demo page