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

bluster

v2.0.0

Published

Test both promises and callbacks in one go

Downloads

73

Readme

Test both promises and callbacks in one go.

Rationale

If your function supports both promise-style and continuation-passing-style asynchronous calls, bluster will cut your tests in half.

Take this function for example:

function getResource(name: string): Promise<Resource>;
function getResource(name: string, callback: (error: Error, resource: Resource) => void): void;

(TypeScript types and overloading for clarity.)

Developers can call this function promise-style and continuation-passing-style (also known as callback-style). Whichever they prefer and fits the rest of the project. Cool! But how would you go about testing this? bluster lets you test both branches at the cost of one.

Jest users, see jest-bluster.

Installation

Install bluster using npm or Yarn and import the function in your tests:

import bluster from 'bluster';

Usage

Wrap your function using bluster:

const resource = await bluster(getResource)('example.gz');
// Perform assertions on the resource.

This line throws an error if:

  • either const promise = getResource('example.gz') or getResource('example.gz', callback) produces an error, or
  • const promise = getResource('example.gz') and getResource('example.gz', callback) produce different values.

If no error is thrown, you can rest assured that the function behaves the same when used promise-style as it does when used continuation-passing-style. As normal, you will now determine whether the resource constant is accurate.

License (X11/MIT)

Copyright (c) 2019, 2023 Pimm "de Chinchilla" Hogeling

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

The Software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. in no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the Software or the use or other dealings in the Software.