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

@medic/search

v1.1.1

Published

Our implemenation of search using (C|P)ouchDB views.

Downloads

2

Readme

Search

A shared library that uses CouchDB views to generate search results.

v1 API

You must initialise the library with a Promise library and a PouchDB DB:

const Search = require('search')(Promise, new PouchDB('foo'));

PouchDB needs access to at least map reduce and some kind of back-end (here HTTP):

const PouchDB = require('pouchdb-core');
PouchDB.plugin(require('pouchdb-adapter-http'));
PouchDB.plugin(require('pouchdb-mapreduce'));

You can then request search results for Reports and contacts:

Search('reports', {}, {limit: 50, skip: 0})
    .then(ids => {
        ...
    })

The first parameter is the type, the second parameter is the query params described in the sections below, and the third are options related to pagination.

Contacts

There is only one query option in contacts: search:

Search('contact', {search: "your search terms"})
    .then(ids => { ... })

These search terms are broken up and used on tokens pulled from contacts. Names, dobs, phone numbers etc.

Reports

Basic example of all the options:

{
  "forms": {
    "selected": [
      {
        "code": "confirm_death",
      },
      {
        "code": "delivery",
      },
      {
        "code": "immunization_visit",
      }
    ],
  },
  "facilities": {
    "selected": [
      "665e98ef-8fdf-43ba-90aa-1fd422daaa5b",
      "bf99cec0-a0eb-4f77-a557-d2fe2c694b94"
    ],
  },
  "date": {
    "from": 1517443200000,
    "to": 1518825599999
  },
  "valid": true,
  "verified": true,
  "search": "your search terms"
}

forms.selected is an array of {code: "foo"} objects where foo is the form code.

facilities.selected is an array of _id values for those facilities.

date.from and date.to are outputs from Date.getTime(): the number of milliseconds since Jan 1st 1970 UTC.

valid is whether or not the forms returned are forms without errors (undefined means either).

verified is whether or not the forms returns have been validated (undefined means either).

search follows the same logic as for contacts, but for data in reports.