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

wbh-ui-components

v1.0.0

Published

use wp2vite, change webpack config into vite config. Package includes react, TypeScript, Mobx(simple use). Package use Eslint && pretteir. Support Tailwind Css.

Downloads

2

Readme

Chainx-Ui-Components

npm version

This is Chainx's front-end team, a more convenient and easy-to-use component library based on the ant design component library for secondary packaging.

Ant-design is powerful, but if you want to personalize the style customization, you need to spend a lot of time to modify. In order to avoid having to re-modify the default style that overrides ant-design every time a new project is created, it is necessary to recapture it.

At the same time, we can customize styles directly on components, such as:

<Icon cursor={'pointer'} iconSrc={IconSearch} size={24} />

The root element of Icon here is actually an img tag, and we can directly pass cursor, size or other set attributes on props to change its css style, without using styled-components or whatever to wrap him.

Get started

yarn add chainx-ui-components

Then you can reference it in your file!

import { Icon } from 'chainx-ui-components';

<Icon cursor={'pointer'} iconSrc={IconSearch} size={24} />

Extend

Our component library is also compatible with the powerful rebass library, which you can also use for some simple styling customization. such as:

<Text fontSize={15} fontWeight={600}>
  Test
</Text>

Moreover, since it is a component based on ant design for secondary encapsulation, the properties of the ant design component are also fully supported

Development

Unit Tests

When developing components, it is important to note that the coverage rate of unit tests should reach more than 90. The command to run the test is:

yarn test

The unit test files for each component are placed in the test directory of its directory, for example: lib/Button/__test__/Button.test.tsx

Documentation

Documentation is an important thing for a component library, and each component should have its corresponding documentation description. Document file placement path: lib/Button/Button.mdx

Regarding the writing of the mdx file, the docz library was developed with the help of the command to run the document locally: yarn docz:dev Then visit http://localhost:6001 to view the contents of your document

Publish

Before publish, make sure your tests pass before you publish to npm