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

@adobe/helix-shared-journal

v2.0.2

Published

Shared modules of the Helix Project - journal

Readme

Helix Shared Journal

S3-backed journal readers and writers, copied from the auditlog module in @adobe/helix-admin-support. The existing storage format and behavior are preserved, with the public API renamed from AuditLog to Journal.

Usage

import { Journal } from '@adobe/helix-shared-journal';

const options = { bucketName: 'helix-adobe-logs' };
const writer = await Journal.createWriter('org', 'site', console, options).init();
try {
  await writer.append([{ timestamp: Date.now(), action: 'preview' }]);
} finally {
  writer.close();
}

const reader = await Journal.createReader('org', 'site', console, options).init();
try {
  const pagination = { limit: 1000 };
  let page = await reader.getEntries(
    Date.parse('2026-01-01'),
    Date.now(),
    pagination,
  );
  console.log(page.entries);
  while (page.start && page.end) {
    page = await reader.getNextPage(page.start, page.end, pagination);
    console.log(page.entries);
  }
} finally {
  reader.close();
}

AWS credentials and region are resolved by the AWS SDK. The default bucket is helix-adobe-logs; override it with bucketName. Omit the site (pass undefined) to use the organization-wide log under <org>/.all.

Use Journal.getBucketAndKey('org', 'site', 'custom.json') to get { bucket: 'helix-adobe-logs', key: 'org/site/custom.json' } for a custom file alongside the journal. Pass undefined as the site to use the key org/.all/custom.json instead. An optional fourth argument, { bucketName }, overrides the default bucket.

Entries must have a millisecond timestamp and be appended in chronological order. The writer stores gzip-compressed JSON files and maintains a .index file. Use a single writer per log prefix to avoid concurrent read-modify-write conflicts.

Call getEntries(from, to, options) once to retrieve the first page. The reader returns { entries, start?, end? }. While both start and end are present, pass them to getNextPage(start, end, options) to retrieve the next page. limit caps the number of entries; optional maxSize limits their serialized size, but always allows at least one entry.

Development

From the repository root:

npm test --workspace=@adobe/helix-shared-journal
npm run lint --workspace=@adobe/helix-shared-journal