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

sui-indexer

v1.0.1

Published

sui indexer made by therealmagyar lmao

Readme

Key Changes

  1. Automatic PrismaClient Initialization:
    • The Db class now imports @prisma/client and creates a new PrismaClient instance if none is provided in the constructor.
    • This eliminates the need for users to declare const prisma = new PrismaClient() in their code.
  2. Database Methods Under db:
    • Removed the #proxyDbMethods function from Indexer.
    • The Db instance is now exposed as indexer.db, allowing calls like indexer.db.save(), indexer.db.modify(), etc.
  3. Dependency Update:
    • Added @prisma/client as a direct dependency in package.json since it’s now used internally.
    • Removed it from peerDependencies to simplify installation for users.
  4. Simplified Usage:
    • The usage example in the README.md and your provided code no longer requires declaring a PrismaClient.
    • Database methods are accessed via indexer.db, matching your specified syntax.
  5. Maintained Flexibility:
    • Users can still provide a custom prismaClient via the options.prismaClient parameter if they need to customize the Prisma client (e.g., with specific configurations).
    • Config customization remains intact via options.config or options.configOverrides.

Updated Usage Example

Your provided usage code is now simplified as follows:

const Indexer = require('my-indexer-package');

async function main() {
  const indexer = new Indexer({
    configOverrides: {
      db: { host: 'production.db.com' },
      proxy: { SPEED_CONFIG: { RATE_LIMIT_DELAY: 1000 } }
    }
  });

  await indexer.start();
  // Output: Indexer started with configuration: { db: { host: 'production.db.com' }, proxy: {...} }
  // Output: Saving data to database at production.db.com...
  // Output: Data saved to the database: { status: 'Indexer started' }

  await indexer.db.save({ data: 'test' });
  // Output: Saving data to database at production.db.com...
  // Output: Data saved to the database: { data: 'test' }

  await indexer.db.modify(1, { data: 'updated' });
  // Output: Modifying data in database at production.db.com...
  // Output: Data modified in the database: { id: 1, data: 'updated' }

  await indexer.db.delete(1);
  // Output: Deleting data from database at production.db.com...
  // Output: Data deleted from the database: 1

  await indexer.db.reset();
  // Output: Resetting database at production.db.com...
  // Output: Database reset.
}

main().catch(console.error);