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

@knowdev/jest

v1.1.0

Published

Jest extensions

Downloads

2

Readme

KnowDev Jest Extensions 🃏

📋 Usage

npm install --save @knowdev/jest

jest.config.js

module.exports = {
  setupFilesAfterEnv: ["jest-extended", "@knowdev/jest"],
};

📖 Reference

toBeAsyncIterator()

Checks that a special symbol, subject[Symbol.asyncIterator], exists and is a function. Does not exercise iterator

expect(subject).toBeAsyncIterator();

toBeClass()

Attempts to instantiate subject

expect(subject).toBeClass();

toBeCalledWithInitialParams()

Unlike toHaveBeenCalledWith(), which matches the entire set of parameters, toBeCalledWithInitialParams() only matches the first n parameters. E.g., if you want to test only the first parameter

# Passes:
mockFunction(1, 2, 3);
expect(mockFunction).toBeCalledWithInitialParams(1, 2);

# Fails:
mockFunction(1);
expect(mockFunction).toBeCalledWithInitialParams(1, 2);

toBeProjectError()

Checks that the subject is a ProjectError instance

expect(error).toBeProjectError();

toThrowProjectError(), toThrowProjectErrorAsync()

Checks that the thrown error is an instance of ProjectError. Can be called with any of the following matchers, which much all match:

  • String (matches as a substring)
  • RegExp
  • ProjectError class

Strings and RegExps are matched against the error title or detail fields. ProjectError classes compare the title and status fields but not detail.

expect(() => functionCall(...params)).toThrowProjectError();

expect(() => functionCall(...params)).toThrowProjectError(InternalError, "Internal Application", /internal application/i);

🚀 Deployment

npm run publish

📝 Changelog

  • 1.1.0: adds toBeProjectError()
  • 1.0.2: Split toThrowProjectError() into sync and totoThrowProjectErrorAsync() versions
  • 1.0.1: toThrowProjectError() supports async functions
  • 1.0.0: arbitrary starting point
  • 0.4.0: adds toThrowProjectError() (unpublished)
  • 0.3.0: adds toBeAsyncIterator()
  • 0.2.0: adds toBeCalledWithInitialParams()
  • 0.1.0: adds toBeClass()

🛣 Roadmap

N/A

Wishlist 🌠

  • toMatchJsonApiErrorSchema()

📜 License

All rights reserved. Safe for use around pets.