From 56ba65e1301454df88f9a3856fa1a70dc052d314 Mon Sep 17 00:00:00 2001 From: Divyansh Singh <40380293+brc-dd@users.noreply.github.com> Date: Sun, 22 Jun 2025 17:13:38 +0530 Subject: [PATCH] fix: resolve pages after setting global vitepress config x-ref: #4803 --- src/node/config.ts | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/node/config.ts b/src/node/config.ts index 76269dcb..9cc4dca6 100644 --- a/src/node/config.ts +++ b/src/node/config.ts @@ -128,7 +128,7 @@ export async function resolveConfig( ? userThemeDir : DEFAULT_THEME_PATH - const config: SiteConfig = { + const config: Omit = { root, srcDir, assetsDir, @@ -160,15 +160,17 @@ export async function resolveConfig( transformPageData: userConfig.transformPageData, userConfig, sitemap: userConfig.sitemap, - buildConcurrency: userConfig.buildConcurrency ?? 64, - ...(await resolvePages(srcDir, userConfig, logger, true)) + buildConcurrency: userConfig.buildConcurrency ?? 64 } // to be shared with content loaders // @ts-ignore global.VITEPRESS_CONFIG = config - return config + // resolve pages after setting global, so that path loaders can access it + Object.assign(config, await resolvePages(srcDir, userConfig, logger, true)) + + return config as SiteConfig } const supportedConfigExtensions = ['js', 'ts', 'mjs', 'mts']