Skip to content
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

Node.js Loaders Team Meeting 2024-05-07 #194

Closed
mhdawson opened this issue May 3, 2024 · 3 comments
Closed

Node.js Loaders Team Meeting 2024-05-07 #194

mhdawson opened this issue May 3, 2024 · 3 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented May 3, 2024

Time

UTC Tue 07-May-2024 18:00 (06:00 PM):

Timezone Date/Time
US / Pacific Tue 07-May-2024 11:00 (11:00 AM)
US / Mountain Tue 07-May-2024 12:00 (12:00 PM)
US / Central Tue 07-May-2024 13:00 (01:00 PM)
US / Eastern Tue 07-May-2024 14:00 (02:00 PM)
EU / Western Tue 07-May-2024 19:00 (07:00 PM)
EU / Central Tue 07-May-2024 20:00 (08:00 PM)
EU / Eastern Tue 07-May-2024 21:00 (09:00 PM)
Moscow Tue 07-May-2024 21:00 (09:00 PM)
Chennai Tue 07-May-2024 23:30 (11:30 PM)
Hangzhou Wed 08-May-2024 02:00 (02:00 AM)
Tokyo Wed 08-May-2024 03:00 (03:00 AM)
Sydney Wed 08-May-2024 04:00 (04:00 AM)

Or in your local time:

Links

Agenda

Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

  • Proposal for a simple, universal module loader hooks API to replace require() monkey-patching #52219
  • ESM Hook deadlocks since 21.2.0 a3e09b3 #50948
  • esm: spawn only one hooks thread #50752

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

@mhdawson mhdawson self-assigned this May 3, 2024
@dygabo
Copy link
Member

dygabo commented May 7, 2024

I would try to attend but I will probably be in a train at the time of the meeting. If I'm already at home, I will try to join. If not, next time maybe better luck with the timeslot.
Short update:

  • #52706 (aka #50752) all known comments adressed, PR is green. as far as I am concerned: author-ready
  • since it seems to be around the same part of the code, I could look into #50948 if that's ok and nobody else already handles it. This would be the same like for 52706 without strong time commitment as it depends on how much time I can put aside to work on it
  • if there's some other open issues that need attention (better from priority point of view), let me know.

@jsumners-nr
Copy link

No one has shown up by 14:10EDT.

@JakobJingleheimer
Copy link
Contributor

Ah sorry it was posted in Slack.

Heads up though: if there are no 👍 on the issue, no-one has RSVD'd.

@JakobJingleheimer JakobJingleheimer closed this as not planned Won't fix, can't repro, duplicate, stale May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants