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

feature-detect

v1.0.0

Published

Feature detection library for node environments.

Downloads

17

Readme

Feature detection

This library is meant to provide feature detection support for Node.js or Io.js compatible environments. It is not intended to provide feature detection support in browser environments, for which there already are numerous alternatives.

Usage

npm install --save feature-detect

Install time detection (recommended)

To detect features at install time, put an install script similar to the following in package.json:

{ scripts:
  { "install": "feature-detect generators" }
}

In the example above, the feature-detect executable will load the module generators. The module is expected to export a list of tests, like so:

exports.feature = 'Generators'

exports.tests =
[ 'generator syntax'
  , function() {
      return function *() { yield true }
    }
  ]
]

When running npm install in an environment that supports generators, nothing will happen, but if generators aren't supported, the installation will fail and you should see output like the following:

WeakMap is not supported in this environment
├ ✘ basic functionality WeakMap is not defined
├ ✘ constructor arguments WeakMap is not defined
├ ✘ WeakMap.prototype.set returns this WeakMap is not defined
├ ✘ WeakMap.prototype.delete WeakMap is not defined
└ ✘ Support frozen objects as keys WeakMap is not defined

Runtime detection

While installation time detection is recommended, it is possible to do runtime detection:

var detect = require('feature-detect')

var result = detect(
  { feature: 'WeakMap'
  , tests:
    [ [ 'basic functionality', function() {
        var key = {};
        var weakmap = new WeakMap();
        weakmap.set(key, 123);
        return weakmap.has(key) && weakmap.get(key) === 123;
      } ]
    ]
  }
)

result.success? console.log('WeakMap supported!') : console.error('No WeakMap!')

License: MIT