-
-
Notifications
You must be signed in to change notification settings - Fork 6
doc(minutes): add 11 Mar 2026 #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+25
−0
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| # 11 March 2026 | ||
|
|
||
| ## Attendees | ||
|
|
||
| * Diogo de Souza [@sozua](https://github.com/sozua) | ||
| * Jacob Smith [@JakobJingleheimer](https://github.com/JakobJingleheimer) (chair) | ||
| * Pietro Marchini [@pmarchini](https://github.com/pmarchini) | ||
|
|
||
| ## Topics | ||
|
|
||
| * doc(proposal): un/break --test [nodejs/test-runner#13](https://github.com/nodejs/test-runner/pull/13) | ||
| * change test flag to subcommand? `node --test` → `node test` | ||
| * High-impact suggestions from Colin [nodejs/test-runner#21](https://github.com/nodejs/test-runner/issues/21) | ||
|
|
||
| ## Outcomes | ||
|
|
||
| * From a technical standpoint, a `test` subcommand appears to be much easier than we expected. | ||
| * 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`) | ||
|
|
||
| ## Todos | ||
|
|
||
| * @JakobJingleheimer: To ask around about lack of subcommands | ||
| * Antoine FtW: it's indeed because of the breaking change suspected in the above discussion. | ||
| * @JakobJingleheimer: To keep an ear to the ground for the TC39 discussion about relaxing the requirement for dynamic import to always return the same. | ||
| * 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. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I couldn't attend the meeting.
This was also discussed back when Yagiz added
node --runand in nodejs/node#53483Seems relevant as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huzzah! There is where that discussion was! I knew I wasn't crazy. Thank you 🙏