Node.js Loaders Team Meeting 2024-04-09 #191
Comments
|
Based on the input I heard during the collab summit from last week that the @nodejs/loaders team is looking for more collaborators and support in implementing some of the open tasks, considering also that I am interested in any contributions that might bring node.js esm implementation/modules to a state that is APM friendlier I would like to participate to the ongoing discussion around #52219 and see if there is something I can do to support the efforts. |
|
Hiya @dygabo we would love some help! The issue you cited maaay be a very large first-bite though. Do you have any particular areas of expertise? If so, I can maybe point you to an open issue; you're welcome to try at the one you cited, but I worry you may spin your wheels. I'm returning from a hiatus, so I may be able to support; I was hoping to jump back onto nodejs/node#50752 (and maybe some cleanup). |
|
Hi @JakobJingleheimer and thanks for the reply, I work in observability domain, being part of a team working on a node.js apm solution. I have some previous contributions to node.js loaders area about two years ago, concerning returning the module type from the resolve hook instead of during load. I for sure still would need to read into the open issues and also into the challenges that you have currently on your agenda and I think I could participate in the discussions, maybe also some code changes. I'm sure that having a working solution on #52219 is not an easy task and I did not want to imply that I would solve that on my own, without collaboration with the rest of the team. More like the other way around, it would make sense IMO that the team continues to work on it and maybe I could help with some input, ideas, reviews, tests, etc. I could jump in one of the group meetings (e.g. this one today) and we could discuss it more and maybe take it from there. What do you think? |
|
Oh sure! Do join this evening's meeting if it happens 🙂 |
|
I have a conflict for the first half-hour, can we start 30 minutes late? |
|
I can do |
|
@joyeecheung We’d love to see you too if you can attend, at UTC Tue 09-Apr-2024 18:30. |
|
I'd like to attend to at least listen in, but my team always has its "planning" and "grooming" meetings at this time. |
|
Should we reschedule this occurrence for a different day? (Any later is too late for me) |
|
I doubt it's worth rescheduling on my account, but my only viable day would be Friday. |
|
Looks like I can pop in for the first 30 minutes today. |
FYI we’ll start at UTC Tue 09-Apr-2024 18:30 (06:30 PM) today. I just updated the top post. |
|
Then maybe next time. |
|
I think I can attend the first 30 minutes but will need to go after that or I will have no bed to sleep on... |
|
(Or maybe I can rejoin after leaving for ~15 minutes, not too sure) |
Time
UTC Tue 09-Apr-2024 18:30 (06:30 PM):
Links
Agenda
Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
loaders-agendaacross 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
The text was updated successfully, but these errors were encountered: