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

nefbl

v0.2.6

Published

新一代前端框架

Vulnerabilities

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

Links

Git

Maintainers

hai2007hai2007

Keywords

frameworknefbl

Readme

Nefbl | 新一代前端框架

Issues

使用的时候遇到任何问题或有好的建议，请点击进入issue！

How to use?

你可以查阅文档获得接口API和入门教程。

RFC

我们设计并启动了需求收集流程：

首先，如果你有说明新功能希望提供（文档未提供的），应该先去RFC文件夹中查询是否有类似的，如果有，可以参与评论你的看法。

如果没有，那么，你可以在RFC/draft中进行新增。

可以发现RFC文件夹中有四个子文件，其中的意思如下：

  • RFC/draft : 草案阶段，所有人可以随意新增或修改意见。

  • RFC/think : 准备阶段，被这里收录意味着此功能不就将提供出来，最终在API也会在其中尽力说明清楚，此时，你还可以参与修改。

  • RFC/nouse : 废弃的建议，一般绝对不会采纳的建议收集在这里，一般会给出理由，当然，未来还是可能会回退到草案阶段的。

  • RFC/achieve : 确定阶段，这里的内容就是确定将提供的了，不允许再进行修改，除非特殊情况（标记完成的，如果需要修改，请提issue）。

开源协议

MIT

Copyright (c) 2021 hai2007 走一步，再走一步。