Skip to content

ryan-blunden/jitter-batch-export

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

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.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Packages

 
 
 

Contributors