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 🙏

© 2024 – Pkg Stats / Ryan Hefner

hemera-arango-store

v7.0.2

Published

This is a plugin to use Arangodb with Hemera

Downloads

104

Readme

:avocado: Hemera-arango-store package

Build Status npm styled with prettier

This is a plugin to use Arangodb with Hemera.

Execute any AQL query from anywhere. For more details ArangoDB Query Language

Start Arangodb with Docker

docker run -e ARANGO_NO_AUTH=1 -d --name arangodb-instance -d arangodb -p 8529:8529

Running the tests

Install and start Arangodb before running the tests.

arangod.conf

endpoint = tcp://127.0.0.1:8529
authentication = false
npm run test

Install

npm i hemera-arango-store --save

Usage

const hemera = new Hemera(nats)
hemera.use(require('hemera-joi'))
hemera.use(require('hemera-arango-store'), {
  database: {
    url: 'http://127.0.0.1:8529',
    name: 'test' // default database
  }
})

Plugin decorators

  • hemera.arango
  • hemera.aql

API

See Store Interface.

Database specific interface


createCollection

The pattern is:

  • topic: is the store name to publish to arango-store
  • cmd: is the command to execute createCollection
  • name: the name of the collection string
  • database: the database to use against the query. string (optional)
  • type: the type of collection to create edge or "" (optional)

Example:

hemera.act(
  {
    topic: 'arango-store',
    cmd: 'createCollection',
    name: 'products'
  },
  function(err, resp) {}
)

executeAqlQuery

The pattern is:

  • topic: is the store name to publish to arango-store
  • cmd: is the command to execute executeAqlQuery
  • database: the database to use against the query. string (optional)
  • query: the AQL query string
  • type: return one or multiple results one or all

Example:

hemera.act(
  {
    topic: 'arango-store',
    cmd: 'executeAqlQuery',
    type: 'one',
    database: 'test',
    query: aql`INSERT ${user} INTO testColl return NEW`
  },
  function(err, resp) {}
)

executeTransaction

The pattern is:

  • topic: is the store name to publish to arango-store
  • cmd: is the command to execute executeTransaction
  • database: the database to use against the query. string (optional)
  • action: a string evaluating to a JavaScript function to be executed on the server. string
  • params: available as variable params when the action function is being executed on server. Check the example below. object
  • collection: If collections is an array or string, it will be treated as collections.write. object (optional)
    • read: an array of names (or a single name) of collections that will be read from during the transaction. Array<string> (optional)
    • write: an array of names (or a single name) of collections that will be written from during the transaction. Array<string> (optional)
  • lockTimeout: determines how long the database will wait while attemping to gain locks on collections used by the transaction before timing out. integer

Example:

var action = String(function() {
  return true
})

hemera.act(
  {
    topic: 'arango-store',
    cmd: 'executeTransaction',
    database: 'test',
    action,
    params: {
      age: 12
    },
    collections: {
      read: 'users'
    }
  },
  function(err, resp) {}
)

createDatabase

The pattern is:

  • topic: is the store name to publish to arango-store
  • cmd: is the command to execute executeAqlQuery
  • name: the name of the database. string

Example:

hemera.act(
  {
    topic: 'arango-store',
    cmd: 'createDatabase',
    name: 'test'
  },
  function(err, resp) {}
)