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

merstone

v0.1.1

Published

A data model

Downloads

500

Readme

Merstone

NPM

Build Status

A data-model abstraction. This is a base class for models. You can construct one if all you want to do is observe some data, or you can extend it if you want that and more.

If you have used Backbone before, Merstone models will be familiar to you. The main difference is that where Backbone models are "active record"-like, i.e. they correspond to an API and deal with persistence, Merstone models are not. They don't have any functionality pertaining to persistence at all. They are intended to be used in a service oriented architecture, i.e you call model.toJSON() and pass that to a service for persistence. This allows greater flexibility, but still allows you to extend the models and build in behaviour like save() and fetch() should you wish.

Merstone models inherit their eventy behaviour from node event emitter.

Installation

npm install --save merstone

Usage

//
// Constructor
//

var Model = require('merstone')
  , m = new Model(serviceLocator, {})

//
// Getting, setting and resetting
//

m.get('name')

m.set('name', 'Ben')
m.set({ firstName: 'Ben', lastName: 'Gourley'})

m.reset({ firstName: 'Cara', lastName: 'Haines'})

//
// Events
//

m.on('change', function (model) {
  console.log('An attribute changed on model ' + model.id)
})

m.on('change:name', function (value, model) {
  console.log('Name attribute is now ' + value + ' on model ' + model.id)
})

m.on('reset', function (model) {
  console.log('model ' + model.id + ' attributes were reset')
})

//
// Serialisation
//

// Creates a deep clone of the model's attributes
m.toJSON()

//
// Hooks
//

// 'preSet'
// These hooks are run on .set() before the model attributes are updated
// Accepting raw user input? Maybe you want to do some type casting…

m.hook('preSet', castNumbers)

function castNumbers(attributes, cb) {
  // Do something to the attributes
  if (attributes.age) attributes.age = parseInt(attributes.age, 10)
  cb(null, attributes)
}

Extending Merstone for your own models

Merstone doesn't do any fancy extend-y stuff, you just use built-in JS prototypal inheritence methods.

module.exports = ClockModel

var Model = require('merstone')

function ClockModel(serviceLocator, attributes) {
  // Call the model constructor
  Model.apply(this, arguments)
}

// Set the object prototype
ClockModel.prototype = Object.create(Model.prototype)

// Now add custom methods to the new prototype

ClockModel.prototype.tick = function () {
  console.log('tick')
}

ClockModel.prototype.tock = function () {
  console.log('tock')
}
var ClockModel = require('./clock-model')
  , m = new ClockModel(serviceLocator)

The name?

I've made a bunch of MVC-like components. I named each one after villages on the Isle of Wight (where I live) beginning with the same letter as the thing it represents.

See also Ventnor views and Chale collections.

Credits

Licence

Copyright (c) 2014, Ben Gourley

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.