{"version":3,"mappings":";q/BAgBA,eAAeA,GAAO,CACpB,QAAQ,MAAM,QAAQ,EAEtB,MAAMC,EAAO,SAAS,cAAc,mBAAmB,EACvD,GAAIA,EAAM,CACR,KAAM,CAAE,UAAAC,CAAA,EAAc,MAAAC,EAAA,0BAAAD,CAAA,OAAM,QAAO,oBAAO,OAAAE,KAAA,qBAAAF,CAAA,+BAC1C,MAAMA,EAAUD,CAAI,CACtB,CACF,CACK,WAAW,mBAId,QAAQ,IAAI,yCAAyC,GAHrD,WAAW,mBAAqB,GAChCD,EAAA,EAAO,KAAK,IAAM,QAAQ,IAAI,eAAe,CAAC","names":["main","node","renderApp","__vitePreload","n"],"ignoreList":[],"sources":["../../../../client/main.tsx"],"sourcesContent":["// Main module. This is the entry point for the client side code.\n\n// 🚨🚨🚨 VERY IMPORTANT 🚨🚨🚨:\n// Don't import anything here. Vite doesn't like to mix dynamic with static imports. It\n// breaks react's hooks completely, when react is imported in both ways. Hence, we\n// dynamically import even the basic app. THIS WILL ONLY MANIFEST IN PRODUCTION BUILDS.\n// If we ever try to change it, don't think that just because it runs in dev it'll run\n// in prod as well (as I did once... :-)).\n\ndeclare global {\n  // For some reason, we're getting loaded multiple times when we use dynamic imports. This\n  // can also lead to weird bootup errors on safari. Let's just guard it here.\n  var gospireInitialized: boolean;\n}\n\n// Main entry for client\nasync function main() {\n  console.debug(\"main()\");\n\n  const node = document.querySelector(\"[data-widget=app]\");\n  if (node) {\n    const { renderApp } = await import(\"./app\");\n    await renderApp(node);\n  }\n}\nif (!globalThis.gospireInitialized) {\n  globalThis.gospireInitialized = true;\n  main().then(() => console.log(\"main(): done.\"));\n} else {\n  console.log(\"main(): already initialized - skipping.\");\n}\n\nexport {};\n"],"file":"assets/main-B6MqNkmv.js"}