Is there some API similar with onAfterConfigResolve or buildStart in vitepress

[shellRaining]

https://github.com/shellRaining/shellRaining-blog/blob/2a2222f579557de8e7065552a79adc57cb29c637/packages/theme/src/node/config.ts#L62-L64

I am building a custom theme for a VitePress blog, and I want users to be able to specify a font when using it, my theme will perform font subsetting during the build process

After the font subsetting operation, a piece of CSS code for font-face is generated. I wish to insert it into the final built HTML, but the buildEnd hook function is too late, and it seems below code not work

  siteConfig.site.head.push(["style", {}, `...`]);

I check the code of vitepress and found the onAfterConfigResolve hook in the node/cli/ts, but it seems to be used internally by vitepress and I cannot invoke it. Therefore, I would like to ask if there are other methods to address this issue.

[brc-dd]

You can do that with vite plugin:

// .vitepress/config.ts

import { defineConfig, type SiteConfig } from 'vitepress'

export default defineConfig({
  vite: [
    {
      name: 'foo',
      configResolved(config) {
        const siteConfig = ((config as any).vitepress as SiteConfig)
        // do stuff
      }
    }
  ]
})

[brc-dd]

try skipping on ssr - if (config.build.ssr) return, client bundle is compiled first and siteConfig isn't reloaded so it should work fine for both 👀

[shellRaining]

With this piece of code, he indeed only called the function once! However, a new issue arose: since I wrote the subsetted font to .viteress/dist/fonts/xxx.woff2, it was overwritten during the subsequent build process.

Kapture.2025-03-03.at.17.15.14.mp4

I have an idea that first save the subsetted fonts to the /tmp directory (or some other location), and then move them back in buildEnd, but this approach seems a bit unreliable. Are there any other solutions?

[brc-dd]

How are you emitting it?

    buildStart() {
      if (this.environment.name !== 'client') return
      const siteConfig: SiteConfig = (this.environment.config as any).vitepress

      // subset it and add to siteConfig...

      this.emitFile({
        type: 'asset',
        source: 'foo', // use fs to read if subsetting is not in-memory
        fileName: 'foo.woff2'
      })
    }

https://rollupjs.org/plugin-development/#this-emitfile

ah on vite 5, this.environment won't be there, store config to some variable in configResolved hook and use it instead at start

[shellRaining]

now work properly! Thanks a lot for your help.

By the way, if there are other channels through which I could sponsor? Mainland bank cards can't be used on GitHub 😭

[brc-dd]

Ah, no need. There might be some ways but last I checked the transaction fees were too high on most platforms. Anyway, happy to help.