loaders
loaders copied to clipboard
nodejs
Node.js Loaders Team Meeting 2023-06-06
Time
UTC Tue 06-Jun-2023 18:00 (06:00 PM):
| Timezone | Date/Time |
|---|---|
| US / Pacific | Tue 06-Jun-2023 11:00 (11:00 AM) |
| US / Mountain | Tue 06-Jun-2023 12:00 (12:00 PM) |
| US / Central | Tue 06-Jun-2023 13:00 (01:00 PM) |
| US / Eastern | Tue 06-Jun-2023 14:00 (02:00 PM) |
| EU / Western | Tue 06-Jun-2023 19:00 (07:00 PM) |
| EU / Central | Tue 06-Jun-2023 20:00 (08:00 PM) |
| EU / Eastern | Tue 06-Jun-2023 21:00 (09:00 PM) |
| Moscow | Tue 06-Jun-2023 21:00 (09:00 PM) |
| Chennai | Tue 06-Jun-2023 23:30 (11:30 PM) |
| Hangzhou | Wed 07-Jun-2023 02:00 (02:00 AM) |
| Tokyo | Wed 07-Jun-2023 03:00 (03:00 AM) |
| Sydney | Wed 07-Jun-2023 04:00 (04:00 AM) |
Or in your local time:
- https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Loaders%20Team+Meeting+2023-06-06&iso=20230606T1800
- or https://www.wolframalpha.com/input/?i=06PM+UTC%2C+Jun+06%2C+2023+in+local+time
Links
- Minutes Google Doc: https://docs.google.com/document/d/1REVBirIaUVmYG85yDTFxLyh0SJZzbt62oa9uD-r-rY8/edit
Agenda
Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
- console.log failure while working with worker threads. #30491
Invited
- Loaders team: @nodejs/loaders
Observers/Guests
Notes
The agenda comes from issues labelled with loaders-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting
-
link for participants: https://zoom.us/j/97506450082
-
For those who just want to watch: https://www.youtube.com/c/nodejs+foundation/live
I took the loaders agenda label off of https://github.com/nodejs/node/issues/30491 since it’s been on for a few meetings now. I don’t know of any issues to discuss, but happy to meet if others want to.
I think we're in a daisy-chain of blocked—some broken test (that has nothing to do with ESM) is blocking @aduh95's PR which apparently blocks everything else? So we're in a holding pattern til that broken test is fixed.
In the meantime we can at least get register ready to land as soon as the upstream blocks are resolved. Is there anything left to do for that one?
If not, we could do the follow-up of merging the classes and removing the need for --loader. If that follow-up is small enough it could even just be merged into the main register PR.
I believe the register PR is done (just waiting for upstream PRs to land and unblock it).
I could branch off that PR to start the reunification stuff; that usually makes me nervous, but maybe it's okay here. (I think it should be kept atomic in a separate PR)