sindresorhus

eslint-node-test

ESLint rules for the Node.js built-in test runner (`node:test`)

by sindresorhus

JavaScript

JavaScript100%

Commit activity

Last 12 weeks · 147 commits

Full graph →

Community health

5 of 6 standards met

Community profile →
85
✓README✓License✓Contributing✓Code of Conduct○Issue Template✓PR Template
ericcornelissen

Description Instead of just requiring a top-level , also support requiring a top-level . I believe this should be an either-or situation. I'm not quite sure if it makes sense to have it as an extension of this rule (because the name would not make it obvious you could enforce a top-level with it) but it feels like a better option than separately having a (because it could cause conflicts). Perhaps the best approach is to create an entirely new rule and drop ? Examples Additional Info I suppose a concern with requiring a top-level as opposed to is that a test file with only a single also satisfies this rule. To me, that does not seem like a problem (definitely not enough to reject the idea). Also, it could be addressed by requiring the top-level to have at least one nested .

ericcornelissen · 2w ago
Structured data for AI agents

Repository: sindresorhus/eslint-node-test. Description: ESLint rules for the Node.js built-in test runner (`node:test`) Stars: 66, Forks: 0. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Latest release: v1.0.1 (2w ago). Open PRs: 0, open issues: 0. Last activity: 2w ago. Community health: 85%. Top contributors: sindresorhus.