2023-1-26 Meeting

[jasnell]

• Updates on current initiatives
  • fetch spec
  • runtime keys
  • common minimum api
• Couple of small whatwg spec changes to highlight
  • URLSearchParams size getter https://github.com/whatwg/url/pull/734
  • URLSearchParams has() and delete() value argument https://github.com/whatwg/url/pull/735
  • fetch set-cookie handling in Headers https://github.com/whatwg/fetch/pull/1346 (Andreu)
• Standardize JavaScript Functions API next steps
  • https://github.com/wintercg/admin/issues/44
• AsyncContext and AsyncLocalStorage
  • We now have multiple platforms implementing Node.js' AsyncLocalStorage (workerd, deno, bun, etc)
  • We should identify a strict subset of the API to focus on interoperability (littledan)
  • AsyncContext is coming, what's the status and roadmap for that? Key issues?

[jasnell]

• Fetch spec
  • Fetch meeting progress made
  • Initial meeting fairly light
  • Need old repo deleted
• Small whatwg spec changes
  • Just making folks aware of the URLSearchParams has/delete and size
  • Luca: concern over what the size getter returns, the other needs more consideration
  • Littledan: has/delete needs to be different methods. Reference tag guidelines. Why risk breaking?
  • James: Should other web apis also have these?
• fetch set-cookie API
  • Andreu: has implementation bugs open, working on webkit implementation
  • Andreu: Chrome is interested if there is consensus. Firefox?
  • James: is the signature going to remain the same? If so I can do a workerd impl this week
  • Andreu: Additional tests and implementation work progressing
  • Andreu: Also looking at ReadableStream.from... still some open issues? Is it settled?
  • Standard JavaScript Function API
  • Ethan: Start standardizing in some way
  • James: We have a survey of what everyone is doing currently. What is the next step?
  • Ethan: Next meeting, perhaps discussing the idea of a standard.
  • James: Can we start with a high level description of the problem and the general requirements?
  • Jean: Can we go the opposite way and have something that can translate...
  • Ethan: Implementers could provide tools to translate
  • Luca: What are we trying to standardize here? Need to clarify what and requirements
  • AsyncContext and AsyncLocalStorage
  • Luca: Why this popped up. Next.js added AsyncLocalStorage as a requirement
    • AsyncLocalStorage is non-standard Node.js API
    • What subset of the API needs to be implemented?
  • Daniel: Do not ship AsyncContext early. If we ship early and people start using it, it'll block shipping the standard. Use something else.
  • What should be in the ALS subset?
    • Documenting the minimal ALS API surface. James can write this.
  • Andreu: For AsyncContext we'll need a list of how it should work with web apis anyway
  • Document covers API surface area. General rules about what APIs should propagate context.
  • Should AsyncLocalStorage be exposed on globalThis? Vercel is doing that. Not a good idea, let's push back against that
  • Chengzhong: is next.js only dependent on the stable api.
  • Luca: looks like run/getStore only
  • Let's push to keep ALS out of globalThis
  • Common minimum api could include a warning again poluting the global scope.
  • James: What about AsyncResource?
  • Littledan: There are discussions about wrap vs an AsyncResource like object
  • Justin: wrap is a bit cumbersome, AsyncResource has a better api for this.
  • Chengzhong: trying to find some minimum viable API.
  • Littledan: Why is Deno thinking of omitting it?
  • Luca: Focusing on specifically what next.js needs
  • James: going to be pushing for some API changes on AsyncResource
  • Littledan: document should have some kind of lower status
  • James: just a markdown document in the repo

[jasnell]

Recording link will take some time to generate. I'll post the link first thing my morning

[ascorbic]

@jasnell was this ever generated?

[lholmquist]

just bumping to ask the same question 😄

[jasnell]

https://us06web.zoom.us/rec/share/wLRPNNhRmOySQ5tABb-IDm41QNYF5bRUbE953RXnMGbTU9R8ewAbcgIVB-f3TOGs.N8uUs2m5PHQQzEjf Passcode: GY!S1Y1N