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

@webreflection/interface

v0.1.1

Published

Simple interfaces for modern JavaScript.

Downloads

580

Readme

interface Build Status Coverage Status

Simple interfaces for modern JavaScript.

npm -i @webreflection/interface

API

There are two functions usable through Object or any Function.prototype:

  • Object.interface([iFace, ...iFace, ]{object: 'literal'}) to defines left to right interfaces properties on top of the newly created interface
  • Object.implements(iFace[, ...iFace]) to create a new object that implements all interfaces (still left to right)

Both methods can be also used to define classes:

  • Function.interface([iFace, ...iFace, ]class {}) to defines left to right classes implementing the optional list of previous interfaces as parameters
  • class extends AnyClass.implements(iFace[, ...iFace]) to create a new intermediate class that implements all interfaces (still left to right)

Peculiarities

  • all interfaces properties and symbols are forced as non enumerable
  • all interfaces are created through the same internal class with a null object as prototype

Last point means that objects interfaces do not have toString methods or constructors. These are indeed meant to be used as interfaces only, not as generic objects.

Example

// Function.prototype polluted, deal with it!
require('@webreflection/interface');

// an interface is just an object
// carrying some definition that can be implemented
// through other objects or classes
const EventListener = Object.interface({
  handleEvent(e) { this['on' + e.type](e); }
});

// but it can be defined through a class too
// in such case you can even new EventListener
// or directly extends EventListener
const EventListener = Function.interface(class {
  handleEvent(e) { this['on' + e.type](e); }
});

// a simple clicker class (it could directly extends EventListener too)
class Clicker {
  constructor() { super(); this.clicks = 0; }
  onclick(e) {
    e.preventDefault();
    console.log(`You clicked me ${++this.clicks} times`);
  }
}

// a BasicClicker that extends Clicker and implements EventListener
class BasicClicker extends Clicker.implements(EventListener) {
  constructor(node) {
    super();
    node.addEventListener('click', this);
  }
}

new BasicClicker(document.documentElement);