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

rux-icon

v0.0.2

Published

RUX Icon Project

Downloads

5

Readme

Vant Icons

Install

NPM

npm i @rux-icon -S

Document

Contribution

Update Icons

  1. Update iconfont in your project
  2. Download new iconfont & update font directory
  3. Make a Pull Request

About Version

1. version

每个npm包都有一个package.json,如果要发布包的话,package.json里面的version字段就是决定发包的版本号了。

version字段是这样一个结构: ‘0.0.1’,是有三位的版本号。分别是对应的version里面的:major, minor, patch。 也就是说当发布大版本的时候会升级为 1.0.0,小版本是0.1.0,一些小修复是0.0.2

2. npm version

为了方便用户更改版本号,npm有npm version这个命令来自动更改版本号,同时帮忙commit. 比如说 当前版本是 1.1.1,当执行 npm version patch -m '[patch]'的时候,会自动把package.json里面的version改为1.1.2,同时git会多一个commit log [patch],这次改动便是更改package.json。

如果执行了prepatch,版本号会从1.1.1变成 1.1.2-0

  • 我们称版本号的三位分别是 大号.中号.小号-预发布号

3. major | minor | patch | premajor | preminor | prepatch | prerelease

| npm version | 功能 | | ----------- | ------------------------------------------------------------ | | major | - 如果没有预发布号,则直接升级一位大号,其他位都置为0 - 如果有预发布号: -- 中号和小号都为0,则不升级大号,而将预发布号删掉。即2.0.0-1变成2.0.0,这就是预发布的作用 -- 如果中号和小号有任意一个不是0,那边会升级一位大号,其他位都置为0,清空预发布号。即 2.0.1-0变成3.0.0 | | minor | - 如果没有预发布号,则升级一位中号,大号不动,小号置为空 - 如果有预发布号: -- 如果小号为0,则不升级中号,将预发布号去掉 -- 如果小号不为0,同理没有预发布号 | | patch | - 如果没有预发布号:直接升级小号,去掉预发布号 - 如果有预发布号:去掉预发布号,其他不动 | | premajor | - 直接升级大号,中号和小号置为0,增加预发布号为0 | | preminor | - 直接升级中号,小号置为0,增加预发布号为0 | | prepatch | - 直接升级小号,增加预发布号为0 | | prerelease | - 如果没有预发布号:增加小号,增加预发布号为0 - 如果有预发布号,则升级预发布号 |

执行命令及版本提升示例:

假设初始版本为0.1.0

➜  xxx git:(master) npm version preminor
v0.1.0-0
➜  xxx git:(master) npm version minor
v0.1.0
➜  xxx git:(master) npm version prepatch
v0.1.1-0
➜  xxx git:(master) npm version patch   
v0.1.1
➜  xxx git:(master) npm version prerelease
v0.1.2-0
➜  xxx git:(master) npm version premajor
v1.0.0-0
➜  xxx git:(master) npm version major   
v1.0.0