Repository navigation
Node.js Loaders Team Meeting 2023-10-24 #167
Description
Time
UTC Tue 24-Oct-2023 18:00 (06:00 PM):
| Timezone | Date/Time |
|---|---|
| US / Pacific | Tue 24-Oct-2023 11:00 (11:00 AM) |
| US / Mountain | Tue 24-Oct-2023 12:00 (12:00 PM) |
| US / Central | Tue 24-Oct-2023 13:00 (01:00 PM) |
| US / Eastern | Tue 24-Oct-2023 14:00 (02:00 PM) |
| EU / Western | Tue 24-Oct-2023 19:00 (07:00 PM) |
| EU / Central | Tue 24-Oct-2023 20:00 (08:00 PM) |
| EU / Eastern | Tue 24-Oct-2023 21:00 (09:00 PM) |
| Moscow | Tue 24-Oct-2023 21:00 (09:00 PM) |
| Chennai | Tue 24-Oct-2023 23:30 (11:30 PM) |
| Hangzhou | Wed 25-Oct-2023 02:00 (02:00 AM) |
| Tokyo | Wed 25-Oct-2023 03:00 (03:00 AM) |
| Sydney | Wed 25-Oct-2023 05:00 (05:00 AM) |
Or in your local time:
- https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Loaders%20Team+Meeting+2023-10-24&iso=20231024T1800
- or https://www.wolframalpha.com/input/?i=06PM+UTC%2C+Oct+24%2C+2023+in+local+time
Links
- Minutes Google Doc: https://docs.google.com/document/d/1SSuX_JzlW0tSEMoVRNYDLnynic4WeJQwzuXP_a_gQUw/edit
Agenda
Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
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
Metadata
Metadata
Assignees
Labels
No labels
Activity
GeoffreyBooth commentedon Oct 21, 2023
Anything we want to discuss?
Next steps after esm: detect ESM syntax in ambiguous JavaScript node#50096: should we remove
--experimental-default-typenow? I don’t see the point of having it if we have ESM syntax detection?We were hoping to clean up a bunch of things as part of the switch to
--default-type=moduleby default, namely cutting out some “include the CommonJS loader here to allow for monkey patching” hacks that have had TODOs to deprecate for years. If detection becomes the new way forward, how will we do this cleanup? Perhaps we set the module customization hooks stable by December hopefully, and just do the cleanup as a semver-major to ship in 22.0.0?I think the next big goal for regular modules code would be to finally remove the CommonJS loader. That means getting all the tests to pass if
shouldUseESMLoaderalways returnstrue(as in, we use the ESM loader for all entry points). Currently I get 154 failures if you do this; the bulk of these areasync_hookstests that fail because of async resources created by the ESM loader as part of startup. See [DO NOT MERGE] test: duplicate async_hooks tests in esm node#44323.Import Maps Implementation Plan #168
module: improve external format support node#49704
ESM Loader Hooks (20.8) should support a more testable, less stateful design node#50042
module: initialize hook returns load, resolve node#50044
JakobJingleheimer commentedon Oct 23, 2023
I feel like there are some open questions for initialize's return and external formats. Perhaps we quickly discuss those?
I the we're in agreement for the rest—they're just a matter of doing it.
GeoffreyBooth commentedon Oct 23, 2023
Sure. @ggoodman, are you available to join this meeting?
ggoodman commentedon Oct 23, 2023
Sure, I'll try to make it.
GeoffreyBooth commentedon Oct 24, 2023
#169