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

knockout-refs

v1.0.1

Published

knockout ref binding inspired by React refs

Downloads

3

Readme

Knockout refs

Knockout, by default, does not give a way to access child components from their parents. This is sometimes desireble. This simple knockout plugin solves this problem in a similar way that React does.

Usage

On your child component element define a ref:

<div data-bind="click: callback">
  <child data-bind="ref: 'child'></child>
</div>

Then the instance governing the <child> element you can find in ko.bindingHandlers.ref.refs (or if you use browserify const refs = require("knockout-refs"));

In this example it will be ko.unwrap(ko.bindingHandlers.ref.refs.child).
References are packed inside an observable, and you can subscribe to it, the instance will change, whenever the component governing the child will change ( this might be useful, when you use some kind of routing that change the component of the top most element).

Note that references are created after parent is instantiated, so you cannot access them when parent component's custructor is called (as in React, where you cannot access refs in render method).

There is also refFn binding which accepts as its arguments an object {ref: string: callback: function}. The callback is called asynchronously, since first knockout has to instantiate all the children which is after the parent is instantiated. Sinve refFn controls descendant bindings you cannot use on any other element that does the same, for example on any other element which has a component binding (e.g. a knockout custom element).

Final remarks

Often by moving 'state' up the component tree you can avoid using this approach, though sometimes a cleaner approach is to have some public methods on the child accessible by the parent.