NanoCouch is a minimalistic driver for CouchDB built on mikeals/request
JavaScript Shell
Pull request Compare This branch is 502 commits behind dscape:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


nano (short for nanocouch) is a minimalistic couchdb driver for node.js


  1. install npm
  2. npm install nano


  var nano = require('nano')('http://localhost:5984');

within the nano variable you have various methods you can call. these include tasks like create, delete or list databases:


in this function there is not callback. in nano the absence of callback means "do this, ignore what happens"

you normally don't want to do that though:

  // clean up the database we created previously
  nano.db.destroy("alice", function() {
    nano.db.create("alice", function() {
      // specify the database we are going to use
      var alice = nano.use("alice");
      alice.insert({crazy: true}, "rabbit", function(e,b,h){
        if(e) { throw e; }
        console.log("you have inserted the rabbit.")

the nano.use method creates a scope where you operate inside a single database. this is just a convenience so you don't have to specify the database name every single time you do an update or delete

  // 5: var alice = nano.use("alice");

in nano a callback has always the same three arguments

  // 6: alice.insert({crazy: true}, "rabbit", function(e,b,h) {
  // 7:   if(e) { throw e; }
  // 8:   console.log("you have inserted the rabbit.")
  // 9: });


  e: the `error`, if any
  b: the http `response body` from couchdb, if no error. json parsed body, binary for non-json responses
  h: the http response `headers` from couchdb, if no error

errors include responses from couchdb which had a non 200 response code. that's it. don't forget to delete the database you created:


tutorials & screencasts


* marks optional params are additional querystring parameters

databases, et al


server.db.create(db_name,callback*) server.db.get(db_name,callback*) server.db.destroy(db_name,callback*) server.db.list(callback*) server.db.compact(db_name,design_name*,callback*) server.db.replicate(source,target,continuous*,callback*) server.db.changes(db_name,params*,callback*) server.use(db_name) server.request(opts,callback*) server.config


nano.use: [nano.db.use, nano.db.scope, nano.scope] nano.request: [nano.relax, nano.dinosaur]

documents, attachments, views, et al


db.insert(doc,doc_name*,callback*) db.destroy(doc_name,rev,callback*) db.get(doc_name,params*,callback*) db.bulk(docs,callback*) db.list(params*,callback*) db.view(design_name,view_name,params*,callback*) db.attachment.insert(doc_name,att_name,att,content_type,params*,callback*) db.attachment.get(doc_name,att_name,params*,callback*) db.attachment.destroy(doc_name,att_name,rev,callback*)


nano.use sets db_name in scope so you don't have to specify it every time

nano.db.get: [*)] nano.db.replicate: [doc.replicate(target,continuous*,callback*)] nano.db.compact: [doc.compact(callback*), doc.view.compact(design_name,callback*)] nano.db.changes: [doc.changes(params*,callback*)]


nano is minimalistic so it provides advanced users with a way to code their own extension functions:


to get a document in a specific rev an advanced user might do:

  nano.request( { db: "alice"
                , doc: "rabbit"
                , method: "GET"
                , params: { rev: "1-967a00dff5e02add41819138abb3284d"}
    function (_,b) { console.log(b) });

this is the same as (assuming alice = require('nano')('http://localhost:5984/alice')):

  alice.get("rabbit", {rev: "1-967a00dff5e02add41819138abb3284d"},
    function (_,b) { console.log(b) });


you can pipe in nano just like you do in any other stream. this is available in all methods:

  alice.attachment.get("breakfast", "sugar", {rev: rev})


check issues


everyone is welcome to contribute. patches, bugfixes, new features

  1. create an issue on github so the community can comment on your idea
  2. fork nano in github
  3. create a new branch git checkout -b my_branch
  4. create tests for the changes you made
  5. make sure you pass both existing and newly inserted tests
  6. commit your changes
  7. push to your branch git push origin my_branch
  8. create an pull request


to run (and configure) the test suite simply:

  cd nano
  vi cfg/tests.js
  npm install # should install ensure and async, if it doesnt install manually
  npm test

after adding a new test you can run it individually (with verbose output) using:

  NANO_ENV=testing node tests/doc/list.js list_doc_params

where list_doc_params is the test name.


              / _) ROAR! i'm a vegan!
       .-^^^-/ /
    __/       /
   /__.|_|-|_|     cannes est superb

(oO)--',- in caos