8.0.1 • Public • Published

PouchDB Collate semver non-compliant

Collation functions for PouchDB map/reduce. Used by PouchDB map/reduce to maintain consistent CouchDB collation ordering.

The PouchDB Collate API is not exposed by PouchDB itself, but if you'd like to use it in your own projects, it's pretty small, and it has a few functions you may find useful.


npm install pouchdb-collate
var pouchCollate = require('pouchdb-collate');

Warning: semver-free zone!

This package is conceptually an internal API used by PouchDB or its plugins. It does not follow semantic versioning (semver), and rather its version is pegged to PouchDB's. Use exact versions when installing, e.g. with --save-exact.


PouchDB and its sub-packages are distributed as a monorepo.

For a full list of packages, see the GitHub source.



This is probably the most useful function in PouchDB Collate. It converts any object to a serialized string that maintains proper CouchDB collation ordering in both PouchDB and CouchDB (ignoring some subtleties with ICU string ordering in CouchDB vs. ASCII string ordering in PouchDB).

So for example, if you want to sort your documents by many properties in an array, you can do e.g.:

var pouchCollate = require('pouchdb-collate');
var myDoc = {
  firstName: 'Scrooge',
  lastName: 'McDuck',
  age: 67,
  male: true
// sort by age, then gender, then last name, then first name
myDoc._id = pouchCollate.toIndexableString(
  [myDoc.age, myDoc.male, mydoc.lastName, mydoc.firstName]);

The doc ID will be:


Which is of course totally not human-readable, but it'll sort everything correctly (floats, booleans, ints – you name it). If you need a human-readable doc ID, check out the DocURI project.

Warning! If you are syncing or storing docs in CouchDB, then you will need to modify these doc IDs, due to a bug in how Chrome parses URLs, which causes problems in the replicator when it tries to GET docs at those URLs.

In short, you will need to replace all the \u0000 characters with some other separator. Assuming you're storing text data and not binary data, \u0001 should be fine:

pouchCollate.toIndexableString([/* ... */])
    .replace(/\u0000/g, '\u0001');


Same as the above, but in reverse. Given an indexable string, it'll give you back a structured object.

For instance:

var pouchCollate = require('pouchdb-collate');

// [ 67, true, 'McDuck', 'Scrooge' ]

collate(obj1, obj2)

Give it two objects, and it'll return a number comparing them. For example:

pouchCollate.collate('foo', 'bar'); // 1
pouchCollate.collate('bar', 'foo'); // -1
pouchCollate.collate('foo', 'foo'); // 0

Of course it sorts more than just strings - any valid JavaScript object is sortable.


You shouldn't need to use this, but this function will normalize the object and return what CouchDB would expect - e.g. undefined becomes null, and Dates become date.toJSON(). It's basically what you would get if you called:


but a bit faster.

Package Sidebar


DownloadsWeekly Downloads






Unpacked Size

36.2 kB

Total Files


Last publish


  • jcoglan
  • albaherreriasdev
  • jan
  • daleharvey
  • pouchdb-user
  • garethbowen
  • garrensmith
  • nolanlawson
  • cwmma
  • willholley