Report invalid `--require` directly instead of via UnhandledPromiseRejectionWarning

Open

#1,688 opened on Apr 24, 2022 0 comments 0 reactions 1 assignee View on GitHub

@Krinkle is already working on this.

Since Apr 24, 2022.

Assessment

This issue has not been assessed yet.

Description

Component: CLI Type: Enhancement

QUnit version: 2.18.2
Which environment are you using?: Node.js
How are you running QUnit?: QUnit CLI

We have a test case displays helpful error when failing to require a file in test/cli/cli-main.js which. The assertion currently ensures that the output "includes" the important subset, which is Error: Cannot find module 'does-not-exist-at-all'.

However, when running it directly (in prep for https://github.com/qunitjs/qunit/issues/1684) I noticed it gets there in quite an unsual manner:

(node:4519) UnhandledPromiseRejectionWarning: Error: Cannot find module 'does-not-exist-at-all'
Require stack:
- /qunit/src/cli/require-from-cwd.js
- /qunit/src/cli/run.js
- /qunit/bin/qunit.js
    at internal
    at bin/qunit
    at internal
    at bin/qunit
    at internal
(node:4519) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:4519) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

This happens because /src/cli/run.js currently handles options.requires before setting up options.reporter and process.on('unhandledRejection'). I suggest we swap this around.

Dominant language: JavaScript
Stars: 4k
Forks: 773
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Duplicate Code] Repeated filtered model-alias assembly in proxy server Open

code-quality refactoring

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

github/gh-aw-firewall#8816 · Opened Sep 20, 2026
quickjs: support `timeout=None` (no per-call deadline) in `CodeInterpreterMiddleware` Open

integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

langchain-ai/deepagents#6450 · Opened Sep 20, 2026
[optimization:agents-md-curator] AGENTS.md: compress duplicated Debugging & Logging section and merge redundant autopilot rules Open

optimization optimization:agents-md-curator

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

githubnext/gh-aw-cao#13143 · Opened Sep 20, 2026
[BUG] schema-compat/zodToJsonSchema: nullable zod v4 enum/literal widens to type:[X,"null"] but keeps enum/const, so exported schema rejects null Open

status: needs triage

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

mastra-ai/mastra#24516 · 2 comments · Opened Sep 20, 2026
Kubernetes request flow diagram 404s on both copies of the tutorial Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

layer5io/docs#1263 · Opened Sep 20, 2026

More JavaScript issues