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 🙏

© 2025 – Pkg Stats / Ryan Hefner

hemera-store

v2.0.0

Published

This is a store interface for Hemera to be interoperable with most database interfaces

Downloads

85

Readme

Hemera-store package

npm styled with prettier

Simple API to be interoperable with most database interfaces.

Interface

Provide a unique pattern set for all common api methods. We had to choose for some conventions across document and table oriented stores.

| Table-oriented | Document-oriented | Convention | | -------------- | ----------------- | -------------- | | Database | Database | Database | | Collection | Collection | Collection |


create

The pattern is:

  • topic: is the store name to publish to <name>-store
  • cmd: is the command to execute create
  • collection: the name of the table or collection string
  • data: the data which represent the entity to create object or Array<object>

Example:

hemera.act(
  {
    topic: 'sql-store',
    cmd: 'create',
    collection: 'product',
    data: {
      name: 'tomato'
    }
  },
  function(err, resp) {}
)

update

The pattern is:

  • topic: is the store name to publish to <name>-store
  • cmd: is the command to execute update
  • collection: the name of the table or collection string
  • data: the data which represent the entity to update object
  • query: the search criteria object

Example:

hemera.act(
  {
    topic: 'sql-store',
    cmd: 'update',
    collection: 'product',
    query: {},
    data: {
      name: 'tomato'
    }
  },
  function(err, resp) {}
)

updateById

The pattern is:

  • topic: is the store name to publish to <name>-store
  • cmd: is the command to execute updateById
  • collection: the name of the table or collection string
  • data: the data which represent the entity to create object
  • id: the primary identifier of your entity string or number

Example:

hemera.act(
  {
    topic: 'sql-store',
    cmd: 'updateById',
    id: 1,
    collection: 'product',
    data: {
      name: 'tomato'
    }
  },
  function(err, resp) {}
)

find

The pattern is:

  • topic: is the store name to publish to <name>-store
  • cmd: is the command to execute find
  • collection: the name of the table or collection string
  • query: the search criteria object
  • options: the search criteria object (optional)
    • limit: maximum items to fetch integer
    • offset: the offset integer
    • orderBy: the offset array<string> or string or map<string, int>
    • fields: the projection settings array<string> or map<string, int>

Example:

hemera.act(
  {
    topic: 'sql-store',
    cmd: 'find',
    collection: 'product',
    query: {}
  },
  function(err, resp) {}
)

findById

The pattern is:

  • topic: is the store name to publish to <name>-store
  • cmd: is the command to execute findById
  • collection: the name of the table or collection string
  • id: the primary identifier of your entity string or number

Example:

hemera.act(
  {
    topic: 'sql-store',
    cmd: 'findById',
    id: 1,
    collection: 'product'
  },
  function(err, resp) {}
)

remove

The pattern is:

  • topic: is the store name to publish to <name>-store
  • cmd: is the command to execute remove
  • collection: the name of the table or collection string
  • query: the search criteria object

Example:

hemera.act(
  {
    topic: 'sql-store',
    cmd: 'remove',
    collection: 'product',
    query: {}
  },
  function(err, resp) {}
)

removeById

The pattern is:

  • topic: is the topic to publish to sql-store
  • cmd: is the command to execute removeById
  • collection: the name of the table or collection string
  • id: the primary identifier of your entity string or number

Example:

hemera.act(
  {
    topic: 'sql-store',
    cmd: 'removeById',
    id: 1,
    collection: 'product'
  },
  function(err, resp) {}
)

replace

The pattern is:

  • topic: is the store name to publish to <name>-store
  • cmd: is the command to execute replace
  • collection: the name of the table or collection string
  • data: the data which represent the entity to replace object
  • query: the search criteria object

Example:

hemera.act(
  {
    topic: 'sql-store',
    cmd: 'replace',
    collection: 'product',
    query: {},
    data: {
      name: 'tomato'
    }
  },
  function(err, resp) {}
)

replaceById

The pattern is:

  • topic: is the store name to publish to <name>-store
  • cmd: is the command to execute replaceById
  • collection: the name of the table or collection string
  • data: the data which represent the entity to update object
  • id: the primary identifier of your entity string or number

Example:

hemera.act(
  {
    topic: 'sql-store',
    cmd: 'replaceById',
    id: 1,
    collection: 'product',
    data: {
      name: 'tomato'
    }
  },
  function(err, resp) {}
)

exists

The pattern is:

  • topic: is the store name to publish to <name>-store
  • cmd: is the command to execute exists
  • collection: the name of the table or collection string
  • query: the search criteria object

Example:

hemera.act(
  {
    topic: 'sql-store',
    cmd: 'exists',
    collection: 'product',
    query: {}
  },
  function(err, resp) {}
)

count

The pattern is:

  • topic: is the store name to publish to <name>-store
  • cmd: is the command to execute count
  • collection: the name of the table or collection string
  • query: the search criteria object

Example:

hemera.act(
  {
    topic: 'sql-store',
    cmd: 'count',
    collection: 'product',
    query: {}
  },
  function(err, resp) {}
)