-
Notifications
You must be signed in to change notification settings - Fork 4
Closed
Labels
meetingAn issue announcing a meeting.An issue announcing a meeting.
Description
Agenda:
- Socket API Update
- Reorganize Spec for consistency and clarity proposal-sockets-api#8
- Ethan will land existing reorg pr
- James will be opening a couple PRs for a few edits
- Move ref impl repo into wintercg
import.meta.resolve,import.meta.url,import.meta.mainstatus- https://github.com/wintercg/proposal-common-minimum-api/pull/49/files
- Node.js still has issues with
main. Lack of understanding what main means? - e.g. Is it still main if it's in a worker thread?
- Need clarity on what the entrypoint module is
- entry.js import foo, foo imports entry.js, does main change in entry.js, etc
- import.meta.resolve should work for files that do not exist, should resolve a directory, trailing slash resolution?
- We will add these to the import.meta registry (see below)
- Discussion for each of these will be separated so that they can move forward independently
- Node.js import.meta proposal
- import.meta path helpers proposal proposal-minimum-common-api#54
- Set up a registry of reserved import.meta keys rather than "standard" spec. Runtimes can implement if they want, if they do, conform to the registry.
- Idea here is that the registry would serve a similar purpose as iana registries, reserving
import.metakey names with links to specs for them, but leaving it up to runtimes to decide what they want to implement. This helps avoid the conflict but gives runtimes room to do what they need.
- PR from fastly runtime key (and other ones)
- Going to get these landed
- AsyncContext update
- Working through task attribution issues in chrome
- Task attribution for
EventandEventTargetis an open question - MessagePort, task attribution when message is enqueued?
- Work ongoing in Node.js to refactor AsyncLocalStorage to align closer with AsyncContext
- Work ongoing in Node.js to align unhandledrejection context propagation with spec
- James has opened a conversation around adding trailing header and interim responses to the fetch api
- Not controversial from a server runtime point of view but would browsers accept it?
- What is the right compromise between server and browsers?
Attendees:
- James Snell
- Geoffrey Booth
- Ethan Arrowood
- Guy Bedford
- Andreu Botella
- Pooya
Metadata
Metadata
Assignees
Labels
meetingAn issue announcing a meeting.An issue announcing a meeting.