What is the problem?
给中文新手的 ESLint 报错处理流程：先读规则名和报错文件，判断是代码问题、配置问题还是临时例外，再决定是否局部禁用，不要一上来全局关闭检查。
Quick solution
Treat this as a Node.js errors tutorial issue. First confirm the environment, inputs, permissions, logs, and delivery boundary. Then use the linked deep guide for the full checklist before changing production code or promising a result.
Read the deep guideDetailed steps
- 保存完整报错。记录命令、文件、行号、规则名和错误信息。
- 判断规则类型。是格式、类型、React Hook、安全、无障碍、导入、未使用代码，还是项目自定义规则。
- 优先修代码。能删除未使用变量、补依赖、拆函数、修导入，就不要先禁用规则。
- 判断配置是否合理。如果规则和项目技术栈不匹配，再考虑调整配置，但要写清原因。
- 如需禁用，范围要小。优先单行、单条规则、带解释，不要整文件或全项目禁用。
- 运行验证。修完后跑 lint、build，必要时检查页面或测试。
Commands or code
The source article does not include a copyable command block. Do not invent commands here; follow the diagnostic steps in the deep guide and validate changes in the real project environment.
Risk notes
Confirm the real project environment, account permissions, platform rules, and output quality before delivery. Do not ship AI-generated changes without human review, and do not claim indexing, income, deployment success, or ranking improvements without measured evidence.