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

hermanjs

v1.0.3

Published

Singleton models with Backbone and possibly other frameworks

Downloads

5

Readme

Request for Comments

###This project solves problems of

boilerplate
// for example you have collection/users.js
return Backbone.Collection.extend({
  url: '/api/users',
});

// and collection/things.js
return Backbone.Collection.extend({
  url: '/api/things'
});

// and model/thing.js
return Backbone.Model.extend({
  url: '/api/thing'
});

// file-that-uses-things.js
var Things = require('./collection/things.js'),
  things = new Things();
  
// file-that-uses-thing.js
var Things = require('./model/things.js'),
  things = new Thing({
    id: maybeId
  });

You get the idea, this is called boilerplate. This project simplifies your model layer at the cost of flexibility in terms of custom code.

// api.js
return new M({
  prefix: '/api',
  resources: {
    user: 'any',
    thing: 'any' // model/collection defenition
  }
})

// file-that-uses-things.js
var api = require('./api.js'),
  things = api.things().collection(); // returns an instance

// file-that-uses-thing.js
var api = require('./api.js'),
  things = api.thing(maybeId).model();
synchronisation and singleton management
// usually you would have a manager kind of thing, that would keep track of your instances
// manager.js
var Things = require('./collection/things.js'),
  things = new Things();
return {
  things: things
};
// file-that-uses-things.js
var manager = require('./manager.js'),
  things = manager.things;
// file-that-uses-thing.js
var manager = require('./manager.js'),
  things = manager.things,
  thing = things.find(function (thing) {
    return thing.id === maybeId;
  }); 

Regarding that last part, things may not be up to date and have no such item. If you create a separate model, but then there is again the sync question. It's a slippery slope. This project manages sigletons for you.

// file-that-uses-things.js
var api = require('./api.js'),
  things = api.things().collection();

// file-that-uses-thing.js
var api = require('./api.js'),
  thing = api.thing(maybeId).model();

If things has an item with such id, then it would be the same reference. If things would then be fetched, and got the new thing, it would be the same reference.

schema mappings

If you are uncofortable with your schema, because it involves

  • odd to javascript naming conventions like_this or
  • it.is.very.unnecessary.deeply.nested or
  • it['com.this.like.gems.has'] or
  • it has abbrs instead of readable abbreviations
GET /api/things/1
[{
  "id": 1,
  "integrated_services": [],
  "details": {
    "fullName": "thingie",
    "prc": 0.99
  }
}]

in Backbone you would

// and model/thing.js
return Backbone.Model.extend({
  url: '/api/thing',
  parse: function (object) {
    return {
      price: object.details.prc,
      name: object.details.fullName,
      integratedServices: object.integrated_services;
    };
  } // yet it does not solve the problem of converting it backwards for update
});

// and collection/things.js
var Thing = require('./model/thing.js');
return Backbone.Collection.extend({
  url: '/api/things',
  model: Thing
}); // now you have to mention your custom model, because it's not generic

Or you could just

// api.js
return new M({
  prefix: '/api',
  resources: {
    user: {
      _shortcutMappings: {
        price: ['details', 'prc'],
        name: ['details', 'name'],
        integratedServices: ['integrated_services']
      }
    },
    thing: 'any'
  }
})

This will intercept all gets/sets and correct the keys.

###Features

  • models with defined ids are singletons
  • once id changes (ex. current user is fetched) the model will be tied to an existing model with same id
  • collections also point to singleton models, thus sync is free
  • sort of type validation
  • adaptation to other (than backbone) framework's models is possible

###How to Use

// m-for-my-api.js
define(['m-for-backbone'], function (m) {
  return M({
    prefix: '/rest/v37',
    resources: {
      account: 'any',
      group: 'array of users',
      user: {
        id: 'number',
        name: 'string',
        email: 'email',
        attributes: 'array of objects',
        _attributeMappings: {
          language: 'com.m.lang'
        },
        _shortcutMappings: {
          isAdmin: ['association', 'flags', 'com.m.administrator']
        }
      }

    }
  });
});
// current-group-mvwhaterver.js
var m = require('m-for-my-api.js');
var usersInMyGroup = m.group().users({limit: 10}).collection();
// selected-user-mvwhaterver.js
var m = require('m-for-my-api.js');
var user = m.user(selectedId).model();
// current-user-mvwhaterver.js
var m = require('m-for-my-api.js');
var me = m.user().model();
me.set('language', 'ru')
me.set('isAdmin', true)
//  {
//    id: 1,
//    name: 'Herman Starikov',
//    attributes: [{
//      name: 'com.m.lang',
//      value: 'ru'
//    }],
//    association: {
//      flags: {
//        'com.m.administrator': 'true'
//      }
//    }
//  }