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

divine.css

v1.4.0

Published

A library that resets almost any element's styles to be like virgin pure <div>

Readme

divine.css

divine.css is a library that resets almost any element's styles to be like virgin pure <div>. No matter what you are going to use: <fieldset> or <details>, <button> or <a> — everything will be rendered as simple <div>.

Start building divine web right now:

npm install --save divine.css

Why?

When you are creating elements using some methodoligies like BEM, you you should not depend on the name of the element. For example, you have a button-styled element named .primary-button and you wanna use it like <button class="primary-button">...</button> in forms and <a class="primary-button">...</a> somewhere else. You should not think about element's default styles! Just add this class name to any element and it will work.

How ofter do you reset <ul>'s bullets and margins? How ofter do you reset <fieldset>'s border? How ofter do you completely reset <input>'s and <button>'s background and borders? That's it! divine.css solves all your problems! It's easier to think you are styling <div> element than reset the <ul> in every CSS class name and then style it.

Everything is a <div>. <div> is everything.

Even inline elements are block-level <div>s. To see list of normalized and resetted elements, please visit the src/divine.css file.

Please note:

  • It also resets outline property. Don't forget to enable it manually!
  • It does not reset cursor property.
  • It does not reset deprecated and not standardized elements.

License

divine.css is licensed under MIT license. For details, please see the LICENSE file.