[mostafaNazari702]

PR Checklist

• Addresses an existing open issue: works on 📝 Docs: Review docs for correctness #5528 (@mark-wiemer changed from "fixes" to "works on")
• That issue was marked as status: accepting prs (@mark-wiemer checked this box)
• Steps in CONTRIBUTING.md were taken

Overview

Fixes several documentation correctness issues across 5 pages, each verified against the current source code.

Error codes (features/error-codes.mdx): The table listed 7 of the 16 error codes defined in error-constants.mjs. Added the 9 missing codes (ERR_MOCHA_FATAL, ERR_MOCHA_FORBIDDEN_EXCLUSIVITY, ERR_MOCHA_INSTANCE_ALREADY_DISPOSED, ERR_MOCHA_INSTANCE_ALREADY_RUNNING, ERR_MOCHA_INVALID_PLUGIN_DEFINITION, ERR_MOCHA_INVALID_PLUGIN_IMPLEMENTATION, ERR_MOCHA_MULTIPLE_DONE, ERR_MOCHA_TIMEOUT, ERR_MOCHA_UNPARSABLE_FILE) in alphabetical order.

CLI --extension default (running/cli.mdx): Prose said the default was js. The actual default is ["js", "cjs", "mjs"] per mocharc.json. Updated the description and the usage example accordingly.

Config file priority list (running/configuring.mdx): The numbered priority list was missing .mocharc.cjs (highest precedence) and .mocharc.mjs. Updated to match the CONFIG_FILES array in config.js exactly.

Compiler deprecation page (explainers/compilers-deprecation.mdx): Stated Mocha "only loads .js files" by default. Updated to reflect the actual defaults (.js, .cjs, and .mjs).

ESM support limitations (explainers/nodejs-native-esm-support.mdx): Stated the configuration file "can only be a CommonJS file (.mocharc.js or .mocharc.cjs)". This is incorrect — YAML and JSON config formats are also supported. Corrected the bullet to accurately describe the JavaScript config format requirement and point readers to the configuring page.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mostafaNazari702 / name: Mostafa Nazari (22c690b)

[mark-wiemer]

@mostafaNazari702 thanks for the PR :) please do review CONTRIBUTING.md when you can. Additionally, I've added a quick explainer in the backing issue (#5528). As much as we know about the project, it's critical that our changes to the docs are accurate, and it takes time for us to manually verify a lot of these edge cases. If you could add your own examples in the form of PR comments or GitHub Gists to support these changes, it'd go a long way in getting this PR merged :)

That said, three of the five files were easy to validate, so if you could create two quick examples we'd be able to merge this promptly!

Also, please run npm run format:fix when you have a chance. We are working on #5856 in the meantime :)

Thanks again!

[mark-wiemer]

Won't merge until we get the go-ahead from Josh :) thank you for this!

[JoshuaKGoldberg]

Looks great - I verified this matches up the code & #5397. Thanks so much @mostafaNazari702! 🔥