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

vitest-unsettled

v0.0.1-alpha.2

Published

Custom Vitest matcher for checking if a Promise is settled (either resolved or rejected).

Downloads

4

Readme

vitest-unsettled

Custom Vitest matcher for checking if a Promise is settled (either resolved or rejected).


If you expect a promise to be settled, you probably assert on its value: expect(p).resolves.toBe(value). But what if you want to assert that a promise is not settled? You can't do that with the built-in matchers.

I've needed this a few times, so I made a custom matcher. Here's how it works.

let resolve = null;
const p = new Promise((r) => {
  resolve = r;
});
expect(p).toBeUnsettled(); // passes
resolve(12);
expect(p).not.toBeUnsettled(); // passes

Installation

# with npm
npm install --save-dev vitest-unsettled
# yarn
yarn add --dev vitest-unsettled
# pnpm
pnpm add -D vitest-unsettled

Setup

Import vitest-unsettled/extend-expect module

The simplest way to use this library is to import vitest-unsettled/extend-expect from your test setup file.

// vitest-setup.js
import "vitest-unsettled/extend-expect";

Extend in test setup file

You can also import the matcher from vitest-unsettled and pass them to Vitest's expect.extend method yourself:

// vitest-setup.js
import { toBeUnsettled } from "vitest-unsettled";
import { extend } from "vitest";
expect.extend({ toBeUnsettled });

With TypeScript

If you imported the vitest-unsettled/extend-expect module, you don't need to do anything else. Make sure your setup file is included in your tsconfig.json.

If you're extending the matchers yourself, you may need to add a type declaration to your test setup file:

import type { UnsettledMatcher } from "vitest-unsettled";
declare module "vitest" {
  export interface Assertion extends UnsettledMatcher {}
  export interface AsymmetricMatchersContaining extends UnsettledMatcher {}
}

Further reading:

Acknowledgements

I leaned heavily on the chaance/vitest-axe project to see how to structure this project and README.