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

result-type

v1.0.0

Published

nothing but a Result type

Downloads

762

Readme

result-type

Just an empty class to use as a kind of tag. If your implementing something you consider to be a "Result" you can inherit from it and enjoy nice reliable type detection via instanceof. This would normally be too limited but in the case of Result implementations should be fine. Its probably a bad idea anyway though since module systems like npm can easily duplicate modules but fuck it lets see if it works with better package managers.

Installation

This form of type checking relies on identity. That means every module that dependends on it must load the exact same path.

With component

$ component install jkroso/result-type

With packin

$ packin install result-type:http://github.com/jkroso/result-type/tarball/1.0.0

With npm

$ echo "good luck" && npm install result-type

then in your app:

inherit(MyResultClass, require('result-type'))