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

mi

v1.0.0

Published

The simplest and most obvious way to use multiple inheritance in Javascript that I could think of.

Downloads

120

Readme

Mi

Mi is the simplest and most obvious way to use multiple inheritance in Javascript that I can think of. Constructor functions are created the same way, prototype properties and methods are still created the same way, and instances are created the same way.

API

Both of these functions can be called as-is like so:

function Constructor() {}
function SubClass() {}

mi.inherit(SubClass, Constructor)

or assigned to the super-most class, and called thusly:

function Constructor() {}
function SubClass() {}

Constructor.inherit = mi.inherit

Constructor.inherit(SubClass)
  • mi.inherit grants prototypical inheritance just like util.inherits. In fact, it calls util.inherits, so the behaviour should be near-identical. The only difference is "static" methods; those defined as Constructor.doIt. Those aren't inherited as SubClass.doIt with util, but they are with mi.

  • mi.extend grants "parasitical" or "mixin" inheritance much like dotmixin, nmix, and others. Unlike mi.inherit, util.inherits is not used, and typical, prototypical inheritance will not occur. Instead, the prototype of the "subclass" will have all prototype methods of the "superclass" injected into itself.

Notes

  • You still have to call Constructor.call(this) in the "subclass" contructor, just as you would normally.
  • You still have to call Constructor.prototype.doIt.call(this, ...) in the "subclass"'s doIt method, just as you would normally.
  • Notice a pattern?

License

Copyright (C) 2013 Michael Schoonmaker ([email protected])

This project is free software released under the MIT/X11 license:

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.