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

@qualifyze/design-system

v3.2.2

Published

Qualifyze Design System

Downloads

162

Readme

Design System

A place to develop React components in a sandboxed environment.

Docs

Getting Started

  • Install Volta
  • Install all dependencies with npm ci
  • Run Storybook with npm start, it will open automatically in your browser.

Fonts

You need to include the new fonts from @qualifyze/mui-theme:

import "@qualifyze/mui-theme/fonts/everett/index.css"
import "@qualifyze/mui-theme/fonts/tobias/index.css"

Dependencies

The design system has a dependency on globalThis so if you are using the design system you need to either install a npm package like globalthis. Or if you have access to core-js in your project you can solve the dependency like this:

import 'core-js/features/global-this'

In your app entry where you would normally apply other polyfills.

Z-Indices

This project includes several components that have to work even when they are layered on top of each other. To not mess up the order in which they should appear on screen, let's collect all relevant values for z-index here.

| Component | z-index | | ---------------------------- | --------- | | Header (in website) | 50 | | Cookie Banner (in website) | 900 | | Notification | ??? | | Modal | 500 |

Limitations and known issues

Stack, Inline, Tiles and Columns components with large space prop values

Child components of Stack, Inline, Tiles and Columns might "leak" into other components if values above 4 are given to it in the space prop, blocking interaction with other UI elements like buttons or text.

Workaround is to wrap the component that "leaks" and the one "leaked into" in Box or Flex components and provide z-index for both. For example, with a Stack component:

import Box from '@qualifyze/design-system'

function App() {
  return (
    <Box>
      <Box sx={{ zIndex: 2 }}>
        <Button>You can't click Me!</Button>
      </Box>
      <Box sx={{ zIndex: 1 }}>
        <Stack space={5}>
          <Button>Just a regular button</Button>
        </Stack>
      </Box>
    </Box>
  )
}

For examples of how these components can leak, check their stories in storybook under "leaking example". So far, Stack is the only one who has actually given trouble and the only example taken from the platform.

Fixing this requires a major version release because we still need to support Internet Explorer.