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

ie8linter

v0.0.3

Published

A little linter server to try to figure out why a page doesn't work in an old version of IE

Downloads

29

Readme

ie8linter

A little tool to lint websites for IE8 compatibility, with warnings for possible pitfalls and suggested fixes.

Screenshot

Unfortunately for some of us, there are still projects out there that require compatability with our friendly dinosaur IE8. For these special occasions I made this little linter. What it would do is spit all the usual suspects that cause incompatability and suggest fixes. Rather than scratch your head for hours about a missing navigation bar only to find you set an initial value on your position property in one of the multiple CSS files, just give it to the linter.

Right now this is still in development, but if you wanna see what it does already, git clone it, and then run npm install and then node main.js. It should be running on http://localhost:3000/.

Contributing

Feel free to contribute your "favorite" pitfall or bug in the issues section or as a pull request (as of now the source code isn't very heavily commented, sorry about that).

I'd love to hear about suggestions of common pitfalls, useful polyfills and problems you had with IE8 you wish would have been caught by a linter automatically

You can always drop me a line here: [email protected]