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

foxit-component

v1.0.7

Published

Foxit React Component

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

linye96linye96

Keywords

foxitcomponentcssreact

Readme

Foxit Component

组件库

发包原则问题

在 npm 和软件版本管理中，版本号（Versioning）遵循 语义化版本控制（Semantic Versioning，简称 SemVer）的规则。版本号通常采用三位数的格式：MAJOR.MINOR.PATCH。

除了常见的正式版本，还有一些用于标识开发阶段的版本号标签，通常包括 alpha、beta 这些标签帮助开发者和使用者理解软件处于哪个发布阶段。

Alpha 版本 (alpha)

描述：alpha 版本通常是开发中的早期版本，功能未完全实现，可能有大量的 bug 或不稳定的特性，适合开发者和早期测试者使用。 命名规则：通常以 MAJOR.MINOR.PATCH-alpha.N 的格式表示，其中 N 是从 1 开始的递增数字。 例子： 1.0.0-alpha.1 1.0.0-alpha.2 1.0.0-alpha.3

Beta 版本 (beta)

描述：beta 版本通常是开发中的后期版本，功能已经基本完成，可能已经解决了一些 bug，但仍可能存在问题。它是给开发者、测试人员或对新功能感兴趣的用户使用的版本。 命名规则：MAJOR.MINOR.PATCH-beta.N，N 是递增的数字。 例子： 1.0.0-beta.1 1.0.0-beta.2 1.0.0-beta.3

正式版本 (stable, final)

描述：正式版本是经过充分测试，功能和 API 已经稳定，适合最终用户使用。它没有附加的标签，直接用 MAJOR.MINOR.PATCH 格式发布。 命名规则：MAJOR.MINOR.PATCH 例子： 1.0.0 2.0.0 1.1.0

发包示例

alpha:
npm version 1.0.0-alpha.1
npm publish --tag alpha
beta:
npm version 1.0.0-beta.1
npm publish --tag beta
正式:
npm version 1.0.0
npm publish