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

norm-fe-spec

v1.0.1

Published

前端编码规范工程化

Readme

fe-spec

前端编码规范工程化

mountain: 能力支持

1. 全面的前端生态

支持前端全部生态,无需关注环境,支持直接使用

2. 完善的规范配件

支持对全部前端配置实现一键接入、一键扫描、一键修复、一键升级

3. 完整的测试用例

配套完整的测试用例,提升项目健壮性

:star: 设计目的

随着前端技术的发展,前端项目正在变得越来越复杂。JavaScript 作为一门弱类型解释性编程语言,其灵活多变的语法极大的提高了前端开发效率,但同时也存在一系列问题。在大型项目开发过程中,代码维护所占的时间比重往往大于新功能的开发。因此编写符合团队编码规范的代码是至关重要的。 一致性的代码规范可以增强团队开发协作效率、提高代码质量、减少遗留系统维护的负担。但是每个人的代码编写喜好不同,代码风格也会迥然不同,若要一个团队内所有的成员都能发挥最大程度的价值,一个具有普适性的标准是必不可少的。

那么,如何制定前端团队的代码规范,如何在团队内进行最小成本的推广,就是一个合格的前端架构师面临的一大难题。很多团队的基础建设都只是简单地知晓其中一部分规范工具的使用,但却没有一套完整的工程化产出来助力研发同学实现规范落地。因此,如果我们能够产出一套完整化的前端编码规范工具,都会对不仅能够解决存量项目的编码异味,还能够保证后续所有项目的编码质量。

:couch_and_lamp: 配套工具

我们引入了多个业界流行的 Linter 作为规范文档的配套工具,并根据规范内容定制了对应的规则包,它们包括:

| 规范 | Lint 工具 | npm 包 | | ----------------------------------------------------------------- | -------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | JavaScript 编码规范 TypeScript 编码规范 Node 编码规范 | ESLint | eslint-config-norm | | CSS 编码规范 | stylelint | stylelint-config-norm | | Git 规范 | commitlint | commitlint-config-norm | | 文档规范 | markdownlint | markdownlint-config-norm | | Eslint 插件 | ESlint Plugin | eslint-plugin-norme |

norm-fe-lint 收敛屏蔽了上述依赖和配置细节,提供简单的 CLINode.js API,让项目能够一键接入、一键扫描、一键修复、一键升级,并为项目配置 git commit 卡口,降低项目接入规范的成本。

您可以使用norm-fe-lint 方便地为项目接入全部规范。

其他

测试markdown config

全局安装markdownlint-cli

npm i -g markdownlint-cli
pnpm run lint

生成CHANGELOG

参考conventional-changelog-cli,全局安装conventional-changelog-cli

npm install -g conventional-changelog-cli
pnpm run changelog