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

ng-promise-queue

v1.0.4

Published

An angular module that can execute a queue of promises, returning the resolved/rejected results of the promises when the queue has completed.

Downloads

4

Readme

Demo

Install

$ yarn add ng-promise-queue

Or

$ npm install ng-promise-queue

Add To Your Angular App

Supports usage of modules or require.js. Expects angular to be available globally, so if using a module bundler (webpack) be sure your setup supports this.

import ngPromiseQueue from 'ng-promise-queue' // or
const ngPromiseQueue = require('ng-promise-queue')

// Only the modules .name property is exported

angular.module('yourApp', [ngPromiseQueue])

Or more more traditionally just reference the file from a script tag

<script src="node_modules/ng-promise-queue/dist/ngPromiseQueue.min.js"></script>

angular.module('yourApp', ['ngPromiseQueue']) // just reference the module's name as string

Use

ngPromiseQueue exposes a factory that you can inject.

function SomeController (promiseQueue) {
  promiseQueue.run()
}

.run() is the only method exposed from the promiseQueue factory. It takes a simple configuration object as its only argument

function SomeController (promiseQueue, $timeout) {

  // must be an array, can contain whatever data your callback needs to operate on
  const tasks = [1,2,3]

  // The number of tasks you'd like to run at the same time
  const maxConcurrent = 2 // will default to 1 if not passed

  // A callback function that returns a promise and takes a task as an argument
  const promiseCb = function (task) {
      return $timeout(() => {
        return task
      }, 3000)
  }

  const config = {
        tasks,
        maxConcurrent,
        promiseCb,
    }

  promiseQueue.run(config)
}

promiseQueue.run() returns a promise, the promise will resolve when all tasks are complete.

function SomeController (promiseQueue) {
  promiseQueue.run(config)
    // Even if the promiseCb is rejected, the outer promiseQueue promise will still continue.
    .then(console.log)
    // If the promiseCb raises an exception the queue will be rejected and the exception caught here
    .catch(console.error)
}

Results are returned as an array, and in the order that they resolved or were rejected

function SomeController (promiseQueue) {
  promiseQueue.run(config)
    .then(results => {
      const failed = results.filter(task => task.response.code === 500)
      const success = results.filter(task => task.response.code === 200)
    })
}

Development

Install dependencies

$ yarn

Run tests

$ yarn test

Build

$ yarn build