noUnresolvedImports

JavaScript (and super languages)

摘要

¥Summary

规则生效日期：v2.0.0

¥Rule available since: v2.0.0
诊断类别：lint/nursery/noUnresolvedImports

¥Diagnostic Category: lint/nursery/noUnresolvedImports
此规则没有修复方案。

¥This rule doesn’t have a fix.
此规则的默认严重级别为 information。

¥The default severity of this rule is information.
此规则属于以下域：

¥This rule belongs to the following domains:
- project
来源：

¥Sources:
- 灵感来自 import/named
  
  ¥Inspired from import/named

如何配置

¥How to configure

1
{
2
  "linter": {
3
    "rules": {
4
      "nursery": {
5
        "noUnresolvedImports": "error"
6
      }
7
    }
8
  }
9
}

描述

¥Description

导入不存在的导出文件时会发出警告。

¥Warn when importing non-existing exports.

导入不存在的导出会在运行时或构建时导致错误。Biome 可以检测此类不正确的导入并报告错误。

¥Importing a non-existing export is an error at runtime or build time. Biome can detect such incorrect imports and report errors for them.

请注意，如果你使用 TypeScript，则可能不希望使用此规则，因为 TypeScript 已经为你执行了此类检查。

¥Note that if you use TypeScript, you probably don’t want to use this rule, since TypeScript already performs such checks for you.

已知限制

¥Known Limitations

此规则不验证通过动态 import() 表达式或 CommonJS require() 调用导入的内容。

¥This rule does not validate imports through dynamic import() expressions or CommonJS require() calls.

示例

¥Examples

无效

¥Invalid

1
export function foo() {};

1
// Attempt to import symbol with a typo:
2
import { fooo } from "./foo.js";

/bar.js:2:10 lint/nursery/noUnresolvedImports ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ The path ./foo.js has no export named fooo.
  
    1 │ // Attempt to import symbol with a typo:
  > 2 │ import { fooo } from “./foo.js”;
      │          ^^^^
    3 │ 
  
  ℹ Make sure that the path is correct and that you’re importing the right symbol.

有效

¥Valid

1
export function foo() {};

1
// Fixed typo:
2
import { foo } from "./foo.js";

noUnresolvedImports

摘要

如何配置

描述

已知限制

示例

无效

有效

相关链接