@darraghor/eslint-plugin-nestjs-typed

中文文档
7.5.8发布于 2026/10/05ISCTypeScriptES Module构建来源已验证近 30 天下载 112.8万

Eslint rules for nestjs projects

原始使用文档
文档目录15 节
  1. Support this plugin
  2. A note on versions
  3. Eslint 9.x support
  4. TS Eslint version support
  5. Have an idea for a rule?
  6. Index of available rules
  7. Who is this package for?
  8. 1. Detect Nest Dependency Injection issues
  9. 2. Using Open Api / Swagger decorators and automatically ge…
  10. 3. Helping prevent bugs
  11. 4. Security
  12. To install
  13. To configure
  14. Injectables rule scans everything
  15. Disabling a rule

commit npm npm-tag size types

NestJS Eslint Plugin

If you use NestJs (https://nestjs.com/) these ESLint rules will help you to prevent common bugs and issues in NestJs applications.

Skip to How to configure but if you have issues come back and read this whole document.

pnpm add -D @darraghor/eslint-plugin-nestjs-typed
//or
npm i -D @darraghor/eslint-plugin-nestjs-typed
//or
bun install -d @darraghor/eslint-plugin-nestjs-typed

Support this plugin

If you use this plugin in commercial setting consider submitting PRs on work time. It saves your business money, so it makes your business money!

If you really want to support me directly you can use https://darraghoriordan.gumroad.com/coffee

But please, just submit PRs to help all NestJS devs. This is the way!

A note on versions

  • Version 6.x supports Eslint version ^9 and typescript eslint parser ^7 and ^8
  • Version 5.x supports Eslint version ^8 and typescript eslint parser ^7 and ^8
  • Version 4.x supports Eslint version ^8 and typescript eslint parser ^6
  • Version 3.x supports Eslint version ^8 and typescript eslint parser ^5
  • Version 2.x supports Eslint version ^7.x and typescript eslint parser ^4

Eslint 9.x support

I have updated the configs to work with eslint 9.x. This is a breaking change.

If you are using eslint 8.x you should use version 5.x of this plugin.

I did try to leave the old style configs in place but I haven't tested them properly. If you have any issues please submit a PR.

See How to configure for more info.

TS Eslint version support

There are breaking changes between versions of ts-eslint.

typescript eslint parser supports a range of typescript versions but there can be a delay in supporting the latest versions.

This plugin only supports typescript up to the version typescript eslint parser supports. See https://github.com/typescript-eslint/typescript-eslint#supported-typescript-version for the versions.

Have an idea for a rule?

Please submit a pull request. See Contributing.

Index of available rules

CategoryRuleis on in recommended ruleset?
Nest Modules and Dependency Injectionprovided-injected-should-match-factory-parameters✅
injectable-should-be-provided✅
use-injectable-provided-token✅
use-dependency-injection❌
Nest Swaggerapi-property-matches-property-optionality✅
controllers-should-supply-api-tags✅
api-method-should-specify-api-response✅
api-method-should-specify-api-operation❌
api-enum-property-best-practices✅
api-property-returning-array-should-set-array✅
api-property-should-have-api-extra-models✅
api-operation-summary-description-capitalized✅
swagger-file-upload-should-be-documented✅
Preventing bugsparam-decorator-name-matches-route-param✅
forward-ref-injection-should-use-wrapper-type✅
uploaded-file-should-be-validated✅
validate-nested-of-array-should-set-each✅
validated-non-primitive-property-needs-type-decorator✅
all-properties-are-whitelisted✅
all-properties-have-explicit-defined✅
no-duplicate-decorators✅
validation-pipe-should-use-forbid-unknown✅
Securityapi-methods-should-be-guarded❌
Code Consistencysort-module-metadata-arrays❌
use-correct-endpoint-naming-convention❌

The "recommended" ruleset are the default rules that are turned on when you configure the plugin as described in this document.

The name "recommended" is an eslint convention, you can safely use the rules not in that list, they are just more opinionated.

Who is this package for?

If you use NestJs (https://nestjs.com/) these ESLint rules will help you to prevent common bugs and issues in NestJs applications.

They mostly check that you are using decorators correctly.

The primary groupings of rules in this plugin are...

1. Detect Nest Dependency Injection issues

The Nest DI is declarative and if you forget to provide an injectable you wont see an error until run time. Nest is good at telling you where these are but sometimes it's not.

In particular if you're using custom providers the errors can be really tricky to figure out because they won't explicitly error about mismatched injected items, you will just get unexpected operation.

These are described in the "Common Errors" section of the nest js docs.

2. Using Open Api / Swagger decorators and automatically generating a clients

When working with NestJS I generate my front end client and models using the swagger/Open API specification generated directly from the nest controllers and models.

I have a bunch of rules here that enforce strict Open API typing with decorators for NestJs controllers and models.

These rules are opinionated, but necessary for clean model generation if using an Open Api client generator later in your build.

3. Helping prevent bugs

There are some tightly coupled but untyped decorators and things like that in nest that will catch you out if your not careful. There are some rules to help prevent issues that have caught me out before.

4. Security

There is a CVE for class-transformer when using random javascript objects. You need to be careful about configuring the ValidationPipe in NestJs. See https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18413 https://github.com/typestack/class-validator/issues/438

To install

The plugin is on npm here: https://www.npmjs.com/package/@darraghor/eslint-plugin-nestjs-typed You can see how the rules are used in this NestJS project: https://github.com/darraghoriordan/use-miller

npm install --save-dev @darraghor/eslint-plugin-nestjs-typed

// or

yarn add -D @darraghor/eslint-plugin-nestjs-typed
// or

pnpm add -D @darraghor/eslint-plugin-nestjs-typed

If you don't already have class-validator you should install that

npm install class-validator

// or

yarn add class-validator

// or

pnpm add class-validator

To configure

Update your flat eslint config with the plugin import and add the flatRecommended rule set.

My config looks something like this. I'm 99% sure that you have to setup typescript parser also.

import eslintNestJs from "@darraghor/eslint-plugin-nestjs-typed";
// ... and all your other imports
export default tseslint.config(
    eslint.configs.recommended,
    tseslint.configs.strictTypeChecked,
    tseslint.configs.stylisticTypeChecked,
    {
        languageOptions: {
            globals: {
                ...globals.node,
                ...globals.jest,
            },
            parser,
            ecmaVersion: 2022,
            sourceType: "module",
            parserOptions: {
                projectService: true,
                tsconfigRootDir: import.meta.dirname,
            },
        },
    },
    eslintNestJs.configs.flatRecommended // This is the recommended ruleset for this plugin
);

For ESlint 8 I export the old style config in the "classicConfig" export.

I believe it would work something like this...

import {classicPlugin} from "@darraghor/eslint-plugin-nestjs-typed";

module.exports = {
    plugins: [classicPlugin],
};

Injectables rule scans everything

Note: the injectables test scans your whole project. It's best to filter out ts things that don't matter - use filterFromPaths configuration setting for this. See the rule documentation for more info.

There are some sensible defaults already applied.

Note: You can easily turn off all the swagger rules if you don't use swagger by adding the flatNoSwagger rule set AFTER the recommended rule set.

// all the other config
    extends: [
       "plugin:@darraghor/nestjs-typed/recommended",
       "plugin:@darraghor/nestjs-typed/no-swagger"
    ],
 // more config

Disabling a rule

Disable a single rule with the full name e.g. in your eslint configuration...

   rules: {
   "@darraghor/nestjs-typed/api-property-returning-array-should-set-array":
            "off",
   }

版本与发布记录

@darraghor/eslint-plugin-nestjs-typed 共发布 315 个版本,首次发布于 2021/06/04;过去 12 个月发布了 88 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
7.5.8latest2026/10/051 个月前
7.5.72026/10/051 个月前
7.5.62026/09/221 个月前
7.5.52026/09/191 个月前
7.5.42026/09/181 个月前
7.5.32026/09/131 个月前

其他发布通道:next → 6.1.0-rc.5。

关于 @darraghor/eslint-plugin-nestjs-typed 的常见问题

@darraghor/eslint-plugin-nestjs-typed 是什么?

Eslint rules for nestjs projects

如何安装 @darraghor/eslint-plugin-nestjs-typed?

在项目目录运行 npm install @darraghor/eslint-plugin-nestjs-typed,或使用 pnpm add / yarn add / bun add。它还需要宿主项目提供 peer 依赖:eslint(>=9.18.0)、class-validator(*)、@typescript-eslint/parser(^7.0.0 || ^8.0.0)。npm 7 及以上与 pnpm 8 及以上默认会自动安装必需的 peer 依赖,Yarn 需要手动安装。

@darraghor/eslint-plugin-nestjs-typed 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@darraghor/eslint-plugin-nestjs-typed 支持 ESM 还是 CommonJS?

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

@darraghor/eslint-plugin-nestjs-typed 需要什么版本的 Node.js?

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

@darraghor/eslint-plugin-nestjs-typed 可以商用吗?

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

@darraghor/eslint-plugin-nestjs-typed 的下载量有多少?

根据 npm 官方下载统计,@darraghor/eslint-plugin-nestjs-typed 在 2026/10/12 – 2026/11/10 这 30 天内被下载 1,127,674 次,日均约 37,589 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@darraghor/eslint-plugin-nestjs-typed 还在维护吗?

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