Open jasnell opened 1 year ago
- 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
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/manual@v1.35.0/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 š¬
Attendees:
Agenda:
import.meta.url
,import.meta.resolve
?)import.meta.main
? Contentious in node.js because "what is main" ... can we learn lessons from deno's implimport.meta.test
?import.meta.hot
? -- hot reloading... vite using this oneimport.meta.glob
? -- glob imports... vite alsoimport.meta.env
? -- https://vitejs.dev/guide/env-and-mode.htmlimport.meta.glob
.. in vite, almost like a runtime macro that expands the glob into multiple runtime imports.Action Item:
import.meta.url
andimport.meta.resolve
to the Minimum common API