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

dynoga

v0.1.4

Published

**Dynoga** is a light library for use DynamoDB with javascript objects

Downloads

65

Readme

Dynoga

NPM

Disclaimer

Dynoga is a lightweight library to use DynamoDB with JavaScript objects.

We use CRUD naming for easy matching with Backbone.ioBind

How to use

Initialize

Dynoga = require "dynoga"

db = new Dynoga
  endpoint: config.dynamoDB.endpoint
  accessKeyId: config.dynamoDB.accessKeyId
  secretAccessKey: config.dynamoDB.secretAccessKey
  region: config.dynamoDB.region

Create an item

db.create "mytable", item, (err, model) ->
  if err then console.log err
  console.log model

Read an item

keys: Key/value object, a hash is mandatory

db.read "mytable", keys, (err, model) ->
  if err then console.log err
  console.log model

Update an item

item: Key/value object, a hash and range are mandatory

Dynoga automatically find primary keys for update the good item.

db.update "mytable", item, (err, model) ->
  if err then console.log err
  console.log model

Delete an item

item: Key/value object, a hash and range are mandatory

Dynoga automatically find primary keys for delete the good item.

db.delete "mytable", item, (err, model) ->
  if err then console.log err
  console.log model

Running Tests

Put in your environment

export METIDIA_ACCESS_KEY_ID=YOURACCESKEYID
export METIDIA_SECRET_ACCESS_KEY=YOURSECRETACCESSKEY

Run a local dynomadb instance

$ java -Djava.library.path=. -jar DynamoDBLocal.jar

cf: DynamoDB Local for Desktop Development

Run tests

npm test Execute units tests

npm run watch-test Execute units tests with watch files for changes

Warning

For a natural sorting for READ operations, Dynoga use an internal _createTimeStamp attribute. Please don't use it if you don't want surprise ;)