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

postcss-ie11-supports

v0.1.3

Published

PostCSS plugin adding "@supports not" support for IE 11

Downloads

2,387

Readme

postcss-ie11-supports Build Status

PostCSS plugin adding @supports not support for IE 11.

The plugin makes IE skip all @supports blocks but apply all @supports not ones. Since @supports is generally used for APIs newer than IE 11 this is an acceptable solution.

The way it does this is by prepending a selector understood by IE 11 only to the existing selector, making all other browsers ignore this rule.

Example input:

@supports (display: grid) {
    .box {
        /* Grid styles, applied to modern browsers. */
    }
}
@supports not (display: grid) {
    .box {
        /* Fallback styles, applied to older browsers, including IE 11. */
    }
}

Example output:

@supports (display: grid) {
    .box {
        /* Grid styles, applied to modern browsers. */
    }
}
@supports not (display: grid) {
    .box {
        /* Fallback styles, applied to older browsers, including IE 11. */
    }
}
_:-ms-fullscreen, .box {
    /* Fallback styles, applied to older browsers, including IE 11. */
}

Usage

postcss([
    require('postcss-ie11-supports'),
])

Advanced usage

This plugin relies on a behavior of CSS that if browsers don't recognize a certain selector they drop the whole rule even if other selectors after the unrecognized one match. The default selector used, '_:-ms-fullscreen', is recognized only by IE 11. You can change it to a different one that is recognized by other browsers by passing a ieSelector option, e.g.:

postcss([
    require('postcss-ie11-supports')({
        ieSelector: '_:-ms-lang(x)',
    }),
])

will match IE 10 and 11. Note, however, that IE 10 support is not official so bugs affecting only that browser (and not affecting IE 11) may not be fixed.

See PostCSS docs for examples for your environment.