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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@praha/byethrow-testing

v0.11.1

Published

Custom test matchers for asserting @praha/byethrow Result types.

Readme

@praha/byethrow-testing 👋

npm version npm download license Github

Custom test matchers for asserting @praha/byethrow Result types.

🚀 Installation

npm install @praha/byethrow-testing

📚 Usage

Setup

Jest

Add the following to your Jest setup file (e.g. jest.setup.ts):

// jest.setup.ts
import { expect } from '@jest/globals';
import { resultMatchers } from '@praha/byethrow-testing';

import type { ResultMatchers } from '@praha/byethrow-testing';

declare module 'expect' {
  interface Matchers<R> extends ResultMatchers<R> {}
}

expect.extend(resultMatchers);

Then reference the setup file in your Jest config:

// jest.config.ts
export default {
  setupFilesAfterEnv: ['./jest.setup.ts'],
};

Vitest

Add the following to your Vitest setup file (e.g. vitest.setup.ts):

// vitest.setup.ts
import { resultMatchers } from '@praha/byethrow-testing';
import { expect } from 'vitest';

import type { ResultMatchers } from '@praha/byethrow-testing';

declare module 'vitest' {
  interface Matchers<T> extends ResultMatchers<T> {}
}

expect.extend(resultMatchers);

Then reference the setup file in your Vitest config:

// vitest.config.ts
import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    setupFiles: ['./vitest.setup.ts'],
  },
});

Rstest

Add the following to your Vitest setup file (e.g. rstest.setup.ts):

// rstest.setup.ts
import { resultMatchers } from '@praha/byethrow-testing';
import { expect } from '@rstest/core';

import type { ResultMatchers } from '@praha/byethrow-testing';

declare module '@rstest/core' {
  interface Matchers<T> extends ResultMatchers<T> {}
}

expect.extend(resultMatchers);

Then reference the setup file in your Vitest config:

// rstest.config.ts
import { defineConfig } from '@rstest/core';

export default defineConfig({
  setupFiles: ['./rstest.setup.ts'],
});

Matchers

toBeSuccess(callback?)

Asserts that the received value is a success Result. An optional callback receives the success value for further assertions.

Without a callback, it only checks that the result is a success:

import { Result } from '@praha/byethrow';

test('result is success', () => {
  const result = Result.succeed(42);

  expect(result).toBeSuccess();
});

With a callback, the success value is passed to it for further assertions:

import { Result } from '@praha/byethrow';

test('result is success with value', () => {
  const result = Result.succeed(42);

  expect(result).toBeSuccess((value) => {
    expect(value).toBe(42);
  });
});

toBeFailure(callback?)

Asserts that the received value is a failure Result. An optional callback receives the error value for further assertions.

Without a callback, it only checks that the result is a failure:

import { Result } from '@praha/byethrow';

test('result is failure', () => {
  const result = Result.fail(new Error('something went wrong'));

  expect(result).toBeFailure();
});

With a callback, the error value is passed to it for further assertions:

import { Result } from '@praha/byethrow';

test('result is failure with error', () => {
  const result = Result.fail(new Error('something went wrong'));

  expect(result).toBeFailure((error) => {
    expect(error.message).toBe('something went wrong');
  });
});

🤝 Contributing

Contributions, issues and feature requests are welcome.

Feel free to check issues page if you want to contribute.

📝 License

Copyright © PrAha, Inc.

This project is MIT licensed.