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

@anemone/codemod

v0.0.3

Published

Upgrade EdgeDB code to Gel

Readme

Codemod

  • CLI entry point is cli.ts
  • scripts has custom scripts like changing file names, etc.
  • transforms contains different codemod scripts (imported and used in transforms/index.ts)
  • __tests__ contains tests for the codemod
  • __testfixtures__ contains test fixtures

Usage

yarn codemod <path-to-directory>

Tests

yarn test

Tests setup follows the jscodeshift documentation.

Development

JSCodeShift transforms:

  1. Add a new transform in transforms directory, e.g. transforms/my-transform.ts
  2. Add a corresponding unit test in __tests__ directory, e.g. __tests__/my-transform.spec.ts
  3. Add test fixtures in __testfixtures__ directory, e.g. __testfixtures__/my-transform/basic.input.ts and __testfixtures__/my-transform/basic.output.ts
  4. Add a new entry in transforms/index.ts to use the new transform
  5. Run tests with yarn test

Custom scripts:

  1. Add a new script in scripts directory, e.g. scripts/my-script.ts
  2. Use it in cli.ts