2024-11-21 Standardization meeting

[andreubotella]

Agenda:

• Scope and working mode finalized. Next steps?
• Update website to reflect the new scope www#46
• Dealing with proposals and other items that might not be part of TC55 (fetch, web crypto streams, runtime keys...)

[andreubotella]

• runtime keys
  • move to openjsf / lf package.json effort
  • we are not related to this anymore - there is nothing helpful we can do
  • we can encourage wintertc participants to go there and add a key
• navigator registry
  • move into minimum common api the explicitly encouraged and explicitly discouraged apis
  • other navigator keys like hardwareConcurrency and languages go into other conformance levels
• import.meta
  • import.meta.url and import.meta.resolve go into minimum common api
  • import.meta.main tbd, maybe a different conformance level, maybe in minimum common
  • import.meta.dirname and import.meta.filename part of fs conformance levl
  • import.meta.env goes into cli apis
  • import.meta.hot is something for tc39 module harmony to look at
• function api
  • break into two parts: http server using fetch, and export default entrypoints
  • http server using fetch can be layered on fetch itself, open questions around how to expose data that is not visible thru fetch api (like remote IP address and port). also talk to framework authors about this
  • export default entrypoints is a separate spec, this needs feedback from framework authors and runtimes
  • we need a champion for "http server using fetch"