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

@chronicle.app/slack

v0.5.0

Published

Chronicle plugin for Slack message history via slackdump export

Readme

@chronicle.app/slack

Chronicle plugin for Slack message history, read from a slackdump export directory.

Exporting your data

Slack's own export supports public channels on all plans, including Free. Business+ and Enterprise also support private-channel and DM exports with the appropriate access; see Slack's export documentation. slackdump exports conversations your account can access — public and private channels, DMs, and group DMs (mpims) — to a local directory.

# Authenticate and export in Slack-export layout
slackdump export -o my-slack-export

This produces a directory like:

my-slack-export/
├── channels.json          # public/private channels
├── dms.json               # direct messages
├── mpims.json             # group DMs
├── users.json             # workspace members
├── <channel-name>/        # one dir per conversation
│   ├── 2024-03-13.json     #   messages, one file per day
│   └── attachments/        #   downloaded files (if exported)
└── attachments/           # top-level aggregate of all files

Attachments are only present on disk if you exported them with slackdump. Chronicle includes attachment metadata only when --attachments is enabled; otherwise attachments are omitted entirely. With that flag, extraction includes a contentPath for files found locally. Files not found locally are recorded as metadata only. Extraction does not store attachment bytes.

Usage

# Extract to stdout (Chronicle JSON-LD)
chronicle extract slack --input ./my-slack-export

# Include file attachments (with a contentPath for downloaded files)
chronicle extract slack --input ./my-slack-export --attachments

Use --since / --until for incremental or windowed extraction:

chronicle extract slack --input ./my-slack-export --since 2024-01-01

Configuration

  • --input (required): the slackdump export, as a folder or zip
  • --attachments: include file attachments (default: false)
  • --since: only extract messages on or after this date
  • --until: only extract messages on or before this date
  • --limit: maximum number of records to extract (default 100; 0 for no limit)

Schema

This plugin maps Slack data onto the following Chronicle types:

  • Messages → MessageAction whose result is a Message (source: slack, body, author, recipient)
  • Users → Agent (resolved to a handle and name from users.json, group-DM metadata, and message profiles)
  • File attachments → ImageObject / AudioObject / VideoObject / DocumentObject (by MIME type), with contentPath to the locally exported file when available

Recipients are inferred from the conversation type: a DM addresses the other person, a group DM addresses every other member, a small private channel addresses its members, and a public/large channel is treated as a broadcast (no recipients).

Development

# Build the plugin
npm run build -w @chronicle.app/slack

# Typecheck and lint
npm run typecheck -w @chronicle.app/slack
npm run lint -w @chronicle.app/slack

# Run tests
npm run test -w @chronicle.app/slack

Tests build a small synthetic slackdump export (made-up users, channels, DMs, and a group DM) in a temporary directory, so they never read the host's Slack data or accounts and never touch the network.