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

@twilson63/palmetto-couchdb

v1.0.5

Published

An adapter to use couchdb as the append only log in palmetto flow

Downloads

6

Readme

palmetto couchdb adapter

An adapter to use couchdb as the append only log in palmetto flow

Build Status

Usage

The palmetto flow adapter allows both the client and service to keep their code abstracted to the the pub/sub implementation so that the pub/sub implementations can be swapped out and not affect the service or client, they both have to to point to the same pub/sub service inorder to work, but this gives great flexibility in changing out components or parts of the application with different technologies.

Client Example:

var palmetto = require('palmetto-couchdb')
var ee = palmetto({
  endpoint: 'http://localhost:5984',
  app: 'app_log'
})

app.get('/foo', function (req, res) {
  ee.once('1234', function (e) {
    // handle response
    res.writeHead(200, { 'content-type': 'application/json'})
    res.end(e.object)
  })  
  ee.emit('send', {
    to: '/domain/service/action',
    from: '1234',
    subject: 'service',
    verb: 'action',
    object: req.params,
    dateSubmitted: moment().utc().format()
  })
})

Service Example:

// container

require('health-server')
var palmetto = require('palmetto-couchdb')
var ee = palmetto({
  endpoint: 'http://localhost:5984',
  app: 'app_log'
})

svc(ee)

// service

module.exports = function (ee) {
  ee.on('/domain/service/action', function (e) {
    // validate e.object using json-schema
    // do serivce stuff
    ee.emit('send', {
      to: e.from,
      from: '/domain/service/action',
      subject: e.subject + '-response',
      verb: e.verb + '-response',
      object: result,
      ...
    })
  })
}

[see tests]

## Test

npm test



More docs coming soon.