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

clouddb

v0.0.1

Published

Cloud database.

Downloads

12

Readme

clouddb

A cloud-based database.

The idea is to create a useful database and document store based on high-level components such as Amazon's S3, SimpleDB and SQS. Although the database may not be the most performant, it should end up being incredibly reliable. And by using AWS services it will be possible to get up and running with nothing more than a set of AWS keys.

To run the tests, copy the config/environment.yaml file to something suitable, and then set your AWS keys. The name of the file you use should be set in the NODE_ENV environment variable. For example, if you create a file config/test.yaml to hold your keys then you can test as follows:

export NODE_ENV=test
mocha

For more information on why that works, see the magical config module.

Alternatively, if using npm test, then create a config/_default.yaml file, which looks something like this:

aws:
  accessKeyId: '12345678blah'
  secretAccessKey: xyzblah