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

get-z-index

v1.2.0

Published

This is library to help you to manage your z indices in declarative way.

Downloads

13

Readme

get-z-index

This is library to help you to manage your z indices in declarative way.

Example

Let's assume that your application has four layers: page, header, modals and notifications.

Lets assume that header should be above the page. Modal above the header and all notifications above modal and header.

const RULES = [
  ['page', 'header'],
  ['header', 'modals'],
  ['modals', 'notifications'],
];

While we have this RULES array we can create function getZIndex which will return z-index for each layer based on this rules.

import { compile } from 'get-z-index';

const getZIndex = compile(RULES);

And now we can use it:

getZIndex('page'); // => 0
getZIndex('header'); // => 1
getZIndex('modals'); // => 2
getZIndex('notifications'); // => 3

Sometimes there is need to be able to show several modals on the screen and several notifications.

Lets define maximum amount of modals and notifications in the dictionary:

const MAX_NUMBER_DICT = {
  modals: 3,
  notifications: 10,
};

Lets create another version of getZIndex which will use this information:

import { compile } from 'get-z-index';

const getZIndex = compile(RULES, MAX_NUMBER_DICT);

Lets calculate all possible zIndices for all layers and items inside layer with usage of second parameter of getZIndex function - index.

getZIndex('page'); // => 0
getZIndex('header'); // => 1
getZIndex('modals'); // => 2
getZIndex('modals', 1); // => 3, z-index for second modal above the first modal
getZIndex('modals', 2); // => 4
getZIndex('notifications'); // => 5

Also it's possible that sometimes someone else code controls z-index of the component. For example modals are from some library. And inside the library we have z-index equal to 1000. We can define it with usage of the last parameter - predefinedZIndices.

const getZIndex = compile(
  [
    ['page', 'modal'],
    ['modal', 'notification'],
    ['notification', 'tooltips'],
  ],
  null,
  { modal: 1000 }
);

And we can use it:

getZIndex('page'); // 0
getZIndex('modal'); // 1000
getZIndex('notification'); // 1001
getZIndex('tooltips'); // 1002

Pretty much it! Use and enjoy!