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

level-restful

v1.0.7

Published

an easy plug-n-play REST wrapper for leveldb

Downloads

5

Readme

level-restful

A simple plug and play REST wrapper for leveldb, as a simple extension to level-orm

NPM

build status

Installation

This module is installed via npm:

$ npm install level-restful

Usage

Basic example

You extend the base class to give you REST post, put, delete, and get. You specify a list of fields to ensure validation of your object so the database stays safe from any pesky clients.

var http = require('http');
var level = require('level');
var db = level('/tmp/db', { valueEncoding: 'json' });
var RestModel = require('level-restful');

function Users(db) {

  var fields = [
    {
      'name': 'handle',
      'type': 'string'
    },
    {
      'name': 'email',
      'type': 'string',
      'index': true
    },
    {
      'name': 'address',
      'type': 'string'
    },
    {
      'name': 'age',
      'type': 'number',
      'optional': true
    }
  ];

  // users is the sublevel name to user
  // handle is the primary key
  RestModels.call(this, db, 'users', 'handle', fields);
}

// make it inherit from RestModel
util.inherits(Users, RestModel);

Wire up your models to your server

The below example is just one of the many ways of wiring up your models to the server. Because this is a tool, not a framework, we leave it up to you to tailor it to your use case.

models = {
  'users': Users
};

var Router = require('routes-router');
var router = Router();

// Wire up API endpoints
router.addRoute('/api/:model/:id?', function(req, res, opts) {
  var id = parseInt(opts.params.id) || opts.params.id || ''
  var model = models[opts.params.model]
  if (!model) {
    return cb(new Error('no model'))
  }
  model.dispatch(req, res, id, cb)
});

var server = http.createServer(router)''
server.listen(8000)''

note: this uses res.end() under the hood.

Auto incremented keys

You can use a keyfn to set auto incremented keys on your models. Do not put the key in your fields list, it will be generated upon save by eugeneware/level-orm.

var timestamp = require('monotonic-timestamp')

function Book(db) {
  fields = [
    {
      'name': 'owner_id',
      'type': 'number'
    },
    {
      'name': 'name',
      'type': 'string'
    }
  ];
  // Call the parent constructor. id is the primary key, but we
  // don't have to define that in the object's schema. It'll be created
  // automagically by level-orm when a keyfn is provided. (see below)
  RestModels.call(this, db, 'book', 'id', fields);
}

// make it inherit from RestModels
util.inherits(Book, RestModels);

// id is auto incremented by the unique timestamp.
// could be more sophisticated.
Book.prototype.keyfn = timestamp;

Secondary indexing

You can create a secondary index on any of your models by adding index: true to the validation schema

var timestamp = require('monotonic-timestamp')

function Book(db) {
  fields = [
    {
      'name': 'owner_id',
      'type': 'number'
    },
    {
      'name': 'author',
      'type': 'string'
    }
    {
      'name': 'name',
      'type': 'string',
      'index': true
    }
  ];
  RestModels.call(this, db, 'book', 'id', fields);
}

Now, a REST consumer can call the api to filter on one of the indexed fields. NOTE, at this time you can only filter on one field.

$ curl 'http://localhost:8000/api/book?name=Moby%20Dick'
{
  'owner_id': 4,
  'author': 'Mark Twain',
  'name': 'Moby Dick'
}

Compound Keys and Shared Containers

This library extends from eugeneware/level-orm, which has examples of Compound Keys and Shared Containers.

License

Copyright (c) 2014, Karissa McKelvey All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.