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

view-manager

v0.1.0

Published

couchbase-view-manager ======================

Downloads

8

Readme

couchbase-view-manager

A View Manager for CouchBase written in Node.JS

Usage

Usage: node ./view_manager.js -u [str] -p [str] -D [dir] [opts] --force --update

Options:
  -p, --bucket-password  [default: ""]
  -H, --host             [default: "127.0.0.1:8091"]
  -D, --directory        [default: "views"]
  --dev                  [default: false]
  -l, --list             [default: null]
  -e, --no-eval          [default: false]
  -b, --bucket           [default: null]
  -d, --design           [default: null]
  -v, --view             [default: false]
  -f, --force            [default: false]
  -u, --update           [default: false]
  -h, --help             [default: false]
  -V, --version          [default: false]

View Directory

Example with 2 buckets (user and images), and 2 designs for user (info, stats).

$ ls -lR
-rw-r--r-- 1 nico nico 7,0K mai   28 16:45 view_manager.js

./views:
total 8,0K
drwxr-xr-x 2 nico nico 4,0K mai   28 16:54 images
drwxr-xr-x 4 nico nico 4,0K mai   28 17:03 user

./views/images:
total 0

./views/user:
total 8,0K
drwxr-xr-x 2 nico nico 4,0K mai   28 17:03 info
drwxr-xr-x 2 nico nico 4,0K mai   28 17:00 stats

./views/user/info:
total 0

./views/user/stats:
total 0
-rw-r--r-- 1 nico nico 0 mai   28 17:00 aggreg.map.js
-rw-r--r-- 1 nico nico 0 mai   28 17:00 aggreg.reduce.js

To push the view aggreg

Syntax

You have to follow some rules:

| | map function | reduce function | |-----------|------------|----------| | naming | aggreg.map.js | aggreg.reduce.js | | required | yes | no | | syntax | javascript function(doc, meta) {/*...*/} | _count or javascript function(key, values, rereduce) {/*...*/}

Command line

first push

$ node ./view_manager.js -b user -d stats -v aggreg
users/stats/aggreg                                  created

view already exists

$ node ./view_manager.js -b user -d stats -v aggreg
users/stats/aggreg                                  not changed

view already exists, and your local version has changed

$ node ./view_manager.js -b user -d stats -v aggreg
users/stats/aggreg                                  changed but not updated

You have to precise the --update option.

$ node ./view_manager.js -b user -d stats -v aggreg --update
users/stats/aggreg                                  updated

with --force, all views are pushed without verification.

Evaluation

The -e option (default to true) and stops sending if your view is not a valid JS.

Dev

The dev option (default to false) push views on the dev design. Else on the prod one.