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

dtektor

v0.1.4

Published

A module to detect client side browser capabilities, heavily inspired in modernizr but with tests written as commonJS modules.

Downloads

4

Readme

NPM Version Build Status

dtektor

A module to detect client side browser capabilities, heavily inspired in modernizr but with tests written as commonJS modules.

Important:

This is intended to be use with browserify, since it uses browserify transforms:

  • shimixify
  • require-globify
  • babelify

Install

npm i --save dtektor

Usage

// hard way to use it
var dtektor = require('dtektor')({
  touch: require('dtektor/f/touch'),
  fullscreen: require('dtektor/f/fullscreen'),
  // this is a custom test implemented in your app
  // dash separated keys will be transformed to
  // camelCase ones on the returned object
  'another-test': require('./lib/custom-tests')
});

// the keys that contain dashes
// are converted to camelCase ones
dtektor.anotherTest

// also the html element will have the classes:
// - touch, if touch is supported or no-touch if not supported
// - fullscreen, if fullscreen is supported or no-fullscreen if not supported
// - another-test, if the custom test exports a boolean === true or
//   no-another-test if the exported value is false

Load all the tests included in this module

// for now only tests for fullscreen, hover-enabled and touch
// ideally all the tests in the modernizr repo could be moved to commonjs
// modules and can be imported here but this should be only done for dev purposes
// TODO: Add more modernizr tests to the p/ folder (f stands for features)
var dtektor = require('dtektor/all');

Customize the tests

// In a real life app you should only load the tests you use
// this can be achieved by doing:
//
var dtektor = require('dtektor')(
  // this uses the transform require-globify
  // this will load only touch and fullscreen
  // other tests can be added as well when they
  // become available
  require('./node_modules/dtektor/p/{touch,fullscreen}.js', { mode: 'hash'})
);

// or you can load your own tests
var dtektor = require('dtektor')(
  require('./custom-tests/**/*.js', { mode: 'hash'}) // this will expand your tests
)

License

MIT

Changelog

Changelog