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 🙏

© 2026 – Pkg Stats / Ryan Hefner

not-for-ie

v0.9.2

Published

A mini-library to declare that your web application is not designed to run in Internet Explorer

Readme

not-for-ie

npm version npm downloads License
Build Status Code Climate js-myterminal-style Coverage Status
NPM

A mini-library to declare that your web application is not designed to run in Internet Explorer

Features

  • Appends a specified CSS class to HTML body on activation
  • Provides a method to detect IE

How to Use

Directly from a web page

One can use not-for-ie directly from a web-page by attaching the not-for-ie.js and not-for-ie.css to the DOM.

<!-- Attaching the not-for-ie script -->
<script type="text/javascript" src="path/to/library/not-for-ie.js"></script>

<!-- Usage -->
<script type="text/javascript">
    notForIe.activate('ie');
</script>

With Webpack, Browserify or RequireJS

Install not-for-ie from NPM

npm install not-for-ie --save-dev

Consume as an ES6 module

import * as notForIe from 'not-for-ie';

or

import { isIe } from 'not-for-ie';

Consume as a CommonJS module

var notForIe = require('not-for-ie');

Consume as an AMD

require(['not-for-ie'], function (notForIe) {
    // Consume notForIe
}

Note: You may have to use Babel for ES6 transpilation.

Methods

activate

Appends the specified CSS class to the HTML body element.

notForIe.activate('ie');

isIe

Determines whether the application is known to be running within Internet Explorer.

if (notForIe.isIe()) {
    // Running within IE
}

Demo

You can view a demo here.

To-do

  • Write unit-tests