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

z-index

v0.0.1

Published

Dead simple CSS z-index utilities.

Downloads

1,154

Readme

z-index

A tiny and dead simple set of CSS z-index utilities.

why

The z space in CSS can easily become arbitrarily increased over time as new components are added. You've probably seen something like this before in CSS source code...

/* need this to go above the other thing */
.og-component { z-index: 9; }

and some time later...

/* this needs to go above og-component */
.new-component { z-index: 10; }
.newer-component { z-index: 11; }

In practice we generally don't need more than a few layers at any one time even across fairly complex apps.

By adopting a small range of values that mimics the (inverse) of the HTML heading spec, that we can apply directly to any html element, we prevent the need to declare z-indexes on the fly, and keep the mental model of "layers" easy to understand while developing.

.z1 { z-index: 1; }
.z2 { z-index: 2; }
.z3 { z-index: 3; }
.z4 { z-index: 4; }
.z5 { z-index: 5; }
.z6 { z-index: 6; }

Other than the 6 basic indexes, a zF class is included that forces a very high z-index in the event that another component or library is being overzealous with its z-index values and you just can't even.

.zF { z-index: 999; } /* break glass in case of emergency */

usage

<main>
    <section class="z1">I'm the lowest</section>
    <section class="z2">I'm a little bit higher.</section>
    <section class="z3">Chilling here in the middle, kinda hungry, could use a sandwich.</section>
    <section class="z4">Just a bit higher.</section>
    <section class="z5">I'm assistant to the highest z-index</section>
    <section class="z6">Look at me all the way up here.</section>

    <section class="zF">Buahaha and you thought z6 was high.</section>
</main>