The base option of VuePress assumes that the user's website will always have the same public path with router base. but it's very likely that we need to set them separately. For example, you'd deploy HTML and assets on different servers.
See also:
yarn add -D vuepress-plugin-dynamic-base # OR npm install -D vuepress-plugin-dynamic-base
// .vuepress/config.js module.exports = { plugins: [ [ 'dynamic-base', { publicPath: 'your/custom/public/path', routeBash: 'your/custom/router/base', } ] ] }
// .vuepress/config.js module.exports = { plugins: [ [ 'dynamic-base', { publicPath: process.env.NETLIFY_CI ? null : 'your/custom/public/path', routeBash: { 'hostA': '/', 'hostB': '/blog/', } } ] ] }
It means that the publc path will be different acccording to the NEV you set, and the router base will be '/'
when the host is hostA
, and '/blog/'
when the host is hostB
.
string
string | { [host: string]: string }
git checkout -b my-new-feature
git commit -am 'Add some feature'
git push origin my-new-feature
vuepress-plugin-dynamic-base © ULIVZ, Released under the MIT License.
github.com/ulivz · Twitter @_ulivz
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4