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

@zilliz/zui

v1.0.38

Published

## Some rules we need to follow

Downloads

617

Readme

Zilliz design system

Some rules we need to follow

  1. If we need to export className, export classes prop like mui.
  2. All css module named as index.module.css
  3. test

Component style

Material-UI system sx field

  1. In business folder we use css module
  2. In core folder we use sx

Create Component

  1. Go to core folder
  2. Create component folder like ZButton
  3. Create component like ZButton.tsx, and component name need start with Z like ZButton.
  4. Export component in core/index.tsx (Easy for use as lib)

Add Component Story

  1. Go to stories folder
  2. Create ZButton.stories.tsx
  3. Export different component demos like:
  import React from 'react';
  import { ComponentMeta, ComponentStory } from '@storybook/react';
  import { action } from '@storybook/addon-actions';
  import { ZButton } from '../../../core';
  // More on default export: https://storybook.js.org/docs/react/writing-stories/introduction#default-export

  export default {
    title: 'Basic/Button',
    component: ZButton,
  } as ComponentMeta<typeof ZButton>;

  export const Primary: ComponentStory<typeof ZButton> = args => {
    return (
      <ZButton
        {...args}
        onClick={action('custom button click')}
        children="Primary Button"
        color="primary"
      />
    );
  };
  1. Component doc (Optional).

Test Components

  • Unit tests:

    1. Go to test folder
    2. Create ZButton.spec.tsx and implement the tested behavior
    3. Run yarn test to check your work
  • Visual tests:

    We use chromatic for automate visual testing. It will detecte UI changes whenever you open a new pull request to main branch. You can go to PR checks and click UI test to see detail.

Publish

  1. Create PR to dev branch
  2. Merge into dev branch after code review
  3. Action will publish to dev website
  4. Create PR to main branch
  5. Paste story component url in comment
  6. Merge into main branch after ui team review.
  7. Action will publish to prod website
  8. Release with tag, change version in package.json, and action will publish to npm.