test_runner: restore directory search for --test - #64637

Closed
bitpshr wants to merge 1 commit into
nodejs:mainfrom
bitpshr:test-runner/dir-arg-search
Closed

test_runner: restore directory search for --test#64637
bitpshr wants to merge 1 commit into
nodejs:mainfrom
bitpshr:test-runner/dir-arg-search

Conversation

@bitpshr

@bitpshrbitpshr commented Jul 21, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor

Fixes#64555. Passing a directory to node --test (like node --test tests) matched the directory itself as a glob pattern and then tried to run it as a test file, failing with MODULE_NOT_FOUND.

This expands a pattern that resolves to a directory into a search for the default test files inside it, restoring the pre-glob behavior. File paths, real glob patterns, and nonexistent arguments all pass through unchanged.

Note: This isn't Windows-specific despite the report; it reproduces on every platform (on macOS, node@20 searches the directory and passes while node@22 and node@24 both fail).

@bitpshr
test_runner: restore directory search for --test
b48ff5b
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: nodejs#64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
@nodejs-github-bot

nodejs-github-bot commented Jul 21, 2026

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/test_runner

@bitpshrbitpshr mentioned this pull request Jul 21, 2026
Closed
@nodejs-github-botnodejs-github-bot added needs-ci PRs that need a full CI run. test_runner Issues and PRs related to the test runner subsystem. labels Jul 21, 2026
@bitpshr

bitpshr commented Jul 21, 2026

Copy link
Copy Markdown
ContributorAuthor

Both CI failures look unrelated to this change. test-macOS failed on test-debugger-probe-script-throws.js in the "unusual chars folder" re-run step, and the aarch64 shared-boringssl build failed on test-repl-context.mjs with ERR_INSPECTOR_COMMAND: Inspector error -32000: Promise was collected (the log shows failed 1 out of 10, so it's flaky). This PR only touches test runner directory handling, and its own test passed. A re-run should clear them.

@bitpshr

bitpshr commented Aug 5, 2026

Copy link
Copy Markdown
ContributorAuthor

Just keeping this on the radar. It's been approved for a couple of weeks now, and it's a small test_runner fix (restoring directory arguments to node --test) with a regression test. @MoLow is there anything else needed to get it landed?

@atlowChemiatlowChemi added the request-ci Add this label to start a Jenkins CI on a PR. label Aug 6, 2026
@codecov

codecovBot commented Aug 6, 2026•
edited
Loading

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.13%. Comparing base (6071907) to head (b48ff5b).
⚠️ Report is 501 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #64637 +/- ##
=======================================
Coverage 90.13% 90.13% =======================================
Files 741 741 Lines 242076 242095 +19 Branches 45550 45552 +2 =======================================
+ Hits 218199 218219 +20 + Misses 15391 15386 -5 - Partials 8486 8490 +4
Files with missing linesCoverage Δ
lib/internal/test_runner/runner.js94.52% <100.00%> (+0.09%)⬆️

... and 24 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actionsgithub-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Aug 6, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@coderabbitaicoderabbitaiBot mentioned this pull request Aug 17, 2026
Merged
@bitpshr

bitpshr commented Aug 17, 2026

Copy link
Copy Markdown
ContributorAuthor

Just keeping this on the radar, it has been approved and author ready for a few weeks now. Is anything blocking it from landing? Happy to rebase if it needs a refresh.

@coderabbitaicoderabbitaiBot mentioned this pull request Aug 18, 2026
Merged
12 tasks
@trivikrtrivikr added the author ready PRs with CI started, the required approvals, and no outstanding review comments. label Aug 21, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@nodejs-github-bot

nodejs-github-bot commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator

CI: https://ci.nodejs.org/job/node-test-pull-request/76157/

@trivikrtrivikr added the commit-queue PRs queued for automated landing through the Commit Queue. label Aug 21, 2026
@nodejs-github-botnodejs-github-bot added commit-queue-failed PRs whose Commit Queue landing failed and need manual intervention before retrying. and removed commit-queue PRs queued for automated landing through the Commit Queue. labels Aug 21, 2026
@nodejs-github-bot

nodejs-github-bot commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T15:26:07Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32505631714

@richardlaurichardlau added commit-queue PRs queued for automated landing through the Commit Queue. and removed commit-queue-failed PRs whose Commit Queue landing failed and need manual intervention before retrying. labels Aug 21, 2026
@nodejs-github-botnodejs-github-bot added commit-queue-failed PRs whose Commit Queue landing failed and need manual intervention before retrying. and removed commit-queue PRs queued for automated landing through the Commit Queue. labels Aug 21, 2026
@nodejs-github-bot

nodejs-github-bot commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T17:05:44Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32512148725

@trivikrtrivikr removed the commit-queue-failed PRs whose Commit Queue landing failed and need manual intervention before retrying. label Aug 21, 2026
trivikr pushed a commit that referenced this pull request Aug 21, 2026
@bitpshr@trivikr
test_runner: restore directory search for --test
838a3e9
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@trivikr

trivikr commented Aug 21, 2026

Copy link
Copy Markdown
Member

Landed in 838a3e9

@trivikrtrivikr closed this Aug 21, 2026
This was referenced Aug 23, 2026
Merged
Merged
aduh95 pushed a commit that referenced this pull request Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
dfda0f2
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
aduh95 pushed a commit that referenced this pull request Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
1ad7ca3
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@github-actionsgithub-actionsBot mentioned this pull request Aug 25, 2026
Merged
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@MoLowMoLowMoLow approved these changes

Assignees

No one assigned

Labels

author readyPRs with CI started, the required approvals, and no outstanding review comments.needs-ciPRs that need a full CI run.test_runnerIssues and PRs related to the test runner subsystem.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

test_runner: directory arguments to --test fail with MODULE_NOT_FOUND on Windows (regression since v20)

6 participants

@bitpshr@nodejs-github-bot@trivikr@MoLow@richardlau@atlowChemi
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
test_runner: restore directory search for --test - #64637
Closed
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Closed
test_runner: restore directory search for --test#64637
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Conversation
@bitpshr
@bitpshrbitpshr
commented
Jul 21, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Fixes#64555. Passing a directory to node --test (like node --test tests) matched the directory itself as a glob pattern and then tried to run it as a test file, failing with MODULE_NOT_FOUND.
This expands a pattern that resolves to a directory into a search for the default test files inside it, restoring the pre-glob behavior. File paths, real glob patterns, and nonexistent arguments all pass through unchanged.
Note: This isn't Windows-specific despite the report; it reproduces on every platform (on macOS, node@20 searches the directory and passes while node@22 and node@24 both fail).
@bitpshr
test_runner: restore directory search for --test
b48ff5b
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: nodejs#64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
@nodejs-github-bot
nodejs-github-bot
commented
Jul 21, 2026

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/test_runner
@bitpshrbitpshr
mentioned this pull request
Jul 21, 2026

Closed

@nodejs-github-botnodejs-github-bot
added

needs-ci
PRs that need a full CI run.
test_runner
Issues and PRs related to the test runner subsystem.
labels
Jul 21, 2026
@bitpshr
bitpshr
commented
Jul 21, 2026

Copy link


Copy Markdown

ContributorAuthor
Both CI failures look unrelated to this change. test-macOS failed on test-debugger-probe-script-throws.js in the "unusual chars folder" re-run step, and the aarch64 shared-boringssl build failed on test-repl-context.mjs with ERR_INSPECTOR_COMMAND: Inspector error -32000: Promise was collected (the log shows failed 1 out of 10, so it's flaky). This PR only touches test runner directory handling, and its own test passed. A re-run should clear them.
@bitpshr
bitpshr
commented
Aug 5, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar. It's been approved for a couple of weeks now, and it's a small test_runner fix (restoring directory arguments to node --test) with a regression test. @MoLow is there anything else needed to get it landed?
@atlowChemiatlowChemi
added
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@codecov
codecovBot
commented
Aug 6, 2026•

edited

Loading

Copy link


Copy Markdown

Codecov Report
✅ All modified and coverable lines are covered by tests.

✅ Project coverage is 90.13%. Comparing base (6071907) to head (b48ff5b).
⚠️ Report is 501 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@## main #64637 +/- ##
=======================================
Coverage 90.13% 90.13% =======================================
Files 741 741 Lines 242076 242095 +19 Branches 45550 45552 +2 =======================================
+ Hits 218199 218219 +20 + Misses 15391 15386 -5 - Partials 8486 8490 +4 
Files with missing linesCoverage Δ
lib/internal/test_runner/runner.js94.52% <100.00%> (+0.09%)⬆️
... and 24 files with indirect coverage changes
 🚀 New features to boost your workflow: 
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
@github-actionsgithub-actionsBot
removed
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 17, 2026
 Merged

@bitpshr
bitpshr
commented
Aug 17, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar, it has been approved and author ready for a few weeks now. Is anything blocking it from landing? Happy to rebase if it needs a refresh.
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 18, 2026
 Merged

12 tasks
@trivikrtrivikr
added
the 
author ready
PRs with CI started, the required approvals, and no outstanding review comments.
label
Aug 21, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76157/
@trivikrtrivikr
added
the 
commit-queue
PRs queued for automated landing through the Commit Queue.
label
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T15:26:07Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32505631714
@richardlaurichardlau
added

commit-queue
PRs queued for automated landing through the Commit Queue.
and removed

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
labels
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T17:05:44Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32512148725
@trivikrtrivikr
removed
the 
commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
label
Aug 21, 2026
trivikr pushed a commit
that referenced
this pull request
Aug 21, 2026
@bitpshr@trivikr
test_runner: restore directory search for --test
838a3e9
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@trivikr
trivikr
commented
Aug 21, 2026

Copy link


Copy Markdown

Member
Landed in 838a3e9
@trivikrtrivikr
closed this
Aug 21, 2026

This was referenced Aug 23, 2026
 Merged

 Merged

aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
dfda0f2
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
1ad7ca3
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@github-actionsgithub-actionsBot
mentioned this pull request
Aug 25, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@MoLowMoLowMoLow approved these changes

Assignees


No one assigned


Labels

author readyPRs with CI started, the required approvals, and no outstanding review comments.needs-ciPRs that need a full CI run.test_runnerIssues and PRs related to the test runner subsystem.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

test_runner: directory arguments to --test fail with MODULE_NOT_FOUND on Windows (regression since v20)


6 participants

@bitpshr@nodejs-github-bot@trivikr@MoLow@richardlau@atlowChemi

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
test_runner: restore directory search for --test - #64637
Closed
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Closed
test_runner: restore directory search for --test#64637
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Conversation
@bitpshr
@bitpshrbitpshr
commented
Jul 21, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Fixes#64555. Passing a directory to node --test (like node --test tests) matched the directory itself as a glob pattern and then tried to run it as a test file, failing with MODULE_NOT_FOUND.
This expands a pattern that resolves to a directory into a search for the default test files inside it, restoring the pre-glob behavior. File paths, real glob patterns, and nonexistent arguments all pass through unchanged.
Note: This isn't Windows-specific despite the report; it reproduces on every platform (on macOS, node@20 searches the directory and passes while node@22 and node@24 both fail).
@bitpshr
test_runner: restore directory search for --test
b48ff5b
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: nodejs#64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
@nodejs-github-bot
nodejs-github-bot
commented
Jul 21, 2026

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/test_runner
@bitpshrbitpshr
mentioned this pull request
Jul 21, 2026

Closed

@nodejs-github-botnodejs-github-bot
added

needs-ci
PRs that need a full CI run.
test_runner
Issues and PRs related to the test runner subsystem.
labels
Jul 21, 2026
@bitpshr
bitpshr
commented
Jul 21, 2026

Copy link


Copy Markdown

ContributorAuthor
Both CI failures look unrelated to this change. test-macOS failed on test-debugger-probe-script-throws.js in the "unusual chars folder" re-run step, and the aarch64 shared-boringssl build failed on test-repl-context.mjs with ERR_INSPECTOR_COMMAND: Inspector error -32000: Promise was collected (the log shows failed 1 out of 10, so it's flaky). This PR only touches test runner directory handling, and its own test passed. A re-run should clear them.
@bitpshr
bitpshr
commented
Aug 5, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar. It's been approved for a couple of weeks now, and it's a small test_runner fix (restoring directory arguments to node --test) with a regression test. @MoLow is there anything else needed to get it landed?
@atlowChemiatlowChemi
added
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@codecov
codecovBot
commented
Aug 6, 2026•

edited

Loading

Copy link


Copy Markdown

Codecov Report
✅ All modified and coverable lines are covered by tests.

✅ Project coverage is 90.13%. Comparing base (6071907) to head (b48ff5b).
⚠️ Report is 501 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@## main #64637 +/- ##
=======================================
Coverage 90.13% 90.13% =======================================
Files 741 741 Lines 242076 242095 +19 Branches 45550 45552 +2 =======================================
+ Hits 218199 218219 +20 + Misses 15391 15386 -5 - Partials 8486 8490 +4 
Files with missing linesCoverage Δ
lib/internal/test_runner/runner.js94.52% <100.00%> (+0.09%)⬆️
... and 24 files with indirect coverage changes
 🚀 New features to boost your workflow: 
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
@github-actionsgithub-actionsBot
removed
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 17, 2026
 Merged

@bitpshr
bitpshr
commented
Aug 17, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar, it has been approved and author ready for a few weeks now. Is anything blocking it from landing? Happy to rebase if it needs a refresh.
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 18, 2026
 Merged

12 tasks
@trivikrtrivikr
added
the 
author ready
PRs with CI started, the required approvals, and no outstanding review comments.
label
Aug 21, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76157/
@trivikrtrivikr
added
the 
commit-queue
PRs queued for automated landing through the Commit Queue.
label
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T15:26:07Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32505631714
@richardlaurichardlau
added

commit-queue
PRs queued for automated landing through the Commit Queue.
and removed

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
labels
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T17:05:44Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32512148725
@trivikrtrivikr
removed
the 
commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
label
Aug 21, 2026
trivikr pushed a commit
that referenced
this pull request
Aug 21, 2026
@bitpshr@trivikr
test_runner: restore directory search for --test
838a3e9
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@trivikr
trivikr
commented
Aug 21, 2026

Copy link


Copy Markdown

Member
Landed in 838a3e9
@trivikrtrivikr
closed this
Aug 21, 2026

This was referenced Aug 23, 2026
 Merged

 Merged

aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
dfda0f2
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
1ad7ca3
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@github-actionsgithub-actionsBot
mentioned this pull request
Aug 25, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@MoLowMoLowMoLow approved these changes

Assignees


No one assigned


Labels

author readyPRs with CI started, the required approvals, and no outstanding review comments.needs-ciPRs that need a full CI run.test_runnerIssues and PRs related to the test runner subsystem.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

test_runner: directory arguments to --test fail with MODULE_NOT_FOUND on Windows (regression since v20)


6 participants

@bitpshr@nodejs-github-bot@trivikr@MoLow@richardlau@atlowChemi

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
test_runner: restore directory search for --test - #64637
Closed
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Closed
test_runner: restore directory search for --test#64637
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Conversation
@bitpshr
@bitpshrbitpshr
commented
Jul 21, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Fixes#64555. Passing a directory to node --test (like node --test tests) matched the directory itself as a glob pattern and then tried to run it as a test file, failing with MODULE_NOT_FOUND.
This expands a pattern that resolves to a directory into a search for the default test files inside it, restoring the pre-glob behavior. File paths, real glob patterns, and nonexistent arguments all pass through unchanged.
Note: This isn't Windows-specific despite the report; it reproduces on every platform (on macOS, node@20 searches the directory and passes while node@22 and node@24 both fail).
@bitpshr
test_runner: restore directory search for --test
b48ff5b
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: nodejs#64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
@nodejs-github-bot
nodejs-github-bot
commented
Jul 21, 2026

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/test_runner
@bitpshrbitpshr
mentioned this pull request
Jul 21, 2026

Closed

@nodejs-github-botnodejs-github-bot
added

needs-ci
PRs that need a full CI run.
test_runner
Issues and PRs related to the test runner subsystem.
labels
Jul 21, 2026
@bitpshr
bitpshr
commented
Jul 21, 2026

Copy link


Copy Markdown

ContributorAuthor
Both CI failures look unrelated to this change. test-macOS failed on test-debugger-probe-script-throws.js in the "unusual chars folder" re-run step, and the aarch64 shared-boringssl build failed on test-repl-context.mjs with ERR_INSPECTOR_COMMAND: Inspector error -32000: Promise was collected (the log shows failed 1 out of 10, so it's flaky). This PR only touches test runner directory handling, and its own test passed. A re-run should clear them.
@bitpshr
bitpshr
commented
Aug 5, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar. It's been approved for a couple of weeks now, and it's a small test_runner fix (restoring directory arguments to node --test) with a regression test. @MoLow is there anything else needed to get it landed?
@atlowChemiatlowChemi
added
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@codecov
codecovBot
commented
Aug 6, 2026•

edited

Loading

Copy link


Copy Markdown

Codecov Report
✅ All modified and coverable lines are covered by tests.

✅ Project coverage is 90.13%. Comparing base (6071907) to head (b48ff5b).
⚠️ Report is 501 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@## main #64637 +/- ##
=======================================
Coverage 90.13% 90.13% =======================================
Files 741 741 Lines 242076 242095 +19 Branches 45550 45552 +2 =======================================
+ Hits 218199 218219 +20 + Misses 15391 15386 -5 - Partials 8486 8490 +4 
Files with missing linesCoverage Δ
lib/internal/test_runner/runner.js94.52% <100.00%> (+0.09%)⬆️
... and 24 files with indirect coverage changes
 🚀 New features to boost your workflow: 
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
@github-actionsgithub-actionsBot
removed
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 17, 2026
 Merged

@bitpshr
bitpshr
commented
Aug 17, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar, it has been approved and author ready for a few weeks now. Is anything blocking it from landing? Happy to rebase if it needs a refresh.
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 18, 2026
 Merged

12 tasks
@trivikrtrivikr
added
the 
author ready
PRs with CI started, the required approvals, and no outstanding review comments.
label
Aug 21, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76157/
@trivikrtrivikr
added
the 
commit-queue
PRs queued for automated landing through the Commit Queue.
label
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T15:26:07Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32505631714
@richardlaurichardlau
added

commit-queue
PRs queued for automated landing through the Commit Queue.
and removed

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
labels
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T17:05:44Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32512148725
@trivikrtrivikr
removed
the 
commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
label
Aug 21, 2026
trivikr pushed a commit
that referenced
this pull request
Aug 21, 2026
@bitpshr@trivikr
test_runner: restore directory search for --test
838a3e9
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@trivikr
trivikr
commented
Aug 21, 2026

Copy link


Copy Markdown

Member
Landed in 838a3e9
@trivikrtrivikr
closed this
Aug 21, 2026

This was referenced Aug 23, 2026
 Merged

 Merged

aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
dfda0f2
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
1ad7ca3
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@github-actionsgithub-actionsBot
mentioned this pull request
Aug 25, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@MoLowMoLowMoLow approved these changes

Assignees


No one assigned


Labels

author readyPRs with CI started, the required approvals, and no outstanding review comments.needs-ciPRs that need a full CI run.test_runnerIssues and PRs related to the test runner subsystem.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

test_runner: directory arguments to --test fail with MODULE_NOT_FOUND on Windows (regression since v20)


6 participants

@bitpshr@nodejs-github-bot@trivikr@MoLow@richardlau@atlowChemi

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
test_runner: restore directory search for --test - #64637
Closed
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Closed
test_runner: restore directory search for --test#64637
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Conversation
@bitpshr
@bitpshrbitpshr
commented
Jul 21, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Fixes#64555. Passing a directory to node --test (like node --test tests) matched the directory itself as a glob pattern and then tried to run it as a test file, failing with MODULE_NOT_FOUND.
This expands a pattern that resolves to a directory into a search for the default test files inside it, restoring the pre-glob behavior. File paths, real glob patterns, and nonexistent arguments all pass through unchanged.
Note: This isn't Windows-specific despite the report; it reproduces on every platform (on macOS, node@20 searches the directory and passes while node@22 and node@24 both fail).
@bitpshr
test_runner: restore directory search for --test
b48ff5b
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: nodejs#64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
@nodejs-github-bot
nodejs-github-bot
commented
Jul 21, 2026

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/test_runner
@bitpshrbitpshr
mentioned this pull request
Jul 21, 2026

Closed

@nodejs-github-botnodejs-github-bot
added

needs-ci
PRs that need a full CI run.
test_runner
Issues and PRs related to the test runner subsystem.
labels
Jul 21, 2026
@bitpshr
bitpshr
commented
Jul 21, 2026

Copy link


Copy Markdown

ContributorAuthor
Both CI failures look unrelated to this change. test-macOS failed on test-debugger-probe-script-throws.js in the "unusual chars folder" re-run step, and the aarch64 shared-boringssl build failed on test-repl-context.mjs with ERR_INSPECTOR_COMMAND: Inspector error -32000: Promise was collected (the log shows failed 1 out of 10, so it's flaky). This PR only touches test runner directory handling, and its own test passed. A re-run should clear them.
@bitpshr
bitpshr
commented
Aug 5, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar. It's been approved for a couple of weeks now, and it's a small test_runner fix (restoring directory arguments to node --test) with a regression test. @MoLow is there anything else needed to get it landed?
@atlowChemiatlowChemi
added
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@codecov
codecovBot
commented
Aug 6, 2026•

edited

Loading

Copy link


Copy Markdown

Codecov Report
✅ All modified and coverable lines are covered by tests.

✅ Project coverage is 90.13%. Comparing base (6071907) to head (b48ff5b).
⚠️ Report is 501 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@## main #64637 +/- ##
=======================================
Coverage 90.13% 90.13% =======================================
Files 741 741 Lines 242076 242095 +19 Branches 45550 45552 +2 =======================================
+ Hits 218199 218219 +20 + Misses 15391 15386 -5 - Partials 8486 8490 +4 
Files with missing linesCoverage Δ
lib/internal/test_runner/runner.js94.52% <100.00%> (+0.09%)⬆️
... and 24 files with indirect coverage changes
 🚀 New features to boost your workflow: 
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
@github-actionsgithub-actionsBot
removed
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 17, 2026
 Merged

@bitpshr
bitpshr
commented
Aug 17, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar, it has been approved and author ready for a few weeks now. Is anything blocking it from landing? Happy to rebase if it needs a refresh.
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 18, 2026
 Merged

12 tasks
@trivikrtrivikr
added
the 
author ready
PRs with CI started, the required approvals, and no outstanding review comments.
label
Aug 21, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76157/
@trivikrtrivikr
added
the 
commit-queue
PRs queued for automated landing through the Commit Queue.
label
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T15:26:07Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32505631714
@richardlaurichardlau
added

commit-queue
PRs queued for automated landing through the Commit Queue.
and removed

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
labels
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T17:05:44Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32512148725
@trivikrtrivikr
removed
the 
commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
label
Aug 21, 2026
trivikr pushed a commit
that referenced
this pull request
Aug 21, 2026
@bitpshr@trivikr
test_runner: restore directory search for --test
838a3e9
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@trivikr
trivikr
commented
Aug 21, 2026

Copy link


Copy Markdown

Member
Landed in 838a3e9
@trivikrtrivikr
closed this
Aug 21, 2026

This was referenced Aug 23, 2026
 Merged

 Merged

aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
dfda0f2
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
1ad7ca3
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@github-actionsgithub-actionsBot
mentioned this pull request
Aug 25, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@MoLowMoLowMoLow approved these changes

Assignees


No one assigned


Labels

author readyPRs with CI started, the required approvals, and no outstanding review comments.needs-ciPRs that need a full CI run.test_runnerIssues and PRs related to the test runner subsystem.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

test_runner: directory arguments to --test fail with MODULE_NOT_FOUND on Windows (regression since v20)


6 participants

@bitpshr@nodejs-github-bot@trivikr@MoLow@richardlau@atlowChemi

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
test_runner: restore directory search for --test - #64637
Closed
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Closed
test_runner: restore directory search for --test#64637
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Conversation
@bitpshr
@bitpshrbitpshr
commented
Jul 21, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Fixes#64555. Passing a directory to node --test (like node --test tests) matched the directory itself as a glob pattern and then tried to run it as a test file, failing with MODULE_NOT_FOUND.
This expands a pattern that resolves to a directory into a search for the default test files inside it, restoring the pre-glob behavior. File paths, real glob patterns, and nonexistent arguments all pass through unchanged.
Note: This isn't Windows-specific despite the report; it reproduces on every platform (on macOS, node@20 searches the directory and passes while node@22 and node@24 both fail).
@bitpshr
test_runner: restore directory search for --test
b48ff5b
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: nodejs#64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
@nodejs-github-bot
nodejs-github-bot
commented
Jul 21, 2026

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/test_runner
@bitpshrbitpshr
mentioned this pull request
Jul 21, 2026

Closed

@nodejs-github-botnodejs-github-bot
added

needs-ci
PRs that need a full CI run.
test_runner
Issues and PRs related to the test runner subsystem.
labels
Jul 21, 2026
@bitpshr
bitpshr
commented
Jul 21, 2026

Copy link


Copy Markdown

ContributorAuthor
Both CI failures look unrelated to this change. test-macOS failed on test-debugger-probe-script-throws.js in the "unusual chars folder" re-run step, and the aarch64 shared-boringssl build failed on test-repl-context.mjs with ERR_INSPECTOR_COMMAND: Inspector error -32000: Promise was collected (the log shows failed 1 out of 10, so it's flaky). This PR only touches test runner directory handling, and its own test passed. A re-run should clear them.
@bitpshr
bitpshr
commented
Aug 5, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar. It's been approved for a couple of weeks now, and it's a small test_runner fix (restoring directory arguments to node --test) with a regression test. @MoLow is there anything else needed to get it landed?
@atlowChemiatlowChemi
added
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@codecov
codecovBot
commented
Aug 6, 2026•

edited

Loading

Copy link


Copy Markdown

Codecov Report
✅ All modified and coverable lines are covered by tests.

✅ Project coverage is 90.13%. Comparing base (6071907) to head (b48ff5b).
⚠️ Report is 501 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@## main #64637 +/- ##
=======================================
Coverage 90.13% 90.13% =======================================
Files 741 741 Lines 242076 242095 +19 Branches 45550 45552 +2 =======================================
+ Hits 218199 218219 +20 + Misses 15391 15386 -5 - Partials 8486 8490 +4 
Files with missing linesCoverage Δ
lib/internal/test_runner/runner.js94.52% <100.00%> (+0.09%)⬆️
... and 24 files with indirect coverage changes
 🚀 New features to boost your workflow: 
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
@github-actionsgithub-actionsBot
removed
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 17, 2026
 Merged

@bitpshr
bitpshr
commented
Aug 17, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar, it has been approved and author ready for a few weeks now. Is anything blocking it from landing? Happy to rebase if it needs a refresh.
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 18, 2026
 Merged

12 tasks
@trivikrtrivikr
added
the 
author ready
PRs with CI started, the required approvals, and no outstanding review comments.
label
Aug 21, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76157/
@trivikrtrivikr
added
the 
commit-queue
PRs queued for automated landing through the Commit Queue.
label
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T15:26:07Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32505631714
@richardlaurichardlau
added

commit-queue
PRs queued for automated landing through the Commit Queue.
and removed

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
labels
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T17:05:44Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32512148725
@trivikrtrivikr
removed
the 
commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
label
Aug 21, 2026
trivikr pushed a commit
that referenced
this pull request
Aug 21, 2026
@bitpshr@trivikr
test_runner: restore directory search for --test
838a3e9
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@trivikr
trivikr
commented
Aug 21, 2026

Copy link


Copy Markdown

Member
Landed in 838a3e9
@trivikrtrivikr
closed this
Aug 21, 2026

This was referenced Aug 23, 2026
 Merged

 Merged

aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
dfda0f2
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
1ad7ca3
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@github-actionsgithub-actionsBot
mentioned this pull request
Aug 25, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@MoLowMoLowMoLow approved these changes

Assignees


No one assigned


Labels

author readyPRs with CI started, the required approvals, and no outstanding review comments.needs-ciPRs that need a full CI run.test_runnerIssues and PRs related to the test runner subsystem.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

test_runner: directory arguments to --test fail with MODULE_NOT_FOUND on Windows (regression since v20)


6 participants

@bitpshr@nodejs-github-bot@trivikr@MoLow@richardlau@atlowChemi

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
test_runner: restore directory search for --test - #64637
Closed
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Closed
test_runner: restore directory search for --test#64637
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Conversation
@bitpshr
@bitpshrbitpshr
commented
Jul 21, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Fixes#64555. Passing a directory to node --test (like node --test tests) matched the directory itself as a glob pattern and then tried to run it as a test file, failing with MODULE_NOT_FOUND.
This expands a pattern that resolves to a directory into a search for the default test files inside it, restoring the pre-glob behavior. File paths, real glob patterns, and nonexistent arguments all pass through unchanged.
Note: This isn't Windows-specific despite the report; it reproduces on every platform (on macOS, node@20 searches the directory and passes while node@22 and node@24 both fail).
@bitpshr
test_runner: restore directory search for --test
b48ff5b
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: nodejs#64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
@nodejs-github-bot
nodejs-github-bot
commented
Jul 21, 2026

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/test_runner
@bitpshrbitpshr
mentioned this pull request
Jul 21, 2026

Closed

@nodejs-github-botnodejs-github-bot
added

needs-ci
PRs that need a full CI run.
test_runner
Issues and PRs related to the test runner subsystem.
labels
Jul 21, 2026
@bitpshr
bitpshr
commented
Jul 21, 2026

Copy link


Copy Markdown

ContributorAuthor
Both CI failures look unrelated to this change. test-macOS failed on test-debugger-probe-script-throws.js in the "unusual chars folder" re-run step, and the aarch64 shared-boringssl build failed on test-repl-context.mjs with ERR_INSPECTOR_COMMAND: Inspector error -32000: Promise was collected (the log shows failed 1 out of 10, so it's flaky). This PR only touches test runner directory handling, and its own test passed. A re-run should clear them.
@bitpshr
bitpshr
commented
Aug 5, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar. It's been approved for a couple of weeks now, and it's a small test_runner fix (restoring directory arguments to node --test) with a regression test. @MoLow is there anything else needed to get it landed?
@atlowChemiatlowChemi
added
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@codecov
codecovBot
commented
Aug 6, 2026•

edited

Loading

Copy link


Copy Markdown

Codecov Report
✅ All modified and coverable lines are covered by tests.

✅ Project coverage is 90.13%. Comparing base (6071907) to head (b48ff5b).
⚠️ Report is 501 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@## main #64637 +/- ##
=======================================
Coverage 90.13% 90.13% =======================================
Files 741 741 Lines 242076 242095 +19 Branches 45550 45552 +2 =======================================
+ Hits 218199 218219 +20 + Misses 15391 15386 -5 - Partials 8486 8490 +4 
Files with missing linesCoverage Δ
lib/internal/test_runner/runner.js94.52% <100.00%> (+0.09%)⬆️
... and 24 files with indirect coverage changes
 🚀 New features to boost your workflow: 
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
@github-actionsgithub-actionsBot
removed
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 17, 2026
 Merged

@bitpshr
bitpshr
commented
Aug 17, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar, it has been approved and author ready for a few weeks now. Is anything blocking it from landing? Happy to rebase if it needs a refresh.
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 18, 2026
 Merged

12 tasks
@trivikrtrivikr
added
the 
author ready
PRs with CI started, the required approvals, and no outstanding review comments.
label
Aug 21, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76157/
@trivikrtrivikr
added
the 
commit-queue
PRs queued for automated landing through the Commit Queue.
label
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T15:26:07Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32505631714
@richardlaurichardlau
added

commit-queue
PRs queued for automated landing through the Commit Queue.
and removed

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
labels
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T17:05:44Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32512148725
@trivikrtrivikr
removed
the 
commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
label
Aug 21, 2026
trivikr pushed a commit
that referenced
this pull request
Aug 21, 2026
@bitpshr@trivikr
test_runner: restore directory search for --test
838a3e9
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@trivikr
trivikr
commented
Aug 21, 2026

Copy link


Copy Markdown

Member
Landed in 838a3e9
@trivikrtrivikr
closed this
Aug 21, 2026

This was referenced Aug 23, 2026
 Merged

 Merged

aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
dfda0f2
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
1ad7ca3
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@github-actionsgithub-actionsBot
mentioned this pull request
Aug 25, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@MoLowMoLowMoLow approved these changes

Assignees


No one assigned


Labels

author readyPRs with CI started, the required approvals, and no outstanding review comments.needs-ciPRs that need a full CI run.test_runnerIssues and PRs related to the test runner subsystem.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

test_runner: directory arguments to --test fail with MODULE_NOT_FOUND on Windows (regression since v20)


6 participants

@bitpshr@nodejs-github-bot@trivikr@MoLow@richardlau@atlowChemi

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
test_runner: restore directory search for --test - #64637
Closed
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Closed
test_runner: restore directory search for --test#64637
bitpshr wants to merge 1 commit into
nodejs:mainfrom 
bitpshr:test-runner/dir-arg-search
Conversation
@bitpshr
@bitpshrbitpshr
commented
Jul 21, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Fixes#64555. Passing a directory to node --test (like node --test tests) matched the directory itself as a glob pattern and then tried to run it as a test file, failing with MODULE_NOT_FOUND.
This expands a pattern that resolves to a directory into a search for the default test files inside it, restoring the pre-glob behavior. File paths, real glob patterns, and nonexistent arguments all pass through unchanged.
Note: This isn't Windows-specific despite the report; it reproduces on every platform (on macOS, node@20 searches the directory and passes while node@22 and node@24 both fail).
@bitpshr
test_runner: restore directory search for --test
b48ff5b
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: nodejs#64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
@nodejs-github-bot
nodejs-github-bot
commented
Jul 21, 2026

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/test_runner
@bitpshrbitpshr
mentioned this pull request
Jul 21, 2026

Closed

@nodejs-github-botnodejs-github-bot
added

needs-ci
PRs that need a full CI run.
test_runner
Issues and PRs related to the test runner subsystem.
labels
Jul 21, 2026
@bitpshr
bitpshr
commented
Jul 21, 2026

Copy link


Copy Markdown

ContributorAuthor
Both CI failures look unrelated to this change. test-macOS failed on test-debugger-probe-script-throws.js in the "unusual chars folder" re-run step, and the aarch64 shared-boringssl build failed on test-repl-context.mjs with ERR_INSPECTOR_COMMAND: Inspector error -32000: Promise was collected (the log shows failed 1 out of 10, so it's flaky). This PR only touches test runner directory handling, and its own test passed. A re-run should clear them.
@bitpshr
bitpshr
commented
Aug 5, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar. It's been approved for a couple of weeks now, and it's a small test_runner fix (restoring directory arguments to node --test) with a regression test. @MoLow is there anything else needed to get it landed?
@atlowChemiatlowChemi
added
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@codecov
codecovBot
commented
Aug 6, 2026•

edited

Loading

Copy link


Copy Markdown

Codecov Report
✅ All modified and coverable lines are covered by tests.

✅ Project coverage is 90.13%. Comparing base (6071907) to head (b48ff5b).
⚠️ Report is 501 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@## main #64637 +/- ##
=======================================
Coverage 90.13% 90.13% =======================================
Files 741 741 Lines 242076 242095 +19 Branches 45550 45552 +2 =======================================
+ Hits 218199 218219 +20 + Misses 15391 15386 -5 - Partials 8486 8490 +4 
Files with missing linesCoverage Δ
lib/internal/test_runner/runner.js94.52% <100.00%> (+0.09%)⬆️
... and 24 files with indirect coverage changes
 🚀 New features to boost your workflow: 
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
@github-actionsgithub-actionsBot
removed
the 
request-ci
Add this label to start a Jenkins CI on a PR.
label
Aug 6, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 17, 2026
 Merged

@bitpshr
bitpshr
commented
Aug 17, 2026

Copy link


Copy Markdown

ContributorAuthor
Just keeping this on the radar, it has been approved and author ready for a few weeks now. Is anything blocking it from landing? Happy to rebase if it needs a refresh.
@coderabbitaicoderabbitaiBot
mentioned this pull request
Aug 18, 2026
 Merged

12 tasks
@trivikrtrivikr
added
the 
author ready
PRs with CI started, the required approvals, and no outstanding review comments.
label
Aug 21, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76157/
@trivikrtrivikr
added
the 
commit-queue
PRs queued for automated landing through the Commit Queue.
label
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T15:26:07Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32505631714
@richardlaurichardlau
added

commit-queue
PRs queued for automated landing through the Commit Queue.
and removed

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
labels
Aug 21, 2026
@nodejs-github-botnodejs-github-bot
added

commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
and removed

commit-queue
PRs queued for automated landing through the Commit Queue.
labels
Aug 21, 2026
@nodejs-github-bot
nodejs-github-bot
commented
Aug 21, 2026

Copy link


Copy Markdown

Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/64637
✔ Done loading data for nodejs/node/pull/64637
----------------------------------- PR info ------------------------------------
Title test_runner: restore directory search for --test (#64637)
⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch bitpshr:test-runner/dir-arg-search -> nodejs:main
Labels author ready, needs-ci, commit-queue, test_runner
Commits 1
- test_runner: restore directory search for --test
Committers 1
- Paul Bouchon <mail@bitpshr.net>
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
--------------------------------------------------------------------------------
ℹ This PR was created on Tue, 21 Jul 2026 03:18:10 GMT
✔ Approvals: 1
✔ - Moshe Atlow (@MoLow): https://github.com/nodejs/node/pull/64637#pullrequestreview-4743076856
✘ GitHub CI is still running
ℹ Last Full PR CI on 2026-08-21T17:05:44Z: https://ci.nodejs.org/job/node-test-pull-request/76157/
- Querying data for job/node-test-pull-request/76157/
✔ Build data downloaded
✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32512148725
@trivikrtrivikr
removed
the 
commit-queue-failed
PRs whose Commit Queue landing failed and need manual intervention before retrying.
label
Aug 21, 2026
trivikr pushed a commit
that referenced
this pull request
Aug 21, 2026
@bitpshr@trivikr
test_runner: restore directory search for --test
838a3e9
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@trivikr
trivikr
commented
Aug 21, 2026

Copy link


Copy Markdown

Member
Landed in 838a3e9
@trivikrtrivikr
closed this
Aug 21, 2026

This was referenced Aug 23, 2026
 Merged

 Merged

aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
dfda0f2
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
aduh95 pushed a commit
that referenced
this pull request
Aug 25, 2026
@bitpshr@aduh95
test_runner: restore directory search for --test
1ad7ca3
Passing a directory to `node --test` (e.g. `node --test tests`) matched
the directory itself as a glob pattern and then tried to run it as a
test file, failing with MODULE_NOT_FOUND. Before glob patterns were
supported, a directory argument was searched for test files within it.
Expand a pattern that resolves to a directory into a search for the
default test files inside it. Despite the report framing this as
Windows-only, it reproduces on every platform: it is a plain
regression from when directory arguments stopped being searched.
Fixes: #64555
Signed-off-by: Paul Bouchon <mail@bitpshr.net>
PR-URL: #64637
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
@github-actionsgithub-actionsBot
mentioned this pull request
Aug 25, 2026
 Merged

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@MoLowMoLowMoLow approved these changes

Assignees


No one assigned


Labels

author readyPRs with CI started, the required approvals, and no outstanding review comments.needs-ciPRs that need a full CI run.test_runnerIssues and PRs related to the test runner subsystem.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

test_runner: directory arguments to --test fail with MODULE_NOT_FOUND on Windows (regression since v20)


6 participants

@bitpshr@nodejs-github-bot@trivikr@MoLow@richardlau@atlowChemi