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

@fern-api/replay

v0.7.0

Published

Automatically preserves SDK customizations across Fern regenerations

Readme

@fern-api/replay

Automatically preserves SDK customizations across Fern regenerations.

What it does

Fern Replay detects user edits to generated SDK code, stores them as patches, and re-applies them after each regeneration using 3-way merge. This means your customizations survive fern generate without manual intervention.

Pipeline

  1. Detect — Find commits since last generation
  2. Store — Save patches to replay.lock
  3. Generate — Run generator (overwrites all)
  4. Replay — Apply patches via 3-way merge
  5. Commit — Commit the merged result (or surface conflicts)

Install

npm install @fern-api/replay

Development

npm install
npm run build
npm test

Local Development with Fern CLI

To use a local version of @fern-api/replay with the Fern CLI monorepo:

# From the fern-replay directory
cd /path/to/fern-replay
pnpm link --global

# From the fern monorepo root
cd /path/to/fern
pnpm link --global @fern-api/replay

Verify the link is working:

ls -la node_modules/@fern-api/replay
# Should show a symlink pointing to your local fern-replay directory

Any changes you make in fern-replay will be picked up immediately without reinstalling.

To unlink and restore the published npm version:

pnpm unlink @fern-api/replay
pnpm install

License

MIT