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

keepbreak

v0.1.0

Published

Don't resolve your promises. Keep them.

Downloads

1

Readme

keepbreak

It's never made sense to me that JavaScript promises are resolved or rejected. In the real world, we don't resolve or reject promises. We keep (or break) them!

This package brings that reality to the world of JavaScript.

Installation

npm i -D keepbreak

# OR

yarn add -D keepbreak

Usage

Don't.

Ok seriously though

You shouldn't use this package, it's plainly stupid. But if you really want to, here's how:

install()

Preserves 'normal' JavaScript behaviour, but adds extra methods to Promise.

const keepbreak = require('keepbreak');

keepbreak.install();

Promise.keep().then(() => {
  console.log('Hey this works now!')
});

Promise.break().catch(() => {
  console.log('So does this!');
});

Promise.resolve().then(() => {
  console.log('This still works.');
});

Promise.reject().catch(() => {
  console.log('As does this.');
});

installStrict()

Adds the new methods but also deletes the default ones, ensuring that no one ever forgets to keep instead of resolve.

const keepbreak = require('keepbreak');

keepbreak.installStrict();

Promise.keep().then(() => {
  return Promise.resolve();
  // -> Uncaught TypeError: Promise.resolve is not a function
});

Promise.break().then(
  () => {},
  () => {
    return Promise.reject();
    // -> Uncaught TypeError: Promise.reject is not a function
  }
)

For added fun, when constructing a new Promise(), keepbreak will ensure that the executor function's parameters are named keep and braek (note the spelling - we can't call it break because that's a reserved word 😔):

const keepbreak = require('keepbreak');

keepbreak.installStrict();

// Ok (can be arrow- or non-arrow functions, anonymous or named):
new Promise((keep, braek) => { keep(); });
new Promise((keep) => { keep(); });
new Promise((_, braek) => { braek(); });

// Not ok:
new Promise((resolve, reject) => { resolve() });
// -> Uncaught Error: Parameters to `new Promise()` must be called 'keep' and 'braek'

In case it's not clear, this mutates the global Promise object, so if anything (your own code, your dependencies, or even Node.js builtins) tries to Promise.resolve(), it will explode. So you should definitely use this in production.

uninstall()

Puts things back to so-called 'normal'. Boooriiing!