Skip to content

Commit

Permalink
doc: add minutes for meeting 20 Dec 2023 (#1484)
Browse files Browse the repository at this point in the history
Signed-off-by: Michael Dawson <midawson@redhat.com>
  • Loading branch information
mhdawson authored Jan 5, 2024
1 parent 3ff37a5 commit 8a5906a
Showing 1 changed file with 75 additions and 0 deletions.
75 changes: 75 additions & 0 deletions meetings/2023-12-20.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
# Node.js Technical Steering Committee (TSC) Meeting 2023-12-20

## Links

* **Recording**: <https://www.youtube.com/watch?v=_OAt6LMqhFE>
* **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1483>

## Present

* Antoine du Hamel @aduh95 (voting member)
* Benjamin Gruenbaum @benjamingr (voting member)
* Ruben Bridgewater @BridgeAR (voting member)
* Joyee Cheung @joyeecheung (voting member)
* Chengzhong Wu @legendecas (voting member)
* Matteo Collina @mcollina (voting member)
* Michael Dawson @mhdawson (voting member)
* Rafael Gonzaga @RafaelGSS (voting member)
* Richard Lau @richardlau (voting member)
* Robert Nagy @ronag (voting member)

## Agenda

### Announcements

* Matteo - thinking of doing collab summit in April before CityJS, still not looked in but working on it, so good to pencil it into your calendar.
* Matteo, if there is a good event in NA for a collab summit please let us know.

### CPC and Board Meeting Updates

*Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting.

### nodejs/node

* Inconsistent behavior of nextTick and queueMicrotask [#51156](https://github.com/nodejs/node/issues/51156)
* Matteo
* today we say when you emit errors, you should do it in NextTick so that people can register event handlers to catch them.
* Unfortunately this does not play well with promises. Tried out a fix, but broke many tests
* Fix was to invert the position of the two microtasks/nextTick
* Robert, problem is that we have a bug that causes a lot of subtle behaviors, depends on whether you are calling from SetImmediate or microtask context it you can get different behavior.
* Only way to fix it is to break a lot of code
* Benjamin, these kinds of timing bugs are really tricky to fix. Not convinced the fix actually works, just moves the problem to somewhere else. We should make sure that all of our APIs emit in the right place
* Matteo will post the diff
* Tagged for visibility
* Michael, is this unspecified or is there some reason to depend on ordering
* Robert, unspecified, but too easy to shoot yourself in the foot

* enable corepack by default [#50963](https://github.com/nodejs/node/issues/50963)
* Original question was if we can make its use easier
* Clear that npm does not want to be distributed through corepack
* Antoine: gave an overview
* Call is for people to comment on the issue

* lib: promote process.binding/_tickCallback to runtime deprecation [#50687](https://github.com/nodejs/node/pull/50687)
* <https://github.com/nodejs/TSC/issues/1482> was opened to discuss plan, please jump in there to and comment/discuss
* Joyee please review/comment in the issue

### nodejs/admin

* Events / Collaborator Summits for 2024 [#814](https://github.com/nodejs/admin/issues/814)
* Discussed a bit in the announcement parts at the beginning.
* Joyee just waiting on confirmation of venue

## Strategic Initiatives

* Antoine - core promise APIs, no update this week
* Chengzhong - shadow realm , no update
* Michael - Next 10, no update
* Joyee - startup snapshot, landed configuration support <https://github.com/nodejs/node/pull/50453>
* Benjamin - Primordials, no update

## Upcoming Meetings

* **Node.js Project Calendar**: <https://nodejs.org/calendar>

Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.

0 comments on commit 8a5906a

Please sign in to comment.