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

broken-promises-aplus

v1.0.0

Published

A compliant implementation of the Promises/A+ specification which doesn't actually work

Downloads

20

Readme

broken-promises-aplus

An implementation of the Promises/A+ specification which, although it passes the Compliance Test Suite, does not work.

Installation

npm install broken-promises-aplus

Testing

npm test

This runs the full Promises/A+ Compliance Test Suite.

Usage

import Promise from 'broken-promises-aplus'

const get = url => new Promise((resolve, reject) => {
  var xhr = new XMLHttpRequest()
  xhr.addEventListener("error", reject)
  xhr.addEventListener("load", resolve)
  xhr.open("GET", url)
  xhr.send()
})

get("https://github.com")
  .then(JSON.parse)
  .then(console.log)

The above code causes a puzzling exception to be thrown. No HTTP request is sent.

Why?

The purpose of this library is to demonstrate a point about Test-Driven Development:

If the people writing the tests and the people developing the software have opposing goals, then it must be impossible to programmatically distinguish a testing scenario from normal use.

A prominent recent example of this not happening when it should have happened is the Volkswagen emissions scandal. Here, the developers of the VW engine control unit programmed it to display unusual low-emissions behaviour when it (the ECU) detected that an emissions test was in progress, and to display much improved performance (at the cost of emissions) the rest of the time.

In the same way, broken-promises-aplus is programmed to behave like a conforming Promises/A+ implementation when it detects that the Compliance Test Suite is in progress, and to display other behaviour at all other times.

How can I help?

There are two major ways you can help to improve this library:

  • Improve the heuristics by which the library detects that a Compliance Test Suite is in progress
  • Make suggestions and pull requests for more interesting behaviour for when no Compliance Test Suite is in progress (nothing destructive, please)