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

@backblaze-labs/continue-b2-backup

v0.3.0

Published

Back up your Continue (continue.dev) chat sessions and config to Backblaze B2: incremental and encrypted.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

goanpecagoanpecajdnycjdnyc

Keywords

continuecontinuedevbackblazeb2backup

Readme

continue-b2-backup

Incremental, encrypted backup of your Continue chat sessions and config to Backblaze B2.

Built on @backblaze-labs/agent-backup-core.

Why

Continue stores every chat session as JSON under ~/.continue/sessions/, on your machine only — Continue Hub syncs assistant definitions down to the IDE but never backs up your local sessions. This mirrors them (and your config) to B2 on a schedule.

Install & configure

npm install -g @backblaze-labs/continue-b2-backup
export B2_KEY_ID=004... B2_APPLICATION_KEY=K004... B2_BUCKET=my-continue-backups
export B2_ENCRYPTION_KEY="a long random passphrase"

Or ~/.config/continue-b2-backup/config.json. Optional: B2_REGION, B2_PREFIX, B2_SCHEDULE, B2_KEEP_SNAPSHOTS, CONTINUE_GLOBAL_DIR.

Run

continue-b2-backup            # daemon: auto-restore on first run, back up now, then on schedule
continue-b2-backup --once     # single backup then exit
continue-b2-backup --install  # install an OS service (launchd / systemd / Task Scheduler)
continue-b2-backup --help     # usage

What gets backed up

Mirrors ~/.continue (or CONTINUE_GLOBAL_DIR):

  • Included: sessions/*.json (chat history — the main user data), config.yaml/config.json/config.ts, prompts/, and assistants//agents/ definitions.
  • Excluded: index/ (codebase embeddings + index.sqlite — large and regenerable), dev_data/ (usage telemetry + devdata.sqlite), logs/, .utils/. Excluding these also means there's no live SQLite database to snapshot.

Security

Set B2_ENCRYPTION_KEY (separate from your B2 credentials) — config.yaml can contain inline API keys and is included (encrypted) so restores work. ~/.continue/.env (the recommended plaintext secrets store) is excluded and never shipped to B2.

License

MIT