2023-06-01 Meeting Notes

[jasnell]

Attendees:

• Ethan Arrowood
• James Snell
• Luca Casonato
• Guy Bedford
• Pooya Parsa
• Andreu

Agenda:

• Updates on Socket API
• Update on runtime keys
• Response.json implemented in Firefox
• AsyncContext updates, details, implementation all being worked through.
• Breakout Session at the workshop next tuesday
• Do we want to add WebAssembly APIs to minimum? Believe so yes.
• Guy: Do we need to deal with script vs. modules. import.meta space? import.meta.url, import.meta.resolve
  • James: import.meta is a bit of a minefield... wintercg probably should address this.
  • Luca: there are a number that are not-contentious (e.g. import.meta.url, import.meta.resolve?)
  • import.meta.main? Contentious in node.js because "what is main" ... can we learn lessons from deno's impl
  • import.meta.test?
  • import.meta.hot? -- hot reloading... vite using this one
  • import.meta.glob? -- glob imports... vite also
  • import.meta.env? -- https://vitejs.dev/guide/env-and-mode.html
• Related to import.meta.glob .. in vite, almost like a runtime macro that expands the glob into multiple runtime imports.
  • This would be for the bundler... we should cover this
  • Essentially bundler macros

Action Item:

• Raise the discussion about formal support of wintercg by Node.js (@jasnell)
• Sockets spec w/ list of testable assertions (@jasnell)
• Add WebAssembly JavaScript API to the Minimum common API (@andreubotella)
• performance.now/timeOrigin PR needs review Add performance.now/timeOrigin proposal-minimum-common-api#40
• Add import.meta.url and import.meta.resolve to the Minimum common API
• Write up draft for pattern-matching dynamic imports for bundlers (@lucacasonato)

[andreubotella]

• Breakout Session at the workshop next tuesday

For the record, the agenda and the details on time and link to join are at Igalia/webengineshackfest#14

[jcbhmr]

Hello! 👋 Sorry if this is offtopic. I was Googling for "specification"-like documents related to import.meta.main. I found this GitHub issue. I'm looking for a webpage place/document kinda like how https://html.spec.whatwg.org/multipage/webappapis.html#hostgetimportmetaproperties defines import.meta.url and import.meta.resolve for the HTML environment which is then implemented in Node.js, Deno, Bun, browsers, etc. Is there such a document for import.meta.main? Does Deno define it? Or does Bun? Do they share a definition that they both implement? How does that work? How would I say "conforms to {import.meta.main spec name here}"? Would I say "conforms to Deno's import.meta.main implementation"?

Best guesses:
https://deno.land/[email protected]/runtime/import_meta_api
https://bun.sh/docs/api/import-meta
https://tc39.es/proposal-import-meta/
https://nodejs.org/api/esm.html#importmeta
https://html.spec.whatwg.org/multipage/webappapis.html#hostgetimportmetaproperties

DENO import.meta.main: returns whether the current module is the entry point to your program.

BUN import.meta.main | boolean Indicates whether the current file is the entrypoint to the current bun process. Is the file being directly executed by bun run or is it being imported?

Sorry if this is the wrong place to ask about this 😬