You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Vitepress (vuejs/vitepress), the page HTML base path (site.base) and the static assets base path (vite config.base, equivalent to publicPath in webpack) are not handled separately. This causes issues when deploying the HTML and CDN separately (with the HTML being served from a dedicated domain and the CDN deployed on a general CDN service). The built pages cannot navigate correctly or the static assets fail to load properly.
The current code handling both site.base and vite.config.base consistently can be found at the following link:
In Vitepress (vuejs/vitepress), the page HTML base path (
site.base
) and the static assets base path (vite config.base
, equivalent topublicPath
in webpack) are not handled separately. This causes issues when deploying the HTML and CDN separately (with the HTML being served from a dedicated domain and the CDN deployed on a general CDN service). The built pages cannot navigate correctly or the static assets fail to load properly.The current code handling both
site.base
andvite.config.base
consistently can be found at the following link:vitepress/src/node/build/bundle.ts
Line 60 in b16340a
It would be beneficial to separate the handling of these two base paths to better support different deployment scenarios.
The text was updated successfully, but these errors were encountered: