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

mobx-pouchdb

v1.4.3

Published

MobX'd PouchDB connections

Downloads

11

Readme

WIP Docs - https://robertinglin.gitbooks.io/mobx-pouchdb/content/

mobx-pouchdb

Links MobX observers with PouchDB, allowing simple rapid development and persistant state

Classes

mobx-pouchdb has 2 classes. Model, and ModelStore

Model

Basic model scaffolding. Exposes edit actions to modify doc state without changing the doc until saving.

Functions

  • generateId - id generation - defaults to shortid
  • save - writes any edits directly to the document
  • toJS - converts the MobX model back to a JS object for PouchDB write. Also used to remove properties that shouldn't be written to Pouch
  • setE - Sets an edited parameter in temporary storage
  • getE - Gets the parameter from temporary storage or the base object if it isn't in temp
  • clearE - clears all temporary parmeters, reverting state

Big E

Instead of using getE & setE, temp storage can be accessed directly through the E property. Just like getE, if the property hasn't been written to E before it will pull the value from the base model.


const todo = new ToDoModel('Something to do');
console.log(todo.title, todo.E.title);
//  prints 'Something to do', 'Something to do'

todo.E.title = 'E temporary storage example'
console.log(todo.title, todo.E.title);
// prints 'Something to do', 'E temporary storage example'

todo.save();
console.log(todo.title, todo.E.title);
// prints 'E temporary storage example', 'E temporary storage example'

Saving to PouchDB

If using Big E for your edits you can set the following save function to only save to pouch when there's edits.


save() {
    if (super.save()) {
        POUCH_DB_INSTANCE.put(this.toJS());
    }
}

ModelStore

Workhorse of mobx-pouchdb, ModelStore links the Model class and the pouchdb instance

Functions

  • load(documentId, pouchDbGetSettings) - takes a documentId and either returns the in memory stored doc or pulls the doc from PouchDb
  • loadAll(pouchDbAllDocsSettings) - Queries PouchDB for all documents and stores them in memory
  • get(documentId) - takes a documentId and either returns the in memory stored doc or null if not in memory
  • add(Model) - writes a model to the store and then tracks that model in memory
  • query(mapFunction, options) - takes a pouchdb query (currently only map function), as well as search parameters and returns the resulting query docs
  • removeQuery - if the query is "live", it can be removed when it's done being used. That way it doesn't continue to be tracked on PouchDB changes