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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@sandboxed/unitjs

v2.2.1

Published

UnitJS follows the `Revealing Module Pattern`. Easy to use DOM manipulation light-weight library

Readme

UnitJS v2.0.0 CI

About

UnitJS is a personal project I've been developing over the years. It follows the Revealing Module Pattern along with the IIFE Pattern. Started as a simple script for one website, but I realized that as I developed new websites, the same functionality was required. Instead of copy&pasting the code, I decided to start building this library for personal use.

The aim of this library is not the support of all web browsers, but to have a lightweight library with JQuery like syntax for specific projects such as: Extensions, plugins, and/or applications.

Installation

npm install @sandboxed/unitjs

yarn add @sandboxed/unitjs

Or simple download the version you like from lib/, and import the library right into your development environment.

Browser

<script type="module">
  // ESM only
  import { UnitJS as $ } from './path/to/unit.js';

  $(document).ready(() => console.log('ready'));
</script>

ESM

import { UnitJS as $ } from '@sandboxed/unitjs';

$(document).ready(() => console.log('ready'));

CommonJS

// CJS option 1
const $ = require('@sandboxed/unitjs').default;

// CJS option 2
const { default: $ } = require('@sandboxed/unitjs');

$(document).ready(() => console.log('ready'));

What about JQuery

Since JQuery cares about giving support to the vast of web browsers, it tends to be heavy. Most of its functions are not even used, like animations. I've seen projects that require JQuery just to use AJAX functionality, or just the animations. This is the reason I began developing UnitJS.

What about UnitJS

I believe a library should have a purpose and one purpose only. In this case, I built UnitJS to have just the one thing I used the most in JQuery: DOM manipulation. I could add AJAX functionality, or even animations, but then I'll be creating a JQuery copy. UnitJS is just there to manipulate the DOM, to make your life easier, not to learn a whole new framework just to start coding.

You should use UnitJS

No, you don't need to!. UnitJS was built for personal use, but you're free to use it if you need it. Be aware though, this library doesn't support all browsers and will not (until all browsers support ES6 I guess).

If you just started learning JavaScript, perhaps you shouldn't use this at all. You need to understand what's happening behind scenes before using this library (or any library or framework for that matter).

That being said

Feel free to fork and redo as much as you need. Let me know what you did or change to build a better UnitJS.