You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.meta key 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 Event and EventTarget is 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
The text was updated successfully, but these errors were encountered:
Agenda:
import.meta.resolve
,import.meta.url
,import.meta.main
statusmain
. Lack of understanding what main means?import.meta
key 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.Event
andEventTarget
is an open questionAttendees:
The text was updated successfully, but these errors were encountered: