Geoffrey Booth

> I proposed 2 ad-hoc solutions here: loader:cache-key resolution specifier, and sourceURLs array on the result of resolve and load. Could we create a cache based on the resolved URL...

> Ideally you wouldn't need to call nextLoad at all if you don't want to. That's fine. I guess what this illuminates though is that there can be varying goals...

I have a conflict for the first half-hour, can we start 30 minutes late?

@joyeecheung We’d love to see you too if you can attend, at UTC Tue 09-Apr-2024 18:30.

> 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.

One thing to consider is that the point of the communications port isn’t just to pass data at initialization time. There are plenty of use cases where loaders need to...

> PS It looks like a duplicate PR attempting to do the same thing was started whilst I was away. I haven't had a chance yet to look at it....

> This change exists in its own commit in order to be able to be reviewed separately. Thank you so much! Do you mind opening this as its own PR?...

> I’m not sure how I can put the PR on node’s repo So your first PR is based on your `support-nested-loader-chains` branch. I suggest that you: 1. Branch off...

> Note, however, that I opted to add an additional specific `transferList` parameter instead of attempting to automatically deeply inspect the sent data, so the signature for `register` is now:...