Skip to content

Commit 54d0686

Browse files
doc(minutes): add 11 Mar 2026 (#22)
1 parent 51e3791 commit 54d0686

1 file changed

Lines changed: 25 additions & 0 deletions

File tree

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# 11 March 2026
2+
3+
## Attendees
4+
5+
* Diogo de Souza [@sozua](https://github.com/sozua)
6+
* Jacob Smith [@JakobJingleheimer](https://github.com/JakobJingleheimer) (chair)
7+
* Pietro Marchini [@pmarchini](https://github.com/pmarchini)
8+
9+
## Topics
10+
11+
* doc(proposal): un/break --test [nodejs/test-runner#13](https://github.com/nodejs/test-runner/pull/13)
12+
* change test flag to subcommand? `node --test``node test`
13+
* High-impact suggestions from Colin [nodejs/test-runner#21](https://github.com/nodejs/test-runner/issues/21)
14+
15+
## Outcomes
16+
17+
* From a technical standpoint, a `test` subcommand appears to be much easier than we expected.
18+
* It's however not obvious why this is not used more. We suspect it might be due to the breaking change where `node test` would have run `node ./test.js` (or `node ./test/index.js`)
19+
20+
## Todos
21+
22+
* @JakobJingleheimer: To ask around about lack of subcommands
23+
* Antoine FtW: it's indeed because of the breaking change suspected in the above discussion.
24+
* @JakobJingleheimer: To keep an ear to the ground for the TC39 discussion about relaxing the requirement for dynamic import to always return the same.
25+
* Consolidate `defaultExport` & `namedExports` [nodejs/node#61727](https://github.com/nodejs/node/pull/61727) needs some reviews and some opinions on whether old or new should "win" a conflict.

0 commit comments

Comments
 (0)