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

purify-asserts

v0.3.2

Published

Jest expectations for the purify-ts library

Downloads

44

Readme

Version Downloads License GitHub issues GitHub Repo stars

Jest expectations for the purify-ts library

Motivation

Purify is an excellent library for functional TypeScript applications, but its algebraic data types are not so obvious to test. Specifically, the following convention examples are not easy to remember in the scope of unit tests.

expect(maybe.isJust()).toBe(true);
expect(maybe.isNothing()).toBe(true);
expect(maybe.extract()).toEqual("value");

expect(either.isLeft()).toBe(false);
expect(either.isRight()).toBe(true);
expect(either.extract()).toEqual("is this success or error?");

Wouldn't it be more satisfying to assert expectations with the same domain language Purify speaks of? I think so.

expect(possiblyNullableMaybe).toBeJust();
expect(justOrNothing).toBeNothing();
expect(justOrNothing).toHaveJustValue(1);

Install

npm install --save-dev purify-asserts
yarn add --dev purify-asserts

Usage

Using matchers requires to use the expect.extend() method of Jest. These should be imported and used at the beginning of your test suite above the first describe() block.

Import all of the matchers:

import * as matchers from "purify-asserts";

expect.extend(matchers);

Import only selected matchers:

import { toBeJust, toBeNothing } from "purify-asserts";

expect.extend({ toBeJust, toBeNothing });

Examples

  • Examples for using Maybe<T> matchers
  • Examples for using Either<L, R> matchers (work in progress)
  • Examples for using MaybeAsync<T> matchers (work in progress)
  • Examples for using EitherAsync<L, R> matchers (work in progress)
  • Examples for using Tuple<F, S> matchers (work in progress)
  • Examples for using NonEmptyList<T> matchers (work in progress)
  • Examples for using Codec<T> matchers (work in progress)

Author

👤 Niko Heikkilä [email protected]

🤝 Contributing

Contributions, issues and feature requests are welcome!

Feel free to check issues page.

Show your support

Give a ⭐️ if this project helped you!


This README was generated with ❤️ by readme-md-generator