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

jest-to-node

v0.0.1

Published

Migrate Jest tests to Node's native test runner.

Readme

Step 1: Local Build

First, compile your TypeScript code to JavaScript using your build script:

npm run build

Step 2: Link Locally

Before you publish the package, you can use npm link to simulate installing your package globally. This creates a symlink in the global folder that links to the local development folder.

  • Link your package globally:

    Navigate to your project directory (where your package.json is located) and run:

     npm link

    This command makes your CLI tool available globally on your system as if it were installed via npm.

  • Test the command:

    You can now run your tool from anywhere using the command name defined in the bin section of your package.json. For example:

    jest-to-node path/to/jest/tests path/to/output

    Replace path/to/jest/tests and path/to/output with actual paths on your local machine where you have some test files ready to be transformed.