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

jifro

v0.3.0

Published

An indexed JSON file database. Read-only fork.

Downloads

2

Readme

jifro

jifro is a feature-reduced fork of jify, an experimental library/tool for querying large (GBs) JSON files. It does this by consuming an index over the required fields.

In contrast to jify, jifro is read-only, i.e. it can only query a JSON file with an existing index but it can’t modify either.

Building the index must be done in jify proper before jifro can use it. When a JSON file is indexed (eg. data.json), an index file is created in the same directory with a .index.json extension (eg. data.index.json).

Why?

One might ask why one would want a separate, immutable version of jify rather than just ignore jify’s write-access features.

The answer is that jify’s write-access features are using native code via jify’s os-lock dependency. While using native modules is usually not an issue, they can cause issues when one tries to use them on specific hosting platforms such as Electron apps.

In other words, embedding the library inside an Electron app is easier if it doesn’t use native code. For use cases where read-only access is sufficient, this fork may be a useful trade-off.

Install

npm install jifro

Usage

At development/build time (using jify):

const { Database } = require('jify');

async function main() {
  // Must be created and indexed by
  const db = new Database('books.json');

  // Create
  await db.create();

  // Insert - Single
  await db.insert({
    title: 'Robinson Crusoe',
    year: 1719,
    author: { name: 'Daniel Defoe' }
  });

  // Insert - Batch
  await db.insert([
    {
      title: 'Great Expectations',
      year: 1861,
      author: { name: 'Charles Dickens' }
    },
    {
      title: 'Oliver Twist',
      year: 1838,
      author: { name: 'Charles Dickens' }
    },
    {
      title: 'Pride and Prejudice',
      year: 1813,
      author: { name: 'Jane Austen' }
    },
    {
      title: 'Nineteen Eighty-Four',
      year: 1949,
      author: { name: 'George Orwell' }
    }
  ]);

  // Index - creates books.index.json file
  await db.index('title', 'year', 'author.name');
}

main();

Then, at runtime (using jifro):

const { Database, predicate: p } = require('jifro');

async function main() {
  // The same JSON file that jify created earlier
  const db = new Database('books.json');

  // Query
  console.log('author.name = Charles Dickens, year > 1840');
  const query = { 'author.name': 'Charles Dickens', year: p`> ${1840}` };
  for await (const record of db.find(query))
    console.log(record);

  let records;

  // Range query
  console.log('1800 <= year < 1900');
  records = await db.find({ year: p`>= ${1800} < ${1900}` }).toArray();
  console.log(records);

  // Multiple queries
  console.log('year < 1800 or year > 1900');
  records = await db.find(
    { year: p`< ${1800}` }, { year: p`> ${1900}` }
  ).toArray();
  console.log(records);
}

main();

CLI

$ jifro find --query "author.name=Charles Dickens,year>1840" books.json
$ jifro find --query "year>=1800<1900" books.json
$ jifro find --query "year<1800" --query "year>1900" books.json

Implementation

The index is implemented as a JSON array of skip list entries. The entries are encoded as strings and all numbers embedded in the string are encoded using Z85. This implementation was chosen for its simplicity and to allow for using a single JSON file as an index. Better performance might be achieved by using a different data structure, a binary format, or multiple index files.

Performance

jify (and, by extension, jifro) is reasonably fast. Query time is < 5ms for the first result + (0.1ms find + 0.1ms fetch) per subsequent result. All tests on a MBP 2016 base model.

Credits

Credits go to @mohd-akram, the original author of jify.