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

2023-09-07 Meeting #55

Open
jasnell opened this issue Sep 7, 2023 · 1 comment
Open

2023-09-07 Meeting #55

jasnell opened this issue Sep 7, 2023 · 1 comment

Comments

@jasnell
Copy link
Contributor

jasnell commented Sep 7, 2023

Agenda:

  • Socket API Update
  • import.meta.resolve, import.meta.url, import.meta.main status
    • 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.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
@jasnell
Copy link
Contributor Author

jasnell commented Sep 7, 2023

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

1 participant