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

@skywork/sep

v1.2.22

Published

> sep 迁移至 cnpm > Rollup+React+Antd components library(private).

Downloads

114

Readme

Sep

sep 迁移至 cnpm Rollup+React+Antd components library(private).

Use of Sep

Sep's source code

First, absolutely run npm i.

And then, if you want to get in develop mode, simply run npm run dev, this will start storybook to let you overview components. if things goes well, you command line shows information below:

> [email protected] dev /usr/local/var/www/Ele/Sep
> start-storybook -p 9001 -c .storybook

info @storybook/react v3.4.11
info
info => Loading custom webpack config (full-control mode).
webpack built 9962dede4114cdd8e152 in 8764ms
info Storybook started on => http://localhost:9001/
info

Then open your browser and jump to http://localhost:9001/, and you can see a webpage like this:

pic

if you are developing a new component, modify src/components/stories.js and add your component here, then you will see you component shows on the webpage above.

For more information about storybook, please jump to storybook.

After a component completed, run npm run build and this will create a sep folder in root of Sep. The sep is what we are going to publish to npm, and what we are going to import to our project.

Sep's dist code

  1. npm i -S @skywork/sep
  2. npm i -D babel-plugin-import
  3. .babelrc or babel-loader option
// if you are using antd as well, option is an array
"plugins": [
    [
      "import",
      [
        { "libraryName": "antd", "style": true },
        {
          "libraryName": "sep",
          "libraryDirectory": "es",
          "style": true
        }
      ]
    ]
  ]
// if you only use sep, option is an object
"plugins": [
    [
      "import",
        {
          "libraryName": "sep",
          "libraryDirectory": "es",
          "style": true
        }
    ]
  ]

How to develop

Rules

  1. Nameing a component's folder should be all lower-case, and split the words with '-'. For example, a component's name is nav list, we should name the folder as 'nav-list', but the component class, we take Hungarian notation, like we name the nav list as NavList.

  2. A component class should have to define its props and state interface.

  3. A component class should define its propTypes with 'prop-types'.

  4. Class names should composed with 'classnames' if it is complex. If a class name is composed with multiple class names, or a class name is dynamic, we call it complex.

  5. A component's class name should have a prefix, the prefix defined in defaultProps of the class, naming prefixCls.

  6. Common styles defined in src/components/style, witch containing color and themes folder. We usually modify themes/default.less witch defines Base styles for most components and Border color and every component's own style and so on, and themes/default.less takes colors from color/colors.less.

How to publish in local & use it

  1. Download the docker
  2. Docker run -it --rm --name verdaccio -p 4873:4873 verdaccio/verdaccio
  3. Nrm use verdaccio
  4. Npm run build
  5. Cd sep
  6. Change sep version
  7. Npm publish
  8. Check publish successed or not in your verdaccio network
  9. Update the '@skywork/sep' in your project