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

imagineeasy-angular-http-watcher

v2.2.1

Published

Angular HTTP Interceptor to act on failed HTTP request and replay them on a given point in the future

Downloads

5

Readme

imagineasy-angular-http-watcher

HTTP Watcher Module

This is initially based on the concept described in Authentication in AngularJS (or similar) based application and - https://github.com/witoldsz/angular-http-auth

But we extended it to be a general notification (and buffering) system for all http requests an angular app does via the $http service.

Usage

  • Install via npm: npm install --save imagineeasy-angular-http-watcher
  • Include as a dependency in your app: angular.module('myApp', ['http-watch'])

Manual

This module installs $http interceptor and provides the httpWatcher service.

The $http interceptor does the following:

If an HTTP request fails, the event network:http-error is broadcasted with the configuration object (this is the requested URL, payload and parameters) of said request. If the HTTP Error-Code is in the bufferList, it will be buffered and can be replayed at any given time using the continue() method of the httpWatcher service.

You are responsible to invoke this method after you handled the error. Example:

/** @ngInject */
return function(httpWatcher) {
    httpWatcher.continue();
};

Ignoring the interceptor

Sometimes you might not want the interceptor to intercept a request even if one returns a http error code. In a case like this you can add ignoreHttpWatcher: true to the request config.

Disabling the buffering of requests

If needed, you can also add saveOnHttpError: false|true to the request config to specifically say you want to allow/disallow buffering a request regardless of the response code.

Specifing custom default values

If you need a custom event name oder you want to change the defaults which http statuses are saved and which not in your app, you can do this easily by using the httpWatcherConfig provider in your app. On initialization this will be used by the interceptor.

Currently support are these values, shown with their default values, all optional:

angular.module('your-app', []).config(function(httpWatcherConfigProvider) {
  httpWatcherConfigProvider.setConfig({
    eventNames: {
      error: 'network:http-error',
      continue: 'network:continue',
      reject: 'network:reject'
    },
    status: {
      0: true,
      408: true,
      401: true
    }
  });
});