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

jitter-batch-export

v0.1.4

Published

This repository contains a small Playwright workspace for exporting every scene in a Jitter project.

Readme

Jitter batch export

This repository contains a small Playwright workspace for exporting every scene in a Jitter project.

Install

npm install
npm run browsers:install

Global install

After publishing, install the package globally and use the binaries directly:

npm install -g jitter-batch-export

Available commands:

jitter-batch-export https://jitter.video/file/?id=nnbd6mVCRuGmX4iwMsydV4Xq
jitter-batch-export auth
jitter-batch-export auth-clear
jitter-batch-export cleanup

First login

Run the auth step once and complete sign-in in the browser:

jitter-batch-export auth

That saves browser storage state to ~/.jitter-batch-export/.auth/jitter.storage-state.json. If the saved auth state gets weird, clear it with jitter-batch-export auth-clear and log in again. By default the auth state lives under ~/.jitter-batch-export/.auth/jitter.storage-state.json so it works from a global install. Set JITTER_PLAYWRIGHT_ROOT if you want to store it somewhere else.

Export scenes

Pass the file ID or full URL on the command line:

jitter-batch-export https://jitter.video/file/?id=nnbd6mVCRuGmX4iwMsydV4Xq

The export runner now runs headless by default. Use --headed or JITTER_HEADLESS=false if you want the UI. It uses Chromium only, both for login and export.

The export runner reads artboard IDs from the project payload and opens the batch export URL directly in new tabs. It closes its own browser context on normal exit and Ctrl-C. Use jitter-cleanup only when you need to clear stale browser sessions manually.

If a previous run left browser windows open, clean them up with:

jitter-batch-export cleanup

Optional overrides:

JITTER_HEADLESS=false JITTER_EXPORT_SIZE=4K JITTER_FPS=30 jitter-batch-export https://jitter.video/file/?id=nnbd6mVCRuGmX4iwMsydV4Xq

Notes

  • The auth state file is intentionally ignored by git.
  • The published npm package is built from dist/ in CI.
  • Releases use npm trusted publishing from GitHub Actions, so no long-lived npm token is stored in the repo.
  • Before the first release, configure the package as a trusted publisher on npmjs.com for the ryan-blunden/jitter-batch-export repository and the publish-npm.yml workflow.
  • To push a release tag from the current package.json version, run npm run release.