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

check-browser

v0.1.7

Published

Ultra-thin wrapper around bowser with simple declarative interface

Downloads

618

Readme

check-browser

Ultra-thin wrapper around bowser with simple declarative interface

Usage

check-browser takes a single argument, a map of browser names to minimum version numbers, and returns a boolean value indicating whether or not the current browser is equal to or greater than one of the allowed ones. The browser names it uses are the same as bowser's keys:

  • chrome
  • safari
  • msie
  • opera
  • seamonkey
  • blackberry
  • bada
  • tizen
  • sailfish
  • android
  • windowsphone
  • ios (iphone / ipad / ipod)
  • firefoxos
  • webos

(not all of these are browsers, I know, but they will all work)

You may also use the others property to toggle whitelist/blacklist behavior. If others is true, browsers not explicitly listed will be considered valid. others defaults to false.

check-browser is also forgiving about capitalization, chrome/Chrome/CHROME, are all acceptable.

Examples

checkBrowser({
  msie: 7,
  chrome: 10,
  firefox: 3
});
checkBrowser({chrome: 33}) // Returns false for Firefox
checkBrowser({chrome: 33, others: true}) // Returns true for Firefox