@commitlint/config-nx-scopes

中文文档
21.2.3发布于 2026/09/20MITES Module近 30 天下载 28万

Shareable commitlint config enforcing nx project names as scopes

原始使用文档
文档目录3 节
  1. Getting started
  2. Filtering projects
  3. Examples

@commitlint/config-nx-scopes

Lint your nx project commits

Shareable commitlint config enforcing nx project and workspace names as scopes. Use with @commitlint/cli and @commitlint/prompt-cli.

Scopes are read from the nx project graph, so a project contributed by an nx plugin is a valid scope even though it has no project.json or package.json of its own.

Getting started

npm install --save-dev @commitlint/config-nx-scopes @commitlint/cli
echo "module.exports = {extends: ['@commitlint/config-nx-scopes']};" > commitlint.config.js

Filtering projects

You can filter projects by providing a filter function as the second parameter to getProjects(). The function will be called with an object containing each projects' name, projectType, and tags. Simply return a boolean to indicate whether the project should be included or not.

As an example, the following code demonstrates how to select only applications that are not end-to-end tests.

In your .commitlintrc.js file:

async function getConfig() {
  const {
    default: {
      utils: { getProjects },
    },
  } = await import("@commitlint/config-nx-scopes");

  return {
    rules: {
      "scope-enum": async (ctx) => [
        2,
        "always",
        [
          ...(await getProjects(
            ctx,
            ({ name, projectType }) => !name.includes("e2e") && projectType == "application",
          )),
        ],
      ],
    },
    // . . .
  };
}

module.exports = getConfig();

Here is another example where projects tagged with 'stage:end-of-life' are not allowed to be used as the scope for a commit.

In your .commitlintrc.js file:

async function getConfig() {
  const {
    default: {
      utils: { getProjects },
    },
  } = await import("@commitlint/config-nx-scopes");

  return {
    rules: {
      "scope-enum": async (ctx) => [
        2,
        "always",
        [...(await getProjects(ctx, ({ tags }) => !tags.includes("stage:end-of-life")))],
      ],
    },
    // . . .
  };
}

module.exports = getConfig();

Examples

❯ cat commitlint.config.js
{
  extends: ['@commitlint/config-nx-scopes']
}

❯ tree packages

packages
├── api
├── app
└── web

❯ echo "build(api): change something in api's build" | commitlint

❯ echo "test(foo): this won't pass" | commitlint
⧗   --- input ---
test(foo): this won't pass
✖   scope must be one of [api, app, web] [scope-enum]
✖   found 1 problems, 0 warnings

❯ echo "ci: do some general maintenance" | commitlint

Consult Rules reference for a list of available rules.

版本与发布记录

@commitlint/config-nx-scopes 共发布 43 个版本,首次发布于 2022/01/25;过去 12 个月发布了 12 个版本。

版本发布日期距今
21.2.3latest2026/09/201 个月前
21.2.02026/06/304 个月前
21.1.02026/06/234 个月前
21.0.22026/05/295 个月前
21.0.12026/05/125 个月前
21.0.02026/05/086 个月前

关于 @commitlint/config-nx-scopes 的常见问题

@commitlint/config-nx-scopes 是什么?

Shareable commitlint config enforcing nx project names as scopes

如何安装 @commitlint/config-nx-scopes?

在项目目录运行 npm install @commitlint/config-nx-scopes,或使用 pnpm add / yarn add / bun add。

@commitlint/config-nx-scopes 支持 TypeScript 吗?

该包的 package.json 没有声明类型入口。需要类型提示时,可以在 npm 上查找社区维护的 @types/commitlint__config-nx-scopes 是否存在。

@commitlint/config-nx-scopes 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@commitlint/config-nx-scopes 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=22.12.0。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@commitlint/config-nx-scopes 可以商用吗?

@commitlint/config-nx-scopes 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@commitlint/config-nx-scopes 的下载量有多少?

根据 npm 官方下载统计,@commitlint/config-nx-scopes 在 2026/10/11 – 2026/11/09 这 30 天内被下载 279,666 次,日均约 9,322 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@commitlint/config-nx-scopes 还在维护吗?

最新版本 21.2.3 发布于 2026/09/20(1 个月前);至今共发布 43 个版本,其中过去 12 个月发布了 12 个;首次发布于 2022/01/25。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。