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

zvook-ui-kit

v3.0.0

Published

Zvook's official UI kit

Readme

Zvook UI Kit

This is the official Zvook's UI kit. It's a rolling release repository that's currently in development.

Learn more about Zvook @ https://zvook.co

Table of Contents

  1. Conventions
    1. Imports
    2. Color naming
  2. Troubleshooting
    1. Windows End-of-line sequence (CRLF)
    2. Node build errors on MacOS

Conventions

Imports

ES6 modules imports should, preferably, be done at the top of the file either statically or lazy loaded. So, for example, instead of using React.useEffect throughout the code, one should do

import React, { useEffect } from 'react';

...

useEffect(...);

Imports should also be automatically organised alphabetically. See the section "Working with MS Visual Studio Code" to see how to configure this behavior.

Color naming

Variables representing colors follow a specific naming convention: $color-[base-color]-[variation]

Ex: $color-accent-light or $color-blue-dark


Troubleshooting

Windows End-of-line sequence (CRLF)

If you are working on a windows machine, you may experience Delete 'CR' ESLint errors in your files. This is caused by the end of line sequence specific to Windows which is CRLF unlike LF which the project in set up to use. Follow these 2 steps to resolve the issue:

  1. Switch all files to LF EOL sequence by using a VS Code extension called Change All End Of Line Sequence by Keyoti Inc.
    • Install the extension.
    • Click F1 in VS Code, type >Change All End Of Line Sequence and hit Enter.
    • In a dialog window input file types to convert specify: .ts, .tsx.
    • In the next dialog window blacklist node_modules folder by typing: !node_modules.
    • In the new dialog window select LF.
  2. The next step is to set the default EOL sequence. Open git bash or cmd and type in git config --global core.autocrlf false.

Node build errors on MacOS

If you see an error related to node-gyp or snappy while working in MacOS type

xcode-select --install