Ask questionsNode.js Foundation Modules Team Meeting 2019-10-23
UTC Wed 23-Oct-2019 19:00 (07:00 PM):
|US / Pacific||Wed 23-Oct-2019 12:00 (12:00 PM)|
|US / Mountain||Wed 23-Oct-2019 13:00 (01:00 PM)|
|US / Central||Wed 23-Oct-2019 14:00 (02:00 PM)|
|US / Eastern||Wed 23-Oct-2019 15:00 (03:00 PM)|
|London||Wed 23-Oct-2019 20:00 (08:00 PM)|
|Amsterdam||Wed 23-Oct-2019 21:00 (09:00 PM)|
|Moscow||Wed 23-Oct-2019 22:00 (10:00 PM)|
|Chennai||Thu 24-Oct-2019 00:30 (12:30 AM)|
|Hangzhou||Thu 24-Oct-2019 03:00 (03:00 AM)|
|Tokyo||Thu 24-Oct-2019 04:00 (04:00 AM)|
|Sydney||Thu 24-Oct-2019 06:00 (06:00 AM)|
Or in your local time:
Extracted from modules-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
The agenda comes from issues labelled with
modules-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.
Answer questions reasonablytall
I'll be listening, but I'm not in a location where I can speak.
As an update for #351, there hasn't been notable progress except for nodejs/node#29752 which placed loaders behind their own experimental flag, decoupling them from unflagging esm.
To figure out some next steps, I would like to organize an off-band meeting. The design doc is in a decent state, and at the very least the current loader system should be changed to allow multiple loader composition and disallow in-loader module instantiation, as these present major changes to loader designers.