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

classattr

v2.0.1

Published

A classList-like API that's purely based on reading/writing the class attribute.

Downloads

12

Readme

ClassAttr

A classList-like API that's purely based on reading/writing the class attribute.

WHY?!

Because apparently touching the classList API for a node causes a DOMTokenList to be allocated for that node indefinitely. Like you may be asking the classList API to delete a class from a node that perhaps doesn't even have classes to begin with, and that will still allocate a DOMTokenList for that node, which sounds like nonsense to me.

Also sometimes the classList API pointlessly triggers MutationObservers even when it doesn't actually change any class, which sounds like nonsense to me also.

Those problems is what this library is meant to address, maybe you don't need it.

Install

npm install --save classattr

Usage

It works just like the classList API.

import ClassAttr from 'classattr';

const element = document.body;

ClassAttr.add ( element, 'foo', 'bar', 'baz' );

ClassAttr.contains ( element, 'foo' ); // => true
ClassAttr.contains ( element, 'foo2' ); // => false

ClassAttr.remove ( element, 'bar' );

ClassAttr.toggle ( element, 'baz' );
ClassAttr.toggle ( element, 'baz' );
ClassAttr.toggle ( element, 'baz', true );
ClassAttr.toggle ( element, 'baz', false );

License

MIT © Fabio Spampinato