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

@soulofmischief/bind-props

v1.1.8

Published

Bind each function property of an object to a new context.

Downloads

4

Readme

bind-props

build coverage size

About

This module binds each function property of an object to a new context. This is useful for defining class methods in separate files in order to reduce module size and increase code clarity.

Motivation

Modularity is awesome. Javascript classes aren't very modular. Classes methods must be defined inside the scope of the definition if they wish to inherit the class context! And the standard way for adding static methods doesn't work with namespaced methods.

bind-props helps to bring sanity back to your classes by allowing you to define large methods in separate files, namespacing them how you choose.

Private methods are achievable simply by using Function.prototype.call on a non-exported method with this while inside of any exported instance method.

Example

Test.js
import * as ctrl from './ctrl'

export class Test {
  constructor() { 
    super()
    this.message = 'Howdy!'
  }

  ctrl = bindProps( this, ctrl )
}
index.js
import { Test } from './Test'

Test.ctrl.test()

// -> Public: Howdy!
// -> Private: Howdy!

Test.ctrl.testPrivate()

// -> undefined
ctrl.js
export function test() {
  console.log( 'Public: ', this.message )
  testPrivate.call( this )
}

function testPrivate() {
  console.log( 'Private: ', this.value )
}