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

@mavega/oloo

v2.3.1

Published

Add OLOO pattern properly in project. Makes sure prototype is set properly so inheritance just works. No binding needed.

Downloads

130

Readme

OLOO

Use OLOO pattern. Check out VSC extensions by LearnGameDevelopment to have syntax highlighting.

Why to use this module.

Objects Linked to Other Objects Article

Examples

Using Oloo.assign

const { setup } = require('@mavega/oloo');
setup();

const Object1 = {
  create() {
    const object1 = Object.create(Object1);

    object1.var = 0;
    object1.var2 = 'hi';

    return object1;
  },

  virtualMethod() {
    console.log('Base Class!');
  }
}

const Object2 = {
  create() {
    const object2 = Oloo.assign(Object1.create(), Object2);
    return object2;
  },

  virtualMethod() {
    Oloo.base(this, this.virtualMethod);
    console.log('Inherited Class!');
  }
}

const object2Instance = Object2.create();
object2Instance.virtualMethod();
// Base Class!
// Inherited Class!

Using Oloo.assignSlow + Oloo.createSlow

const { setup } = require('@mavega/oloo');
setup();

const Object1 = {
  create() {
    // must use createSlow in the first object of the chain.
    const object1 = Oloo.createSlow(Object1);

    object1.var = 0;
    object1.var2 = 'hi';

    return object1;
  },

  virtualMethod() {
    console.log('Base Class!');
  }
}

const Object2 = {
  create() {
    const object2 = Oloo.assignSlow(Object1.create(), Object2);
    return object2;
  },

  virtualMethod() {
    Oloo.base(this, this.virtualMethod);
    console.log('Inherited Class!');
  }
}

const object2Instance = Object2.create();
object2Instance.virtualMethod();
// Base Class!
// Inherited Class!

Release Notes

2.3.0+

  • Added documentation for all the methods.
  • Changed Base call so that you don't have to specify the funcName. Added a back up baseFunc incase you want to deliberately pass name for speed.

2.2.0+

  • Got rid of parent field on objects, we keep track of the parent throughout the life of the method call and then remove it.
    • In the past we use to inject parent into objects to know if we already called a method on the parent. Now we don't.
  • Improved error handling.

2.1.0+

  • Improved speed tremendously. Kept older assign as assignSlow for creating classes that don't get created often.
  • Added debugging capabilities.
    • If you add a displayName to your Obj we will make sure it appears in the Stack Trace.
    • Check to make sure displayName is a function name. Also consider compiling out displayName with Babel.