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

@wistudent/jest-each-improved-types

v2.1.0

Published

Using recursive conditional types from typescript 4.1 to improve typings of table driven jest-each tests.

Downloads

1,840

Readme

jest-each-improved-types

npm version

When using .each with the table notation, it is possible to set the type of the test function argument on the .each function as a generic argument:

import {test, expect} from "@jest/globals";

test.each<{a: string, b: number, expected: boolean}>`
a      | b    | expected
${'1'} | ${1} | ${true}
${'1'} | ${2} | ${false}
`('some test', ({a, b, expected}) => {
  expect(a === `${b}`).toBe(expected)
});

But this only sets the type for the test function argument, it does not ensure that the correct values were used inside the table. The following does not result in a typescript error:

import {test, expect} from "@jest/globals";

test.each<{a: string, b: number, expected: boolean}>`
a            | b     | expected
${undefined} | ${{}} | ${null}
`('some test', ({a, b, expected}) => {
  expect(a === `${b}`).toBe(expected)
});

This package adds an additional way of providing type definitons to .each table tests that ensures that the values used inside the table are compatible with the provided typescript types. It does by reexporting @jest/globals and extending the type definition of the .each function.

import {test, expect} from "@wistudent/jest-each-improved-types"

test.each<[['a', string], ['b', number], ['expected', boolean]], 2>`
a      | b    | expected
${'1'} | ${1} | ${true}
${'1'} | ${2} | ${false}
`('some test', ({a, b, expected}) => {
  expect(a === `${b}`).toBe(expected)
});

Instead of using an interface as the generic argument, a tuple of Key-Type pairs and the number of rows is used. Using a value with the wrong type inside the table, or the number of values not being (Number of Key-Type pairs * Declared number of rows), will result in a typescript error.