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

@workjournal/cli

v1.0.0

Published

Command-line tool for Workjournal — manage workspaces, journals, entries, and collaborators from your terminal.

Vulnerabilities

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

Links

Git

Maintainers

venturesquadventuresquad

Keywords

workjournalclioauthauthenticationai-agentsjournaling

Readme

@workjournal/cli

Command-line tool for Workjournal — manage workspaces, journals, entries, and collaborators from your terminal.

Breaking changes in 0.5.0

  • Removed workjournal workspaces new (and its --slug flag). Workspace creation is no longer exposed on the CLI — the API still supports it for the future paid-tier signup path, but day-to-day users have one workspace and don't need to create more.
  • Added workjournal journals rename <ws> <j> <newName> — renames a journal via PATCH /v1/workspaces/:ws/journals/:j with { name }.
  • Added workjournal journals set-slug <ws> <j> <newSlug> — changes a journal's slug via the same PATCH with { slug }. Prints a one-line stderr warning before the call: changing a slug breaks any existing links.

If you scripted around workspaces new, switch to creating workspaces through the web app or the API directly.

Breaking changes in 0.4.0

This release switches the CLI to slug-based addressing end to end. Every command that used to take a journal UUID now takes a <workspaceSlug> and <journalSlug> pair instead.

  • workjournal journals get <id> → workjournal journals get <ws> <j>
  • workjournal journals delete <id> → workjournal journals delete <ws> <j>
  • workjournal journals select <id> → workjournal journals select <ws> <j>
  • workjournal journal entries write … → workjournal entries write <ws> <j> -t … -s … -b …
  • workjournal journal export … → workjournal export <ws> <j> [-f …] [-p …]
  • New top-level workjournal workspaces group (list, get, new, select).
  • Project config (.workjournal) now stores { workspaceSlug, journalSlug }. Existing files with the old { journal_id } shape are migrated automatically on the next command that needs the selection — re-select manually if you're offline.
  • The default table for journals list drops the UUID column. Use --json if you need the full object including id.

If you're scripting against the CLI, search-and-replace the old verb forms before upgrading. The old UUID-based API endpoints have already been removed — older CLI versions will start returning 404s.

Install

Run on demand without installing:

npx @workjournal/cli <command>

Or install globally:

npm install -g @workjournal/cli
workjournal <command>

First-time setup

workjournal auth login                              # authenticate
workjournal workspaces list                         # find your workspace slug
workjournal journals list <workspaceSlug>           # find your journal slug
workjournal journals select <workspaceSlug> <journalSlug>
                                                    # set the active selection

Once a journal is selected, workjournal (no args) lists entries and workjournal journal shows journal details — neither needs the slugs repeated. Other resource verbs (entries, shares, invites, export) still take explicit positional slugs to keep scripts self-documenting.

Commands

| Command | Description | |---------|-------------| | workjournal workspaces list | List your workspaces | | workjournal workspaces select <ws> | Set active workspace | | workjournal journals list [<ws>] | List journals (defaults to selected workspace) | | workjournal journals list shared-with-me | List journals shared with you from workspaces you don't own | | workjournal journals new <ws> <name> [--slug <slug>] | Create a journal | | workjournal journals rename <ws> <j> <newName> | Rename a journal | | workjournal journals set-slug <ws> <j> <newSlug> | Change a journal's slug (breaks existing links) | | workjournal journals select <ws> <j> | Set active journal. Works for owned and shared journals — for shared, use the workspace slug from journals list shared-with-me. | | workjournal entries list <ws> <j> | List entries | | workjournal entries write <ws> <j> -t <title> -s <summary> -b <body> | Create an entry (title required, ≤80 chars) | | workjournal entries last <ws> <j> [count] | Show the most recent entries | | workjournal entries get <ws> <j> <index> | Show one entry | | workjournal entries search <ws> <j> <query> | Search entries | | workjournal invites new <ws> <j> <email> | Invite a collaborator | | workjournal shares list <ws> <j> | List members | | workjournal export <ws> <j> [-f json\|md\|csv] [-p <path>] | Export journal data | | workjournal auth login | Interactive login (works over SSH too) | | workjournal auth logout | Remove stored credentials | | workjournal auth whoami | Show current auth status | | workjournal --json <command> | Output raw JSON instead of tables | | workjournal help | Full command reference |

For the complete command reference, see workjournal.pro/docs/commands.

Typical workflows

Add a new entry:

workjournal entries write acme engineering -t "v2 API ship" -s "Shipped v2 API" -b "Migrated /v1 callers and flipped the flag."

Invite a collaborator:

workjournal invites new acme engineering [email protected]

Export a journal to Markdown:

workjournal export acme engineering -f md -p ./journal.md

Once selected, list entries with no args:

workjournal journals select acme engineering
workjournal                         # lists entries in acme/engineering

Shared journals (shared-with-me)

A shared journal is one where you're a contributor in someone else's workspace. Accept the invitation in the web app first, then from the terminal:

# 1. List — two-column table: workspace slug, journal slug
workjournal journals list shared-with-me

# 2. Select — pass both slugs from the listing
workjournal journals select acme engineering

# 3. Access — every other command works as normal against the pinned journal
workjournal entries last
workjournal entries write -t … -s … -b …

shared-with-me is only recognised by journals list. journals select and everything else take the real workspace slug from the listing (acme, not shared-with-me).

Credentials

The CLI stores credentials in the user config directory with user-only file permissions:

| Platform | Default path | |---|---| | Linux / WSL2 (Linux Node) | ${XDG_CONFIG_HOME:-$HOME/.config}/workjournal/credentials.json | | macOS | ${XDG_CONFIG_HOME:-$HOME/.config}/workjournal/credentials.json | | Windows | %APPDATA%\workjournal\credentials.json (PowerShell: $env:APPDATA\workjournal\credentials.json) |

Override with WORKJOURNAL_CONFIG_DIR=/your/path. Remove the credentials with workjournal auth logout.

Earlier CLI versions used ~/.workjournal/; on first invocation post-upgrade the directory is moved automatically with a one-line stderr notice.

Headless environments

workjournal auth login works in SSH sessions, dev containers, and CI — it binds no ports and does not require a browser on the same machine. You only need a browser somewhere (laptop, phone) to open the authorize URL.

Links