fix: load vite config in sequence rather than in parallel

histoire-dev · Feb 17, 2023 · 2a9cda8 · 2a9cda8
1 parent 50bfd61
commit 2a9cda8
Showing 1 changed file with 4 additions and 11 deletions.
diff --git a/packages/histoire/src/node/server.ts b/packages/histoire/src/node/server.ts
@@ -33,17 +33,10 @@ export async function createServer (ctx: Context, options: CreateServerOptions =
     }
   }
 
-  const [
-    { server, viteConfigFile },
-    { server: nodeServer },
-    ,
-    { stop: stopMdFileWatcher },
-  ] = await Promise.all([
-    getViteServer(false),
-    getViteServer(true),
-    watchStories(ctx),
-    createMarkdownFilesWatcher(ctx),
-  ] as const)
+  const { server, viteConfigFile } = await getViteServer(false)
+  const { server: nodeServer } = await getViteServer(true) // Should be run after the first one to get a fresh vite.config.js
+  await watchStories(ctx)
+  const { stop: stopMdFileWatcher } = await createMarkdownFilesWatcher(ctx)
 
   const moduleLoader = useModuleLoader({
     server: nodeServer,