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

v1.1.0

Published

Granular Feature Detection for Browsers

Downloads

971

Readme

feature

Feature-detection at a highly targeted level.

NPM

browser support

unstable bitHound Score

What about Modernizr?

Modernizr is wonderful, no doubt about it. It is however, pretty massive and while it can be whittled down to a smaller size using customization from the download page, I'm just a bit too lazy for that.

By leveraging Browserify's excellent static analysis (powered by esprima), when feature is used within an application in a selective way, only the targeted feature detection is included in the resultant JS file.

So if I was to write the following require:

var fullscreen = require('feature/fullscreen');

Then only the fullscreen code from feature would be included in my application. All the rest of the module would simply be ignored. So that's why. It's purely selfish, and well you should feel free to keep on using Modernizr.

Reference

css(prop)

Test for the prescence of the specified CSS property (in all it's possible browser prefixed variants). The returned function (if we are able to access the required style property) is both a getter and setter function for when given an element.

Consider the following example, with regards to CSS transforms:

var transform = require('feature/css')('transform');
var crel = require('crel');
var el = crel('div', 'test');

// if we have transforms available, then apply one
if (transform) {
  transform(el, 'translate(500px, 100px)');
}

// add the test div to the document
document.body.appendChild(el);

// log out the el position
console.log(el.getBoundingClientRect().left);
// ~~> 508

detect

The core functionality of the feature module is powered by the detect function, which can be imported like so:

var detect = require('feature/detect');

Once you have the detect function available you can do nifty things like detect whether your browser supports requestAnimationFrame:

var raf = require('feature/detect')('requestAnimationFrame');

function logRandom() {
  console.log(Math.random());
  raf(logRandom);
}

// create a requestAnimationFrame fallback
raf = raf || function(fn) {
  setTimeout(fn, 1000 / 60);
};

// start logging random numbers (for some reason...)
logRandom();

If it does then raf will be a function that is equivalent to the browser prefixed requestAnimationFrame function (e.g. webkitRequestAnimationFrame). It should be noted that feature does nothing to try and polyfill things that don't exist, that is left to you to implement yourself.

fullscreen

If the Fullscreen API is available this will allow you to fullscreen either the document or a target element.

var fullscreen = require('feature/fullscreen');

if (fullscreen) {
  fullscreen();
}

Additionally, the function can be passed directly to an event handler and the function will fullscreen just the selected element. This is useful in the case of videos, images, etc.

var fullscreen = require('feature/fullscreen');
var crel = require('crel');
var img = crel('img', {
  src: 'http://upload.wikimedia.org/wikipedia/commons/d/d3/Jim_jim_falls.jpg',
});

img.addEventListener('click', fullscreen);

document.body.appendChild(img);

License(s)

ISC

Copyright (c) 2016, Damon Oehlman [email protected]

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.