CanIUse Command Line

By  on  

Every front-end developer should be well acquainted with CanIUse, the website that lets you view browser support for browser features.  When people criticize my blog posts for not detailing browser support for features within the post, I tell them to check CanIUse:  always up to date, unlike posts on any blog.  While I know to use the CanIUse website, I recently found out that Sam Gentle has an accompanying Node.js CanIUse module for looking up browser support.

To install the utility, use a typical npm install command:

# Install globally for less hassle
npm install -g caniuse-cmd

With the caniuse command available, you can look up feature support from the command line:

CanIUse

CanIUse

The display of results is pretty and it provides a listing of different matching features if the lookup is vague.  And because we can get this information in an automated way, you can probably write a decent scraper with cURL and other tools.

Recent Features

Incredible Demos

  • By
    MooTools Zebra Table Plugin

    I released my first MooTools class over a year ago. It was a really minimalistic approach to zebra tables and a great first class to write. I took some time to update and improve the class. The XHTML You may have as many tables as...

  • By
    Digg-Style Dynamic Share Widget Using MooTools

    I've always seen Digg as a very progressive website. Digg uses experimental, ajaxified methods for comments and mission-critical functions. One nice touch Digg has added to their website is their hover share widget. Here's how to implement that functionality on your site...

Discussion

  1. Steve

    I need to get this hooked up to be an email responder bot! “Hey Steve does ${browserX} support ${featureY}?” => auto respond ;-)

  2. Dominik

    How about just adding canIuse as a search engine to your browser, like so http://caniuse.com/#search=%s?
    Simply typing “c webp” into my browser gives me even nicer formatted results.

  3. Sadly the output is not very useful for automated processing. It would’ve been nice if this could be implemented in a gulp-task, scanning CSS for a defined set of supported browsers, and if a css-declaration wasn’t supported it would throw an error.
    But as your example of ‘transform’ shows, it returns things like JPEG2000, so output parsing is required and tedious. Plus it seems that there is no option to print a simple boolean instead of fancy ticks and crosses.

  4. Definitely an interesting article about this new npm tool, useful for those who like command line better then gui.

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!