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

dom-tools

v0.1.4

Published

A tiny collection of DOM helpers for IE8+.

Readme

dom-tools

A lightweight, tiny collection of DOM Helpers for IE8+. The API attempts to mirror much of jQuery's API. (e.g. DOMUtils.css(el, 'height') -> $(el).css('height'))

This library is just naive wrappers around common DOM API inconsistencies. Cross browser work is minial and mostly taken from jQuery and react-bootstrap/dom-helpers. If you need robust cross-browser support, you should use jQuery instead.

This library does not put a lot of effort to normalize behavior across browsers. Instead it seeks to provide a common interface and help reduce boilerplate code for having to check if (IE8).

For example, DOMTools.addEventListener works in all browsers IE8+. Otherwise you'd be writing:

if (document.addEventListener) {
  element.addEventListener(eventType, handler);
} else if (document.attachEvent) {
  element.attachEvent('on' + eventType, handler);
}

One advantage of this collection is that any method can be required individually. If you use build tools such as Browserify or Webpack, it will only include the exact methods you use. This is great for when environments where jQuery doesn't make sense, or is not a requirement, such as React where you only occasionally need to do direct DOM manipulations.

Installation

Using npm:

npm install dom-tools --save

Using as inline <script> tag

Just include the dom-tools.js or dom-tools.min.js file.

Basic usage

Template:

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <title>DOMTools: Basic usage</title>
  <style>
  #foo {
    height: 50px;
    passing: 5px;
    margin: 5px;
  }
  </style>
</head>
<body>
  <div id="foo" style="margin-right: 5px; border: 1px solid #333;">bar</div>
</body>
</html>

Inline <script> tag

<script src="dom-tools.js"></script>
<script>
  var foo = document.getElementById('foo');
  
  console.log(DOMTools.css(foo, 'width'));
  console.log(DOMTools.css(foo, 'height'));
  console.log(DOMTools.outerWidth(foo, true));
  console.log(DOMTools.outerWidth(foo, false));
  // 1491px
  // 50px
  // 1503
  // 1493
</script>

CommonJS:

var DOMTools = require('dom-tools');

var foo = document.getElementById('foo');

console.log(DOMTools.css(foo, 'width'));
console.log(DOMTools.css(foo, 'height'));
console.log(DOMTools.outerWidth(foo, true));
console.log(DOMTools.outerWidth(foo, false));
// 1491px
// 50px
// 1503
// 1493

API

@todo:

What's next?

  1. Create tests
  2. Complete API documentation
  3. Add additional methods