该插件会监听页面滚动事件。当页面滚动至某个 标题锚点 后，如果存在对应的 标题链接 ，那么该插件会将路由 Hash 更改为该 标题锚点 。
该插件主要用于开发主题，并且已经集成到默认主题中。大部分情况下你不需要直接使用它。
npm i -D @vuepress/plugin-active-header-links@next
+import { activeHeaderLinksPlugin } from '@vuepress/plugin-active-header-links'
+
+export default {
+ plugins: [
+ activeHeaderLinksPlugin({
+ // 配置项
+ }),
+ ],
+}
+类型： string
默认值： 'a.sidebar-item'
详情：
标题链接 的选择器。
如果一个 标题锚点 没有对应的 标题链接 ，那么即使滚动到这个 标题锚点 ，该插件也不会更改路由 Hash 。
类型： number
默认值： 200
详情：
滚动事件监听器的 Debounce 延迟。
类型： number
默认值： 5
详情：
即便直接点击 标题锚点 的链接， scrollTop 也可能不会完全等于 标题锚点 的 offsetTop ，所以我们添加一个 Offset 偏移量来避免这个误差。
This plugin will listen to page scroll event. When the page scrolls to a certain header anchor, this plugin will change the route hash to that header anchor if there is a corresponding header link.
This plugin is mainly used to develop themes, and has been integrated into the default theme. You won't need to use it directly in most cases.
npm i -D @vuepress/plugin-active-header-links@next
+import { activeHeaderLinksPlugin } from '@vuepress/plugin-active-header-links'
+
+export default {
+ plugins: [
+ activeHeaderLinksPlugin({
+ // options
+ }),
+ ],
+}
+Type: string
Default: 'a.sidebar-item'
Details:
Selector of header link.
If a header anchor does not have a corresponding header link, this plugin won't change the route hash to that anchor when scrolling to it.
Type: number
Default: 200
Details:
The delay of the debounced scroll event listener.
Type: number
Default: 5
Details:
Even if you click the link of the header anchor directly, the scrollTop might not be exactly equal to offsetTop of the header anchor, so we add an offset to avoid the error.
npm i -D @vuepress/plugin-append-date@next
+import { appendDatePlugin } from '@vuepress/plugin-append-date'
+
+export default {
+ plugins: [appendDatePlugin()],
+}
+string"date""date" | "time" | "full""date"npm i -D @vuepress/plugin-append-date@next
+import { appendDatePlugin } from '@vuepress/plugin-append-date'
+
+export default {
+ plugins: [appendDatePlugin()],
+}
+Type: string
Default: "date"
Details:
Frontmatter key to use when appending date.
Type: "date" | "time" | "full"
Default: "date"
Details:
Format of the date value when appending date.
该插件会给你的站点添加一个 返回顶部 按钮。当页面向下滚动时，该按钮会显示在页面的右下角，点击它就会滚动到页面顶部。
该插件已经集成到默认主题中。
npm i -D @vuepress/plugin-back-to-top@next
+import { backToTopPlugin } from '@vuepress/plugin-back-to-top'
+
+export default {
+ plugins: [backToTopPlugin()],
+}
+数字100布尔值true你可以通过 CSS 变量来自定义 返回顶部 按钮的样式：
:root {
+ --back-to-top-z-index: 5;
+ --back-to-top-icon: url("back-to-top.svg");
+ --back-to-top-bg-color: #fff;
+ --back-to-top-color: #3eaf7c;
+ --back-to-top-color-hover: #71cda3;
+ --back-to-top-shadow: rgb(0 0 0 / 20%);
+}
+This plugin will add a back to top button to your site. The button will be displayed in the bottom right corner of the page when scrolling down. By clicking the button, the page will scroll to the top.
This plugin has been integrated into the default theme.
npm i -D @vuepress/plugin-back-to-top@next
+import { backToTopPlugin } from '@vuepress/plugin-back-to-top'
+
+export default {
+ plugins: [backToTopPlugin()],
+}
+number100booleantrueYou can customize the style of the back to top button via CSS variables:
:root {
+ --back-to-top-z-index: 5;
+ --back-to-top-icon: url("back-to-top.svg");
+ --back-to-top-bg-color: #fff;
+ --back-to-top-color: #3eaf7c;
+ --back-to-top-color-hover: #71cda3;
+ --back-to-top-shadow: rgb(0 0 0 / 20%);
+}
+npm i -D @vuepress/plugin-baidu-analytics@next
+import { baiduAnalyticsPlugin } from '@vuepress/plugin-baidu-analytics'
+
+export default {
+ plugins: [
+ baiduAnalyticsPlugin({
+ // 配置项
+ }),
+ ],
+}
+插件会在访问和切换页面时自动上报页面浏览事件。
`,5),g=e("code",null,"hmt",-1),D=e("code",null,"window",-1),b={href:"https://tongji.baidu.com/holmes/Analytics/%E6%8A%80%E6%9C%AF%E6%8E%A5%E5%85%A5%E6%8C%87%E5%8D%97/JS%20API/JS%20API%20%E4%BD%BF%E7%94%A8%E6%89%8B%E5%86%8C",target:"_blank",rel:"noopener noreferrer"},f=e("h2",{id:"选项",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#选项"},[e("span",null,"选项")])],-1),C=e("h3",{id:"id",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#id"},[e("span",null,"id")])],-1),E=e("ul",null,[e("li",null,[s("类型： "),e("code",null,"string")]),e("li",null,[s("详情： 百度统计的 ID ，即 "),e("code",null,"hm.js"),s(" URL 中的查询参数。")])],-1);function k(x,v){const l=n("NpmBadge"),t=n("ExternalLinkIcon");return i(),c("div",null,[d,a(l,{package:"@vuepress/plugin-baidu-analytics"}),e("p",null,[s("将 "),e("a",h,[s("百度统计"),a(t)]),s(" 集成到 VuePress 中。")]),e("div",u,[m,e("p",null,[s("请勿打开"),e("a",y,[s("百度统计内置的“单页应用数据统计”功能"),a(t)]),s("，本插件会正确处理相关逻辑。")])]),_,e("p",null,[s("另外，一个全局的 "),g,s(" 数组会被挂载到 "),D,s(" 对象上，你可以使用它进行 "),e("a",b,[s("自定义事件的上报"),a(t)]),s(" 。")]),f,C,E])}const j=o(r,[["render",k],["__file","baidu-analytics.html.vue"]]),N=JSON.parse('{"path":"/zh/plugins/baidu-analytics.html","title":"baidu-analytics","lang":"zh-CN","frontmatter":{"description":"baidu-analytics","head":[["link",{"rel":"alternate","hreflang":"en-us","href":"https://ecosystem.vuejs.press/ecosystem/plugins/baidu-analytics.html"}],["meta",{"property":"og:url","content":"https://ecosystem.vuejs.press/ecosystem/zh/plugins/baidu-analytics.html"}],["meta",{"property":"og:site_name","content":"VuePress 生态系统"}],["meta",{"property":"og:title","content":"baidu-analytics"}],["meta",{"property":"og:description","content":"baidu-analytics"}],["meta",{"property":"og:type","content":"article"}],["meta",{"property":"og:locale","content":"zh-CN"}],["meta",{"property":"og:locale:alternate","content":"en-US"}],["meta",{"property":"og:updated_time","content":"2024-03-25T07:11:23.000Z"}],["meta",{"property":"article:modified_time","content":"2024-03-25T07:11:23.000Z"}],["script",{"type":"application/ld+json"},"{\\"@context\\":\\"https://schema.org\\",\\"@type\\":\\"Article\\",\\"headline\\":\\"baidu-analytics\\",\\"image\\":[\\"\\"],\\"dateModified\\":\\"2024-03-25T07:11:23.000Z\\",\\"author\\":[]}"],["link",{"rel":"alternate","type":"application/atom+xml","href":"https://ecosystem.vuejs.press/ecosystem/zh/atom.xml","title":"VuePress 生态系统 Atom Feed"}],["link",{"rel":"alternate","type":"application/json","href":"https://ecosystem.vuejs.press/ecosystem/zh/feed.json","title":"VuePress 生态系统 JSON Feed"}],["link",{"rel":"alternate","type":"application/rss+xml","href":"https://ecosystem.vuejs.press/ecosystem/zh/rss.xml","title":"VuePress 生态系统 RSS Feed"}]]},"headers":[{"level":2,"title":"使用方法","slug":"使用方法","link":"#使用方法","children":[{"level":3,"title":"上报事件","slug":"上报事件","link":"#上报事件","children":[]}]},{"level":2,"title":"选项","slug":"选项","link":"#选项","children":[{"level":3,"title":"id","slug":"id","link":"#id","children":[]}]}],"git":{"updatedTime":1711350683000,"contributors":[{"name":"Mr.Hope","email":"mister-hope@outlook.com","commits":2},{"name":"Zihan Hu","email":"hu-zihan@foxmail.com","commits":1}]},"autoDesc":true,"filePathRelative":"zh/plugins/baidu-analytics.md"}');export{j as comp,N as data}; diff --git a/assets/baidu-analytics.html-DZmhUCvX.js b/assets/baidu-analytics.html-DZmhUCvX.js new file mode 100644 index 0000000000..e05787a50c --- /dev/null +++ b/assets/baidu-analytics.html-DZmhUCvX.js @@ -0,0 +1,11 @@ +import{_ as i,r as n,o as p,c as r,a,b as e,d as s,e as l}from"./app-3y2wReKQ.js";const c={},d=e("h1",{id:"baidu-analytics",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#baidu-analytics"},[e("span",null,"baidu-analytics")])],-1),u={href:"https://tongji.baidu.com/",target:"_blank",rel:"noopener noreferrer"},h={class:"custom-container tip"},y=e("p",{class:"custom-container-title"},"TIP",-1),m={href:"https://tongji.baidu.com/web/help/article?id=324&type=0",target:"_blank",rel:"noopener noreferrer"},g=l(`npm i -D @vuepress/plugin-baidu-analytics@next
+import { baiduAnalyticsPlugin } from '@vuepress/plugin-baidu-analytics'
+
+export default {
+ plugins: [
+ baiduAnalyticsPlugin({
+ // options
+ }),
+ ],
+}
+The plugin will automatically report page view events when visiting and switching pages.
`,5),D=e("code",null,"hmt",-1),b=e("code",null,"window",-1),_={href:"https://tongji.baidu.com/holmes/Analytics/%E6%8A%80%E6%9C%AF%E6%8E%A5%E5%85%A5%E6%8C%87%E5%8D%97/JS%20API/JS%20API%20%E4%BD%BF%E7%94%A8%E6%89%8B%E5%86%8C",target:"_blank",rel:"noopener noreferrer"},v=l('Type: string
Details: The ID of Baidu Analytics, which is the query of hm.js URL.
Bundler function is for appending or modifying bundler options in theme and plugins.
All functions should be called in extendsBundlerOptions lifecycle hook.
TIP
We are omitting that in examples. The actual code should be like this:
// import functions you need
+import { addCustomElement } from '@vuepress/helper'
+
+export const yourPlugin = {
+ // ...
+ extendsBundlerOptions: (bundlerOptions, app) => {
+ // add them here
+ addCustomElement(bundlerOptions, app, 'my-custom-element')
+ },
+}
+Get current bundler name.
export const getBundlerName: (app: App) => string
+// @vuepress/bundler-vite
+getBundleName(app) === 'vite' // true
+// @vuepress/bundler-webpack
+getBundleName(app) === 'webpack' // true
+Add a custom element declaration to the current bundler.
/**
+ * Add tags as customElement
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param customElements tags recognized as custom element
+ */
+export const addCustomElement = (
+ bundlerOptions: unknown,
+ app: App,
+ customElement: string[] | string | RegExp
+) => void;
+import { addCustomElement } from '@vuepress/helper'
+
+addCustomElement(bundlerConfig, app, 'my-custom-element')
+addCustomElement(bundlerOptions, app, [
+ 'custom-element1',
+ 'custom-element2',
+ // all tags start with \`math-\`
+ /^math-/,
+])
+Provides contents for specific path in dev server.
export interface DevServerOptions {
+ /**
+ * Path to be responded
+ */
+ path: string;
+ /**
+ * Respond function
+ */
+ response: (request?: IncomingMessage) => Promise<string | Buffer>;
+
+ /**
+ * error msg
+ */
+ errMsg?: string;
+}
+
+/**
+ * Handle specific path when running VuePress Dev Server
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param path Path to be responded
+ * @param response respond function
+ * @param errMsg error msg
+ */
+export const customizeDevServer: (
+ bundlerOptions: unknown,
+ app: App,
+ {
+ errMsg:"The server encountered an error",
+ response: responseHandler,
+ path,
+ }: CustomServerOptions
+) => void;
+import { useCustomDevServer } from '@vuepress/helper'
+
+// handle \`/api/\` path
+useCustomDevServer(bundlerOptions, app, {
+ path: '/api/',
+ response: async () => getData(),
+ errMsg: 'Unexpected api error',
+})
+addViteOptimizeDepsInclude
Add modules to Vite optimizeDeps.include list
TIP
If a package meets one of the following conditions, you should consider adding it here.
import()addViteOptimizeDepsExclude
Add modules to Vite optimizeDeps.exclude list
If a package and its dependencies are all pure ESM packages, you should consider adding it here.
addViteSsrExternal
Add modules to Vite ssr.external list
If a package is a pure ESM package and does not use aliases or define variables, you should consider adding it here.
addViteSsrNoExternal
Add modules to Vite ssr.noExternal list
If an alias or define is used within a package, you must add it here.
/**
+ * Add modules to Vite \`optimizeDeps.include\` list
+ */
+export const addViteOptimizeDepsInclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite \`optimizeDeps.exclude\` list
+ */
+export const addViteOptimizeDepsExclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite \`ssr.external\` list
+ */
+export const addViteSsrExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite \`ssr.noExternal\` list
+ */
+export const addViteSsrNoExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+import {
+ addViteOptimizeDepsInclude,
+ addViteOptimizeDepsExclude,
+ addViteSsrExternal,
+ addViteSsrNoExternal,
+} from '@vuepress/helper'
+
+addViteOptimizeDepsInclude(bundlerOptions, app, ['vue', 'vue-router'])
+addViteOptimizeDepsExclude(bundlerOptions, app, 'packageA')
+addViteSsrNoExternal(bundlerOptions, app, ['vue', 'vue-router'])
+addViteSsrExternal(bundlerOptions, app, 'packageA')
+addViteConfig
A function for you to add vite config
export const addViteConfig: (
+ bundlerOptions: unknown,
+ app: App,
+ config: Record<string, unknown>,
+) => void
+import { addViteConfig } from '@vuepress/helper'
+
+addViteConfig(bundlerOptions, app, {
+ build: {
+ charset: 'utf8',
+ },
+})
+mergeViteConfig
A function for you to merge vite config.
WARNING
Your users may choose to use other bundler so it's pretty bad to declare vite as deps!
export const mergeViteConfig: (
+ defaults: Record<string, any>,
+ overrides: Record<string, any>,
+) => Record<string, any>
+import { mergeViteConfig } from '@vuepress/helper'
+
+config.viteOptions = mergeViteConfig(config.viteOptions, {
+ build: {
+ charset: 'utf8',
+ },
+})
+chainWebpack
Chain webpack config.
export const chainWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ chainWebpack: (
+ config: WebpackChainConfig,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { chainWebpack } from '@vuepress/helper'
+
+chainWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+configWebpack
Config Webpack
export const configWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ configureWebpack: (
+ config: WebpackConfiguration,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { configWebpack } from '@vuepress/helper'
+
+configWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+打包器函数用于在主题和插件中追加或修改打包器选项。
所有函数都应在 extendsBundlerOptions 生命周期挂钩中调用。
提示
我们在示例中省略了它。 实际代码应该是这样的：
// 导入你需要的函数
+import { addCustomElement } from '@vuepress/helper'
+
+export const yourPlugin = {
+ // ...
+ extendsBundlerOptions: (bundlerOptions, app) => {
+ // 在此添加它们
+ addCustomElement(bundlerOptions, app, 'my-custom-element')
+ },
+}
+获取当前打包器的名称。
export const getBundlerName: (app: App) => string
+// @vuepress/bundler-vite
+getBundleName(app) === 'vite' // true
+// @vuepress/bundler-webpack
+getBundleName(app) === 'webpack' // true
+将自定义元素声明添加到当前的打包器。
interface CustomElementCommonOptions {
+ app: App;
+ config: unknown;
+}
+/**
+ * Add tags as customElement
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param customElements tags recognized as custom element
+ */
+export const addCustomElement = (
+ bundlerOptions: unknown,
+ app: App,
+ customElement: string[] | string | RegExp
+) => void;
+import { addCustomElement } from '@vuepress/helper'
+
+addCustomElement(bundlerConfig, app, 'my-custom-element')
+addCustomElement(bundlerOptions, app, [
+ 'custom-element1',
+ 'custom-element2',
+ // all tags start with \`math-\`
+ /^math-/,
+])
+为开发服务器中的特定路径提供内容。
export interface DevServerOptions {
+ /**
+ * Path to be responded
+ */
+ path: string;
+ /**
+ * Respond function
+ */
+ response: (request?: IncomingMessage) => Promise<string | Buffer>;
+
+ /**
+ * error msg
+ */
+ errMsg?: string;
+}
+
+/**
+ * Handle specific path when running VuePress Dev Server
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param path Path to be responded
+ * @param response respond function
+ * @param errMsg error msg
+ */
+export const customizeDevServer: (
+ bundlerOptions: unknown,
+ app: App,
+ {
+ errMsg:"The server encountered an error",
+ response: responseHandler,
+ path,
+ }: CustomServerOptions
+) => void;
+import { useCustomDevServer } from '@vuepress/helper'
+
+// handle \`/api/\` path
+useCustomDevServer(bundlerOptions, app, {
+ path: '/api/',
+ response: async () => getData(),
+ errMsg: 'Unexpected api error',
+})
+addViteOptimizeDepsInclude
向 Vite optimizeDeps.include 列表中添加模块
提示
如果一个包满足下列条件之一，你应该考虑将它添加至此。
import() 动态导入addViteOptimizeDepsExclude
向 Vite optimizeDeps.exclude 列表中添加模块
如果一个包和它的依赖都是纯 ESM 包，你应该考虑将它添加至此。
addViteSsrExternal
向 Vite ssr.external 列表中添加模块
如果一个包是纯 ESM 包，且未使用别名 (alias) 或定义变量 (define)，你应该考虑将它添加至此。
addViteSsrNoExternal
向 Vite ssr.noExternal 列表中添加模块
如果一个包内使用了别名 (alias) 或定义变量 (define)，你必须将它添加至此。
/**
+ * Add modules to Vite \`optimizeDeps.include\` list
+ */
+export const addViteOptimizeDepsInclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite \`optimizeDeps.exclude\` list
+ */
+export const addViteOptimizeDepsExclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite \`ssr.external\` list
+ */
+export const addViteSsrExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite \`ssr.noExternal\` list
+ */
+export const addViteSsrNoExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+import {
+ addViteOptimizeDepsInclude,
+ addViteOptimizeDepsExclude,
+ addViteSsrExternal,
+ addViteSsrNoExternal,
+} from '@vuepress/helper'
+
+addViteOptimizeDepsInclude(bundlerOptions, app, ['vue', 'vue-router'])
+addViteOptimizeDepsExclude(bundlerOptions, app, 'packageA')
+addViteSsrNoExternal(bundlerOptions, app, ['vue', 'vue-router'])
+addViteSsrExternal(bundlerOptions, app, 'packageA')
+addViteConfig
A function for you to add vite config
export const addViteConfig: (
+ bundlerOptions: unknown,
+ app: App,
+ config: Record<string, unknown>,
+) => void
+import { addViteConfig } from '@vuepress/helper'
+
+addViteConfig(bundlerOptions, app, {
+ build: {
+ charset: 'utf8',
+ },
+})
+mergeViteConfig
无需导入 vite 即可合并 vite 配置的功能
export const mergeViteConfig: (
+ defaults: Record<string, any>,
+ overrides: Record<string, any>,
+) => Record<string, any>
+注意
你不应将 vite 作为依赖，因为你的的用户可能选择其他打包器！
import { mergeViteConfig } from "@vuepress/helper";
+
+config.viteOptions mergeViteConfig(config.viteOptions, {
+ build: {
+ charset: "utf8",
+ },
+});
+chainWebpack
链式修改 webpack 配置.
export const chainWebpack: (
+ { app, config }: WebpackCommonOptions,
+ chainWebpack: (
+ config: WebpackChainConfig,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { chainWebpack } from '@vuepress/helper'
+
+chainWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+configWebpack
配置 Webpack
export const configWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ configureWebpack: (
+ config: WebpackConfiguration,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { configWebpack } from '@vuepress/helper'
+
+configWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+此插件可以自动生成目录页面，也提供目录组件。
npm i -D @vuepress/plugin-catalog@next
+import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ plugins: [
+ catalogPlugin({
+ // 你的选项
+ }),
+ ],
+}
+首先，你应该在路由元信息中设置目录信息:
import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ extendsPage: (page) => {
+ // 在 routeMeta 中设置目录信息
+ page.routeMeta = {
+ // 目录标题
+ title: page.title,
+ // ... 其他信息
+ }
+ },
+}
+import { defineCatalogInfoGetter } from '@vuepress/plugin-catalog/client'
+
+defineCatalogInfoGetter((meta) => (meta.title ? { title: meta.title } : null))
+
+export default {}
+目录信息应包含:
title: 目录标题order: 目录顺序 (可选)content: 目录内容组件 (可选)通过 order 排序
插件将按以下方式通过 order 对页面进行排序:
// 从小到大依次排列正数
+order 1 的项目
+order 2 的项目
+...
+order 10 的项目
+...
+// 无 order 的项目
+无 order 的项目
+无 order 的项目
+...
+// 从小到大依次排列负数
+order -10 的项目
+// ...
+order -2 的项目
+order -1 的项目
+booleanfalse类型：(path: string) => Record<string, any>
详情：生成页面的 Frontmatter 获取器。
示例：
import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ plugins: [
+ catalogPlugin({
+ frontmatter: (path) => ({
+ // 你想要的 frontmatter
+ // 你可以自定义标题、作者、时间等
+ }),
+ }),
+ ],
+}
+类型：(RegExp | string)[]
默认值：[]
详情：
生成中需要排除的目录页路径。
"/foo/" 意味着仅排除 /foo/ 文件夹的目录页生成。/^\\/foo\\// 意味着排除 /foo/ 文件夹及其子文件夹的目录页生成。404 页面会被自动排除。
string类型：CatalogPluginLocaleConfig
interface CatalogPluginLocaleData {
+ /**
+ * 目录标题
+ */
+ title: string
+
+ /**
+ * 空目录提示
+ */
+ empty: string
+}
+
+interface CatalogPluginLocaleConfig {
+ [localePath: string]: CatalogPluginLocaleData
+}
+必填: 否
详情：目录组件国际化配置。
interface CatalogInfo {
+ /** 目录标题 */
+ title: string
+ /** 目录顺序 */
+ order?: number
+ /** 目录内容 */
+ content?: Component
+}
+
+type CatalogInfoGetter = (meta: Record<string, unknown>) => CatalogInfo | null
+
+const defineCatalogInfoGetter: (options: CatalogInfoGetter) => void
+自定义如何从 meta 中提取目录信息。
详情：
该插件默认会全局注册一个 <Catalog /> 组件（除非你设置了 component 选项）。
你可以在主题布局中或直接在 Markdown 文件中使用 <Catalog />。
组件支持四个属性：
level：更改显示层次深度（最大仅支持 3 层），默认为 3。base：显示指定文件夹的目录，默认显示当前文件夹目录。index：为目录项添加索引号，默认无标号。hideHeading：隐藏组件标题，默认会显示 目录 标题。你可以通过 CSS 变量来自定义目录样式：
:root {
+ --catalog-bg-color: #fff;
+ --catalog-bg-secondary-color: #f8f8f8;
+ --catalog-border-color: #e5e5e5;
+ --catalog-active-color: #3eaf7c;
+ --catalog-hover-color: #71cda3;
+}
+The plugin can automatically generate catalog pages and provide catalog components.
npm i -D @vuepress/plugin-catalog@next
+import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ plugins: [
+ catalogPlugin({
+ // Your options
+ }),
+ ],
+}
+First, you should set catalog info in routeMeta:
import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ extendsPage: (page) => {
+ // set catalog info in routeMeta
+ page.routeMeta = {
+ // catalog title
+ title: page.title,
+ // ... other information
+ }
+ },
+}
+import { defineCatalogInfoGetter } from '@vuepress/plugin-catalog/client'
+
+defineCatalogInfoGetter((meta) => (meta.title ? { title: meta.title } : null))
+
+export default {}
+Catalog info should contains:
title: catalog titleorder: catalog order (optional)content: catalog content component (optional)Sorting with order
The plugin will sort pages by order in the following way:
// order positive numbers from small to large
+Project with order 1
+Project with order 2
+...
+Project with order 10
+...
+// Project without order
+Project without order
+Project without order
+...
+// order negative numbers from small to large
+Project with order -10
+// ...
+Project with order -2
+Project with order -1
+booleanfalseType: (path: string) => Record<string, any>
Required: No
Details: Frontmatter getter for the generated page.
Example:
import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ plugins: [
+ catalogPlugin({
+ frontmatter: (path) => ({
+ // frontmatter you want
+ // you may customize title, author. time, etc.
+ }),
+ }),
+ ],
+}
+Type: (RegExp | string)[]
Default: []
Details:
Catalog page path to be excluded during generation.
"/foo/" means only exclude catalog page generation at /foo/ folder./^\\/foo\\// means exclude catalog page generation at /foo/ folder and its subfolders.404 pages will be automatically excluded.
stringType: CatalogPluginLocaleConfig
interface CatalogPluginLocaleData {
+ /**
+ * Catalog title
+ */
+ title: string
+
+ /**
+ * Empty hint
+ */
+ empty: string
+}
+
+interface CatalogPluginLocaleConfig {
+ [localePath: string]: CatalogPluginLocaleData
+}
+Required: No
Details: Locales config for catalog component.
interface CatalogInfo {
+ /** Catalog title */
+ title: string
+ /** Catalog order */
+ order?: number
+ /** Catalog content */
+ content?: Component
+}
+
+type CatalogInfoGetter = (meta: Record<string, unknown>) => CatalogInfo | null
+
+const defineCatalogInfoGetter: (options: CatalogInfoGetter) => void
+Customize how to extract catalog info from meta.
Details:
The plugin will globally register a <Catalog /> component by default (unless you set the component option).
You can use <Catalog /> in the theme layout or directly in the Markdown file.
The component supports four props:
level: Change the display depth (maximum support 3 levels), default is 3.base: Display catalog of the specified folder, default is the current folder directory.index: Add an index number to the directory item, default is no number.hideHeading: Hide the component title, default is to display the Catalog title.You can customize the style of catalog via CSS variables:
:root {
+ --catalog-bg-color: #fff;
+ --catalog-bg-secondary-color: #f8f8f8;
+ --catalog-border-color: #e5e5e5;
+ --catalog-active-color: #3eaf7c;
+ --catalog-hover-color: #71cda3;
+}
+channel 插件选项用于配置 feed 的频道。
stringSiteConfig.title频道的标题
stringoptions.hostname 和 context.base 生成)频道地址
stringSiteConfig.description频道描述信息
stringsiteConfig.locales['/'].locales"en-US"频道使用的语言
stringauthor.name 生成 Copyright by $author频道版权信息
string (需是合法的 Date ISOString)频道内容的发布时间
string (需是合法的 Date ISOString)频道内容的上次更新时间
number内容有效时间，即获取后保持缓存而不进行新获取的时间
string这是一个会在频道中使用的图片，建议设置正方形图片、尺寸最好不小于 512×512。
string一个代表频道的图标，建议设置正方形图片、尺寸最好不小于 128×128，背景色透明。
FeedAuthor频道的作者。
interface FeedAuthor {
+ /** 作者姓名 */
+ name: string
+ /** 作者电子邮箱 */
+ email?: string
+ /** 作者网站 */
+ url?: string
+ /**
+ * 作者头像地址
+ *
+ * 正方形，最好不小于 128×128，透明背景
+ */
+ avatar?: string
+}
+stringWebsub 的链接。Websub 需要服务器后端，与 VuePress 主旨不符，如无特殊需要忽略即可。
`,39),h={class:"custom-container tip"},d=e("p",{class:"custom-container-title"},"WebSub",-1),u={href:"https://w3c.github.io/websub/#subscription-migration",target:"_blank",rel:"noopener noreferrer"};function g(m,b){const l=s("ExternalLinkIcon");return t(),i("div",null,[p,e("div",h,[d,e("p",null,[n("有关信息，详见 "),e("a",u,[n("Websub"),c(l)]),n("。")])])])}const v=a(r,[["render",g],["__file","channel.html.vue"]]),f=JSON.parse('{"path":"/zh/plugins/feed/channel.html","title":"频道设置","lang":"zh-CN","frontmatter":{"description":"频道设置 channel 插件选项用于配置 feed 的频道。 channel.title 类型：string 默认值：SiteConfig.title 频道的标题 channel.link 类型：string 默认值：部署的网址 (通过 options.hostname 和 context.base 生成) 频道地址 channel.descript...","head":[["link",{"rel":"alternate","hreflang":"en-us","href":"https://ecosystem.vuejs.press/ecosystem/plugins/feed/channel.html"}],["meta",{"property":"og:url","content":"https://ecosystem.vuejs.press/ecosystem/zh/plugins/feed/channel.html"}],["meta",{"property":"og:site_name","content":"VuePress 生态系统"}],["meta",{"property":"og:title","content":"频道设置"}],["meta",{"property":"og:description","content":"频道设置 channel 插件选项用于配置 feed 的频道。 channel.title 类型：string 默认值：SiteConfig.title 频道的标题 channel.link 类型：string 默认值：部署的网址 (通过 options.hostname 和 context.base 生成) 频道地址 channel.descript..."}],["meta",{"property":"og:type","content":"article"}],["meta",{"property":"og:locale","content":"zh-CN"}],["meta",{"property":"og:locale:alternate","content":"en-US"}],["meta",{"property":"og:updated_time","content":"2024-02-01T15:26:40.000Z"}],["meta",{"property":"article:modified_time","content":"2024-02-01T15:26:40.000Z"}],["script",{"type":"application/ld+json"},"{\\"@context\\":\\"https://schema.org\\",\\"@type\\":\\"Article\\",\\"headline\\":\\"频道设置\\",\\"image\\":[\\"\\"],\\"dateModified\\":\\"2024-02-01T15:26:40.000Z\\",\\"author\\":[]}"],["link",{"rel":"alternate","type":"application/atom+xml","href":"https://ecosystem.vuejs.press/ecosystem/zh/atom.xml","title":"VuePress 生态系统 Atom Feed"}],["link",{"rel":"alternate","type":"application/json","href":"https://ecosystem.vuejs.press/ecosystem/zh/feed.json","title":"VuePress 生态系统 JSON Feed"}],["link",{"rel":"alternate","type":"application/rss+xml","href":"https://ecosystem.vuejs.press/ecosystem/zh/rss.xml","title":"VuePress 生态系统 RSS Feed"}]]},"headers":[{"level":2,"title":"channel.title","slug":"channel-title","link":"#channel-title","children":[]},{"level":2,"title":"channel.link","slug":"channel-link","link":"#channel-link","children":[]},{"level":2,"title":"channel.description","slug":"channel-description","link":"#channel-description","children":[]},{"level":2,"title":"channel.language","slug":"channel-language","link":"#channel-language","children":[]},{"level":2,"title":"channel.copyright","slug":"channel-copyright","link":"#channel-copyright","children":[]},{"level":2,"title":"channel.pubDate","slug":"channel-pubdate","link":"#channel-pubdate","children":[]},{"level":2,"title":"channel.lastUpdated","slug":"channel-lastupdated","link":"#channel-lastupdated","children":[]},{"level":2,"title":"channel.ttl","slug":"channel-ttl","link":"#channel-ttl","children":[]},{"level":2,"title":"channel.image","slug":"channel-image","link":"#channel-image","children":[]},{"level":2,"title":"channel.icon","slug":"channel-icon","link":"#channel-icon","children":[]},{"level":2,"title":"channel.author","slug":"channel-author","link":"#channel-author","children":[]},{"level":2,"title":"channel.hub","slug":"channel-hub","link":"#channel-hub","children":[]}],"git":{"updatedTime":1706801200000,"contributors":[{"name":"Mr.Hope","email":"mister-hope@outlook.com","commits":3}]},"autoDesc":true,"filePathRelative":"zh/plugins/feed/channel.md"}');export{v as comp,f as data}; diff --git a/assets/channel.html-D8F2lbSS.js b/assets/channel.html-D8F2lbSS.js new file mode 100644 index 0000000000..de24c886c8 --- /dev/null +++ b/assets/channel.html-D8F2lbSS.js @@ -0,0 +1,15 @@ +import{_ as t,r as s,o as i,c,b as e,d as n,a as o,e as a}from"./app-3y2wReKQ.js";const r={},h=a('The channel plugin option is used to config the feed channel.
stringSiteConfig.titleChannel title
stringoptions.hostname and context.base)Channel address
stringSiteConfig.descriptionChannel description
Type: string
Default:
siteConfig.locales['/'].lang"en-US"The language of the channel
Type: string
Default:
author.name in channel options, and fall back to Copyright by $authorRecommended to set manually: Yes
Channel copyright information
string (must be a valid Date ISOString)Publish date of the Channel
string (must be a valid Date ISOString)Last update time of channel content
numberThe effective time of the content. It's the time to keep the cache after request without making new requests.
stringA picture presenting the channel. A square picture with a size not smaller than 512×512 is recommended.
stringAn icon representing a channel, a square picture, with not less than 128×128 in size, and transparent background color is recommended.
FeedAuthorThe author of the channel.
',35),p={class:"custom-container details"},d=a(`interface FeedAuthor {
+ /** Author name */
+ name: string
+ /** Author's email */
+ email?: string
+ /** Author's site */
+ url?: string
+ /**
+ * Author's avatar address
+ *
+ * Square, preferably not less than 128×128 with transparent background
+ */
+ avatar?: string
+}
+stringLink to Websub. Websub requires a server backend, which is inconsistent with VuePress, so ignore it if there is no special need.
`,5),u={class:"custom-container tip"},m=e("p",{class:"custom-container-title"},"WebSub",-1),g={href:"https://w3c.github.io/websub/#subscription-migration",target:"_blank",rel:"noopener noreferrer"};function y(f,b){const l=s("ExternalLinkIcon");return i(),c("div",null,[h,e("details",p,[d,e("div",u,[m,e("p",null,[n("For details, see "),e("a",g,[n("Websub"),o(l)]),n(".")])])])])}const D=t(r,[["render",y],["__file","channel.html.vue"]]),k=JSON.parse('{"path":"/plugins/feed/channel.html","title":"Channel Config","lang":"en-US","frontmatter":{"description":"Channel Config The channel plugin option is used to config the feed channel. channel.title Type: string Default: SiteConfig.title Channel title channel.link Type: string Default...","head":[["link",{"rel":"alternate","hreflang":"zh-cn","href":"https://ecosystem.vuejs.press/ecosystem/zh/plugins/feed/channel.html"}],["meta",{"property":"og:url","content":"https://ecosystem.vuejs.press/ecosystem/plugins/feed/channel.html"}],["meta",{"property":"og:site_name","content":"VuePress Ecosystem"}],["meta",{"property":"og:title","content":"Channel Config"}],["meta",{"property":"og:description","content":"Channel Config The channel plugin option is used to config the feed channel. channel.title Type: string Default: SiteConfig.title Channel title channel.link Type: string Default..."}],["meta",{"property":"og:type","content":"article"}],["meta",{"property":"og:locale","content":"en-US"}],["meta",{"property":"og:locale:alternate","content":"zh-CN"}],["meta",{"property":"og:updated_time","content":"2024-02-01T04:46:03.000Z"}],["meta",{"property":"article:modified_time","content":"2024-02-01T04:46:03.000Z"}],["script",{"type":"application/ld+json"},"{\\"@context\\":\\"https://schema.org\\",\\"@type\\":\\"Article\\",\\"headline\\":\\"Channel Config\\",\\"image\\":[\\"\\"],\\"dateModified\\":\\"2024-02-01T04:46:03.000Z\\",\\"author\\":[]}"],["link",{"rel":"alternate","type":"application/atom+xml","href":"https://ecosystem.vuejs.press/ecosystem/atom.xml","title":"VuePress Ecosystem Atom Feed"}],["link",{"rel":"alternate","type":"application/json","href":"https://ecosystem.vuejs.press/ecosystem/feed.json","title":"VuePress Ecosystem JSON Feed"}],["link",{"rel":"alternate","type":"application/rss+xml","href":"https://ecosystem.vuejs.press/ecosystem/rss.xml","title":"VuePress Ecosystem RSS Feed"}]]},"headers":[{"level":2,"title":"channel.title","slug":"channel-title","link":"#channel-title","children":[]},{"level":2,"title":"channel.link","slug":"channel-link","link":"#channel-link","children":[]},{"level":2,"title":"channel.description","slug":"channel-description","link":"#channel-description","children":[]},{"level":2,"title":"channel.language","slug":"channel-language","link":"#channel-language","children":[]},{"level":2,"title":"channel.copyright","slug":"channel-copyright","link":"#channel-copyright","children":[]},{"level":2,"title":"channel.pubDate","slug":"channel-pubdate","link":"#channel-pubdate","children":[]},{"level":2,"title":"channel.lastUpdated","slug":"channel-lastupdated","link":"#channel-lastupdated","children":[]},{"level":2,"title":"channel.ttl","slug":"channel-ttl","link":"#channel-ttl","children":[]},{"level":2,"title":"channel.image","slug":"channel-image","link":"#channel-image","children":[]},{"level":2,"title":"channel.icon","slug":"channel-icon","link":"#channel-icon","children":[]},{"level":2,"title":"channel.author","slug":"channel-author","link":"#channel-author","children":[]}],"git":{"updatedTime":1706762763000,"contributors":[{"name":"Mr.Hope","email":"mister-hope@outlook.com","commits":2}]},"autoDesc":true,"filePathRelative":"plugins/feed/channel.md"}');export{D as comp,k as data}; diff --git a/assets/client.html-BFEBU_em.js b/assets/client.html-BFEBU_em.js new file mode 100644 index 0000000000..80f06aff67 --- /dev/null +++ b/assets/client.html-BFEBU_em.js @@ -0,0 +1,22 @@ +import{_ as s,o as e,c as a,e as l}from"./app-3y2wReKQ.js";const n={},o=l(`Check whether a component is registered globally.
TIP
setup scope, you need to pass the app instance as the second parameter.export const hasGlobalComponent: (name: string, app?: App) => boolean
+// if you globally register \`<my-component>\`
+hasGlobalComponent('MyComponent') // true
+hasGlobalComponent('my-component') // true
+
+hasGlobalComponent('MyComponent2') // false
+Get current locale config from locales settings.
export const useLocaleConfig: <T extends LocaleData>(
+ localesConfig: RequiredLocaleConfig<T>,
+) => ComputedRef<T>
+const localesCOnfig = {
+ '/': 'Title',
+ '/zh/': '标题',
+}
+
+const locale = useLocaleConfig(localesConfig)
+
+// under \`/page\`
+locale.value // 'Title'
+
+// under \`/zh/page\`
+locale.value // '标题'
+检查组件是否已全局注册。
提示
setup 之外调用时，你需要将 app 实例作为第二个参数传递。export const hasGlobalComponent: (name: string, app?: App) => boolean
+// 如果你全局注册了 \`<my-component>\`
+hasGlobalComponent('MyComponent') // true
+hasGlobalComponent('my-component') // true
+
+hasGlobalComponent('MyComponent2') // false
+从语言环境设置中获取当前语言环境配置。
export const useLocaleConfig: <T extends LocaleData>(
+ localesConfig: RequiredLocaleConfig<T>,
+) => ComputedRef<T>
+const localesCOnfig = {
+ '/': 'Title',
+ '/zh/': '标题',
+}
+
+const locale = useLocaleConfig(localesConfig)
+
+// under \`/page\`
+locale.value // 'Title'
+
+// under \`/zh/page\`
+locale.value // '标题'
+Props:
'tip' | 'warning' | 'danger''tip'string'''top' | 'middle' | 'bottom' | undefinedundefined示例：
输入
- VuePress - <Badge type="tip" text="v2" vertical="top" />
+- VuePress - <Badge type="warning" text="v2" vertical="middle" />
+- VuePress - <Badge type="danger" text="v2" vertical="bottom" />
+输出
`,4),b=p(`详情：
CodeGroupItem 组件的 Wrapper 。
Props:
stringtruebooleanfalse详情：
该组件必须放置在 CodeGroup 组件的内部。
可以通过 active Prop 来设置初始激活的元素。如果不设置，默认激活第一个元素。
示例：
输入
<CodeGroup>
+ <CodeGroupItem title="pnpm">
+
+\`\`\`bash:no-line-numbers
+pnpm install
+\`\`\`
+
+ </CodeGroupItem>
+
+ <CodeGroupItem title="yarn">
+
+\`\`\`bash:no-line-numbers
+yarn install
+\`\`\`
+
+ </CodeGroupItem>
+
+ <CodeGroupItem title="npm" active>
+
+\`\`\`bash:no-line-numbers
+npm install
+\`\`\`
+
+ </CodeGroupItem>
+</CodeGroup>
+输出
`,7),_=s("div",{class:"language-bash","data-ext":"sh","data-title":"sh"},[s("pre",{class:"shiki dark-plus",style:{"background-color":"#1E1E1E",color:"#D4D4D4"},tabindex:"0"},[s("code",null,[s("span",{class:"line"},[s("span",{style:{color:"#DCDCAA"}},"pnpm"),s("span",{style:{color:"#CE9178"}}," install")]),e(` +`),s("span",{class:"line"})])])],-1),E=s("div",{class:"language-bash","data-ext":"sh","data-title":"sh"},[s("pre",{class:"shiki dark-plus",style:{"background-color":"#1E1E1E",color:"#D4D4D4"},tabindex:"0"},[s("code",null,[s("span",{class:"line"},[s("span",{style:{color:"#DCDCAA"}},"yarn"),s("span",{style:{color:"#CE9178"}}," install")]),e(` +`),s("span",{class:"line"})])])],-1),k=s("div",{class:"language-bash","data-ext":"sh","data-title":"sh"},[s("pre",{class:"shiki dark-plus",style:{"background-color":"#1E1E1E",color:"#D4D4D4"},tabindex:"0"},[s("code",null,[s("span",{class:"line"},[s("span",{style:{color:"#DCDCAA"}},"npm"),s("span",{style:{color:"#CE9178"}}," install")]),e(` +`),s("span",{class:"line"})])])],-1),f={class:"custom-container warning"},x=s("p",{class:"custom-container-title"},"注意",-1),q=s("p",null,[e("你必须在 "),s("code",null,"Props:
'tip' | 'warning' | 'danger''tip'string'''top' | 'middle' | 'bottom' | undefinedundefinedExample:
Input
- VuePress - <Badge type="tip" text="v2" vertical="top" />
+- VuePress - <Badge type="warning" text="v2" vertical="middle" />
+- VuePress - <Badge type="danger" text="v2" vertical="bottom" />
+Output
`,4),b=p(`Details:
Wrapper of the CodeGroupItem components.
Props:
stringtruebooleanfalseDetails:
This component must be placed inside a CodeGroup component.
Use the active prop to set the initial active item, or the first item will be activated by default.
Example:
Input
<CodeGroup>
+ <CodeGroupItem title="pnpm">
+
+\`\`\`bash:no-line-numbers
+pnpm install
+\`\`\`
+
+ </CodeGroupItem>
+
+ <CodeGroupItem title="yarn">
+
+\`\`\`bash:no-line-numbers
+yarn install
+\`\`\`
+
+ </CodeGroupItem>
+
+ <CodeGroupItem title="npm" active>
+
+\`\`\`bash:no-line-numbers
+npm install
+\`\`\`
+
+ </CodeGroupItem>
+</CodeGroup>
+Output
`,7),_=s("div",{class:"language-bash","data-ext":"sh","data-title":"sh"},[s("pre",{class:"shiki dark-plus",style:{"background-color":"#1E1E1E",color:"#D4D4D4"},tabindex:"0"},[s("code",null,[s("span",{class:"line"},[s("span",{style:{color:"#DCDCAA"}},"pnpm"),s("span",{style:{color:"#CE9178"}}," install")]),e(` +`),s("span",{class:"line"})])])],-1),E=s("div",{class:"language-bash","data-ext":"sh","data-title":"sh"},[s("pre",{class:"shiki dark-plus",style:{"background-color":"#1E1E1E",color:"#D4D4D4"},tabindex:"0"},[s("code",null,[s("span",{class:"line"},[s("span",{style:{color:"#DCDCAA"}},"yarn"),s("span",{style:{color:"#CE9178"}}," install")]),e(` +`),s("span",{class:"line"})])])],-1),f=s("div",{class:"language-bash","data-ext":"sh","data-title":"sh"},[s("pre",{class:"shiki dark-plus",style:{"background-color":"#1E1E1E",color:"#D4D4D4"},tabindex:"0"},[s("code",null,[s("span",{class:"line"},[s("span",{style:{color:"#DCDCAA"}},"npm"),s("span",{style:{color:"#CE9178"}}," install")]),e(` +`),s("span",{class:"line"})])])],-1),k={class:"custom-container warning"},x=s("p",{class:"custom-container-title"},"WARNING",-1),q=s("p",null,[e("You must add an empty line between the starting tag of "),s("code",null,"类型：string
必填：是
详情：
当前网站部署到的域名，插件需要此选项才能工作。
类型：string[]
详情：
需要额外包含的网址。
如果你有一些不包含在 VuePress 路由中的链接 (如: 存放在 public 文件夹下的页面或其他插件或工具直接生成的页面)，你可能需要设置此项。
示例：['/about.html', '/api/']
类型：string[]
默认值：['/404.html']
详情：
不需要收录的页面路径，请以绝对路径开头。
默认情况下 VuePress 自动生成的所有路径 (除 404 页) 都会被添加进 Sitemap。
类型：boolean
默认值：false
详情：
是否在开发服务器中启用
提示
由于性能原因，我们不提供热更新。重启开发服务器以同步你的变更。
类型：string
默认值："http://localhost:${port}"
详情：
开发服务器使用的主机名
类型：string
默认值："sitemap.xml"
详情：
输出的文件名，相对于输出目录。
类型：string
默认值："sitemap.xsl"
详情：
输出的 xsl 文件名，相对于输出目录。
类型：string
默认值："@vuepress-plugin/sitemap/templates/sitemap.xsl"
详情：
用作模板的 XSL 文件内容
类型：number
默认值：0.5
详情：
页面优先级，范围 0 至 1。
类型：(page: Page, app: App) => string
详情：
最后修改事件的获得器，需要返回一个 ISO 字符形式的时间，默认会自动通过 Git 插件生成。
string部署网站的域名。
booleanfalse是否启用 Atom 格式输出。
booleanfalse是否启用 JSON 格式输出。
booleanfalse是否启用 RSS 格式输出。
string一个大的图片，用作 feed 展示。
string一个小的图标，显示在订阅列表中。
number100设置 feed 的最大项目数量。在所有页面排序好后，插件会截取前 count 个项目。
如果你的站点文章很多，你应该考虑设置这个选项以减少 feed 文件大小。
(RegExp | string)[] | (tagName：string) => boolean应在 Feed 中保留的自定义元素或组件。
默认情况下，所有未知标签均会被移除。
类型：(page: Page)=> boolean
默认值：
;({ frontmatter, filePathRelative }: Page): boolean =>
+ !(
+ frontmatter.home ||
+ !filePathRelative ||
+ frontmatter.article === false ||
+ frontmatter.feed === false
+ )
+自定义的过滤函数，用于过滤哪些项目在 feed 中显示。
类型： (pageA: Page, pageB: Page)=> number
默认值：
// dateSorter 来源于 @vuepress/helper
+;(pageA, pageB): number =>
+ dateSorter(
+ pageA.data.git?.createdTime
+ ? new Date(pageA.data.git?.createdTime)
+ : pageA.frontmatter.date,
+ pageB.data.git?.createdTime
+ ? new Date(pageB.data.git?.createdTime)
+ : pageB.frontmatter.date,
+ )
+Feed 项目的排序器。
默认的排序行为是通过 Git 的文件添加日期 (需要 @vuepress/plugin-git)。
提示
你应该启用 @vuepress/plugin-git 来获取最新创建的页面作为 feed 项目。否则，feed 项目将按照 VuePress 中页面的默认顺序排序。
channel 选项用于配置 Feed 频道。
booleanfalse是否在开发服务器中启用
提示
由于性能原因，我们不提供热更新。重启开发服务器以同步你的变更。
string"http://localhost:${port}"开发服务器使用的主机名
string"atom.xml"Atom 格式输出路径，相对于输出路径。
string@vuepress/plugin-feed/templates/atom.xsl 的内容Atom xsl 模板文件没人陪美国
string"atom.xsl"Atom xsl 输出路径，相对于输出路径。
string"feed.json"JSON 格式输出路径，相对于输出路径。
string"rss.xml"RSS 格式输出路径，相对于输出路径。
string@vuepress/plugin-feed/templates/rss.xsl 的内容RSS xsl 模板文件内容。
string"rss.xsl"RSS xsl 输出路径，相对于输出路径。
类型：string
必填：是
详情：
部署域名
类型：Author
type AuthorName = string
+
+interface AuthorInfo {
+ /**
+ * 作者姓名
+ */
+ name: string
+
+ /**
+ * 作者网站
+ */
+ url?: string
+
+ /**
+ * 作者 Email
+ */
+ email?: string
+}
+
+type Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]
+详情：
默认作者
类型：boolean
默认值：true
详情：
是否自动生成描述
类型：string | ((page: Page) => string | null)
详情：
首选链接
类型：string
详情：
当找不到图片时的回退图片链接
类型：string
详情：
内容的年龄分级，格式为 [int]+，如 "13+"
类型：string
详情：
你的 twitter 用户名
类型：(page: Page) => boolean
详情：
你可以使用此选项判断一个页面是否是文章。
类型：
function ogp(
+ /** 插件推断的 OGP 信息 */
+ ogp: SeoContent,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+详情：
自定义 OGP 生成器
你可以使用此选项来注入新的或覆盖掉默认生成的 OGP 标签。
类型：
function jsonLd(
+ /** 由插件推断出的 JSON-LD 对象 */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+详情：
自定义 JSON-LD 生成器
你可以使用此选项来注入新的或覆盖掉默认生成的 JSON-LD 标签。
类型：
function customHead(
+ /** head 标签配置 */
+ head: HeadConfig[],
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+详情：
你可以使用此选项来直接注入任意格式的标签到 <head>。
stringThe domain name of the deployment site.
booleanfalseWhether to output Atom syntax files.
booleanfalseWhether output JSON syntax files.
booleanfalseWhether to output RSS syntax files.
stringA large image/icon of the feed, probably used as banner.
stringA small icon of the feed, probably used as favicon.
number100Set the maximum number of items in the feed. After all pages are sorted, the first count items will be intercepted.
If your site has a lot of articles, you may consider this option to reduce feed file size.
(RegExp | string)[] | (tagName: string) => booleanCustom element or component which should be preserved in feed.
By default, all unknown tags will be removed.
Type: (page: Page)=> boolean
Default:
;({ frontmatter, filePathRelative }: Page): boolean =>
+ !(
+ frontmatter.home ||
+ !filePathRelative ||
+ frontmatter.article === false ||
+ frontmatter.feed === false
+ )
+A custom filter function, used to filter feed items.
Type: (pageA: Page, pageB: Page)=> number
Default:
// dateSorter is from @vuepress/helper
+;(pageA: Page, pageB: Page): number =>
+ dateSorter(
+ pageA.data.git?.createdTime
+ ? new Date(pageA.data.git?.createdTime)
+ : pageA.frontmatter.date,
+ pageB.data.git?.createdTime
+ ? new Date(pageB.data.git?.createdTime)
+ : pageB.frontmatter.date,
+ )
+Custom sorter function for feed items.
The default sorting behavior is by file adding time coming from git (needs @vuepress/plugin-git).
TIP
You should enable @vuepress/plugin-git to get the newest created pages as feed items. Otherwise, the feed items will be sorted by the default order of pages in VuePress.
channel option is used to config Feed Channels.
booleanfalseWhether enabled in devServer.
TIP
For performance reasons, we do not provide hot reload. Reboot your devServer to sync your changes.
string"http://localhost:${port}"Hostname to use in devServer
string"atom.xml"Atom syntax output filename, relative to dest folder.
string@vuepress/plugin-feed/templates/atom.xslAtom xsl template file content.
string"atom.xsl"Atom xsl filename, relative to dest folder.
string"feed.json"JSON syntax output filename, relative to dest folder.
string"rss.xml"RSS syntax output filename, relative to dest folder.
string@vuepress/plugin-feed/templates/rss.xslRSS xsl template file content.
string"rss.xsl"RSS syntax xsl filename, relative to dest folder.
类型：boolean
默认值：false
详情：
是否在 Service Worker 首次成功注册时显示 PWA 安装按钮
类型：ManifestOption
详情：
填充一个将被解析为 manifest.webmanifest 的对象。
提示
如果未设置某些选项，它们会回退到插件预设值。
siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.description || siteConfig.locales['/'].description || "A site built with vuepress"siteConfig.locales['/'].lang || "en-US"context.basecontext.base"standalone""#46bd87""#ffffff""portrait-primary"false类型：string
详情：
favicon.ico 地址，填入绝对路径。
注意
我们建议你为你的站点生成 favicon。
string"#46bd87"booleanfalsebooleanfalse类型：number
默认值：2048
详情：
允许缓存的最大大小 (以 KB 为单位)
注意
此选项具有最高优先级，任何超过此值的文件都会被排除。
所以你如果生成了很大的 HTML 或 JS 文件，请考虑调高此值，否则你的 PWA 可能无法在离线模式下正常运行。
类型：number
默认值：1024
详情：
图片允许缓存的最大大小 (以 KB 为单位)
该选项不能大于 maxSize 选项
类型："disabled" | "available" | "hint" | "force"
默认值："available"
详情：
发现新内容时的控制逻辑。
"disabled": 即使有新的 service worker 也不做任何事情，新的 service work 开始等待后，会在用户下次访问时接管页面，让用户获得新内容。
"available": 仅当新的 service worker 可用时才显示更新弹出窗口
"hint": 显示更新内容可用提示，并允许用户立即刷新。当新的 SW 成功注册后，将转为更新内容就绪弹窗。
当你希望用户立即查看新文档时，这很有帮助。
提示
如果用户在新 SW 就绪前选择刷新，当前的 Service Worker 将被注销，并且请求将开始向 Web 发出。新的 service worker 将开始安装并在安装后接管页面。
"force": 立即注销当前 Service Worker 然后刷新以获取新内容
警告
虽然这可以确保用户访问的是最新内容，但这可能会影响访问体验。
提示
文档的更新方式由以前的版本控制，因此当前选项仅影响此版本的下一次更新。
更高支持苹果的特殊设置，忽略它们是安全的。
string"black" | "white""black"string针对微软磁贴的特殊设置，忽略它们是安全的。
stringstringthemeColorstring"PwaFoundPopup"string"PwaReadyPopup"booleanfalse类型：PwaPluginLocaleConfig
interface PwaPluginLocaleData {
+ /**
+ * 安装按钮文字
+ */
+ install: string
+
+ /**
+ * iOS 安装文字
+ */
+ iOSInstall: string
+
+ /**
+ * 取消按钮文字
+ */
+ cancel: string
+
+ /**
+ * 关闭按钮文字
+ */
+ close: string
+
+ /**
+ * 上一张图片文字
+ */
+ prevImage: string
+
+ /**
+ * 下一张图片文字
+ */
+ nextImage: string
+
+ /**
+ * 安装解释
+ */
+ explain: string
+
+ /**
+ * 描述标签文字
+ */
+ desc: string
+
+ /**
+ * 特性标签文字
+ */
+ feature: string
+
+ /**
+ * 更新内容提示文字
+ */
+ hint: string
+
+ /**
+ * 更新内容可用文字
+ */
+ update: string
+}
+
+interface PwaPluginLocaleConfig {
+ [localePath: string]: PwaPluginLocaleData
+}
+详情：
PWA 插件的国际化配置。
import { usePwaEvent } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+ event.on('ready', (registration) => {
+ console.log('Service worker is active.')
+ })
+ },
+}
+详情：
当发现新内容时强制刷新页面。
示例：
import { forceUpdate } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ forceUpdate()
+ })
+ },
+}
+详情：
手动注册 Service Worker。
参数：
| 参数 | 类型 | 描述 |
|---|---|---|
| serviceWorkerPath | string | Service worker 的路径 |
| hooks | object | Service worker 的钩子 |
| showStatus | boolean | 在控制台输出状态日志 |
interface Hooks {
+ registrationOptions?: RegistrationOptions
+ ready?: (registration: ServiceWorkerRegistration) => void
+ registered?: (registration: ServiceWorkerRegistration) => void
+ cached?: (registration: ServiceWorkerRegistration) => void
+ updated?: (registration: ServiceWorkerRegistration) => void
+ updatefound?: (registration: ServiceWorkerRegistration) => void
+ offline?: () => void
+ error?: (error: Error) => void
+}
+import { registerSW } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ registerSW('/service-worker.js', {
+ ready(registration) {
+ console.log('Service worker is active.')
+ },
+ })
+ })
+ },
+}
+详情：
激活等待中的 Service Worker。
参数：
| 参数 | 类型 | 描述 |
|---|---|---|
| registration | ServiceWorkerRegistration | 想要激活的 Service Worker 的注册 |
import { usePwaEvent, skipWaiting } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+
+ event.on('updated', (registration) => {
+ console.log('The waiting service worker is available.')
+ // activate the waiting service worker
+ skipWaiting(registration)
+ })
+ },
+}
+详情：
手动注销 Service Worker。
示例：
import { unregisterSW } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ unregisterSW()
+ })
+ },
+}
+你可以通过 CSS 变量来自定义样式：
:root {
+ --pwa-z-index: 10;
+ --pwa-color: #2c3e50;
+ --pwa-bg-color: #ffffff;
+ --pwa-border-color: #3eaf7c;
+ --pwa-shadow-color: rgb(0 0 0 / 15%);
+ --pwa-btn-text-color: #ffffff;
+ --pwa-btn-bg-color: #3eaf7c;
+ --pwa-btn-hover-bg-color: #4abf8a;
+ --pwa-content-color: #333;
+ --pwa-content-light-color: #666;
+}
+stringstring"ap-shanghai"你可以直接在插件选项中配置可序列化的选项:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Twikoo',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineTwikooConfig 函数来配置 Twikoo。
import { defineClientConfig } from 'vuepress/client'
+import { defineTwikooConfig } from 'vuepress-plugin-comment2/client'
+
+defineTwikooConfig({
+ // Twikoo 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+类型： string
详情：
部署的域名，例如 https://example.com
该章节内的配置项可以作为一般配置使用，也可以使用在 locales 内。
类型： boolean
默认值： true
详情：
是否启用切换颜色模式的功能。
如果设置为 true ，将会在导航栏展示一个切换颜色模式的按钮。
类型： string
默认值： /
详情：
首页的路径。
它将被用于：
类型： false | (NavbarItem | NavbarGroup | string)[]
默认值： []
详情：
导航栏配置。
设置为 false 可以禁用导航栏。
为了配置导航栏元素，你可以将其设置为 导航栏数组 ，其中的每个元素是 NavbarItem 对象、 NavbarGroup 对象、或者字符串：
NavbarItem 对象应该有一个 text 字段和一个 link 字段，还有一个可选的 activeMatch 字段。NavbarGroup 对象应该有一个 text 字段和一个 children 字段。 children 字段同样是一个 导航栏数组 。NavbarItem 对象，将页面标题作为 text ，将页面路由路径作为 link 。示例 1：
export default {
+ theme: defaultTheme({
+ navbar: [
+ // NavbarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ },
+ // NavbarGroup
+ {
+ text: 'Group',
+ children: ['/group/foo.md', '/group/bar.md'],
+ },
+ // 字符串 - 页面文件路径
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // 嵌套 Group - 最大深度为 2
+ {
+ text: 'Group',
+ children: [
+ {
+ text: 'SubGroup',
+ children: ['/group/sub/foo.md', '/group/sub/bar.md'],
+ },
+ ],
+ },
+ // 控制元素何时被激活
+ {
+ text: 'Group 2',
+ children: [
+ {
+ text: 'Always active',
+ link: '/',
+ // 该元素将一直处于激活状态
+ activeMatch: '/',
+ },
+ {
+ text: 'Active on /foo/',
+ link: '/not-foo/',
+ // 该元素在当前路由路径是 /foo/ 开头时激活
+ // 支持正则表达式
+ activeMatch: '^/foo/',
+ },
+ ],
+ },
+ ],
+ }),
+}
+类型： null | string
详情：
Logo 图片的 URL。
Logo 图片将会显示在导航栏的左端。
设置为 null 可以禁用 Logo 。
示例：
export default {
+ theme: defaultTheme({
+ // Public 文件路径
+ logo: '/images/hero.png',
+ // URL
+ logo: 'https://vuejs.org/images/logo.png',
+ }),
+}
+类型： null | string
详情：
在夜间模式中使用的 Logo 图片的 URL。
如果你想在夜间模式中使用不同的 Logo 图片，就可以使用该配置项。
设置为 null 可以在夜间模式下禁用 Logo 。忽略该配置项将会在夜间模式中使用 logo 配置。
参考：
类型：null | string
详情：
指定 Logo 图片的替代文字。
当未指定时，将默认与站点标题相同。
类型： string
详情：
项目仓库的 URL。
它将被用作 仓库链接 的链接。仓库链接 将会显示为导航栏的最后一个元素。
export default {
+ theme: defaultTheme({
+ // 如果你按照 \`organization/repository\` 的格式设置它
+ // 我们会将它作为一个 GitHub 仓库
+ repo: 'vuejs/vuepress',
+ // 你也可以直接将它设置为一个 URL
+ repo: 'https://gitlab.com/foo/bar',
+ }),
+}
+设置为 false 可以禁用侧边栏。
如果你设置为 'auto'，侧边栏会根据页面标题自动生成。
为了手动配置侧边栏元素，你可以将其设置为 侧边栏数组 ，其中的每个元素是一个 SidebarItem 对象或者一个字符串：
SidebarItem 对象应该有一个 text 字段，有一个可选的 link 字段、一个可选的 children 字段和一个可选的 collapsible 字段。 children 字段同样是一个 侧边栏数组 。 collapsible 字段来控制它是否可折叠。SidebarItem 对象，将页面标题作为 text ，将页面路由路径作为 link ，并根据页面小标题自动生成 children 。如果你想在不同子路径中使用不同的侧边栏，你可以将该配置项设置为 侧边栏对象 ：
"heading" 以自动为相应路径生成基于标题的侧边栏。export default {
+ theme: defaultTheme({
+ // 侧边栏数组
+ // 所有页面会使用相同的侧边栏
+ sidebar: [
+ // SidebarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ children: [
+ // SidebarItem
+ {
+ text: 'github',
+ link: 'https://github.com',
+ children: [],
+ },
+ // 字符串 - 页面文件路径
+ '/foo/bar.md',
+ ],
+ },
+ // 字符串 - 页面文件路径
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // 侧边栏对象
+ // 不同子路径下的页面会使用不同的侧边栏
+ sidebar: {
+ '/guide/': [
+ {
+ text: 'Guide',
+ children: ['/guide/introduction.md', '/guide/getting-started.md'],
+ },
+ ],
+ '/reference/': 'heading',
+ },
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // 可折叠的侧边栏
+ sidebar: {
+ '/reference/': [
+ {
+ text: 'VuePress Reference',
+ collapsible: true,
+ children: ['/reference/cli.md', '/reference/config.md'],
+ },
+ {
+ text: 'Bundlers Reference',
+ collapsible: true,
+ children: [
+ '/reference/bundler/vite.md',
+ '/reference/bundler/webpack.md',
+ ],
+ },
+ ],
+ },
+ }),
+}
+详情：
设置根据页面标题自动生成的侧边栏的最大深度。
0 来禁用所有级别的页面标题。1 来包含 <h2> 标题。2 来包含 <h2> 和 <h3> 标题。类型： string
详情：
编辑此页 链接的 Pattern 。
它将会用于生成 编辑此页 的链接。
如果你不设置该选项，则会根据 docsRepo 配置项来推断 Pattern 。但是如果你的文档仓库没有托管在常用的平台上，比如 GitHub 、 GitLab 、 Bitbucket 、 Gitee 等，那么你必须设置该选项才能使 编辑此页 链接正常工作。
用法：
| Pattern | 描述 |
|---|---|
:repo | 文档仓库 URL ，即 docsRepo |
:branch | 文档仓库分支 ，即 docsBranch |
:path | 页面源文件的路径，即 docsDir 拼接上页面文件的相对路径 |
示例：
export default {
+ theme: defaultTheme({
+ docsRepo: 'https://gitlab.com/owner/name',
+ docsBranch: 'master',
+ docsDir: 'docs',
+ editLinkPattern: ':repo/-/edit/:branch/:path',
+ }),
+}
+则会生成类似于 'https://gitlab.com/owner/name/-/edit/master/docs/path/to/file.md' 的链接。
类型： string
详情：
文档源文件的仓库 URL 。
它将会用于生成 编辑此页 的链接。
如果你不设置该选项，则默认会使用 repo 配置项。但是如果你的文档源文件是在一个不同的仓库内，你就需要设置该配置项了。
类型： string
默认值： 'main'
详情：
文档源文件的仓库分支。
它将会用于生成 编辑此页 的链接。
类型： string
默认值： ''
详情：
文档源文件存放在仓库中的目录名。
它将会用于生成 编辑此页 的链接。
stringType: (string | WalineEmojiInfo)[] | false
type WalineEmojiPresets = \`http://\${string}\` | \`https://\${string}\`
+
+interface WalineEmojiInfo {
+ /**
+ * Emoji name show on tab
+ */
+ name: string
+ /**
+ * Current folder link
+ */
+ folder?: string
+ /**
+ * Common prefix of Emoji icons
+ */
+ prefix?: string
+ /**
+ * Type of Emoji icons, will be regarded as file extension
+ */
+ type?: string
+ /**
+ * Emoji icon show on tab
+ */
+ icon: string
+ /**
+ * Emoji image list
+ */
+ items: string[]
+}
+Default: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
Type: WalineCommentSorting
Default: 'latest'
Details:
Comment list sorting methods.
Optional values: 'latest', 'oldest', 'hottest'
Type: string[]
Default: ['nick','mail','link']
Details:
Reviewer attributes.
Optional values: 'nick', 'mail', 'link'
Type: string[]
Default: []
Details:
Set required fields, optional values:
[]['nick']['nick','mail']Type: string
Default value: 'enable'
Details:
Login mode status, optional values:
'enable': enable login (default)'disable': Login is disabled, users should fill in information to comment'force': Forced login, users must login to commentType: number | [number, number]
Default: 0
Details:
Comment words limit. When a single number is filled in, it 's the maximum number of comment words. No limit when set to 0.
Type: number
Default: 10
Details:
Number of comments per page.
Type: WalineImageUploader | false
type WalineImageUploader = (image: File) => Promise<string>
+Type: WalineHighlighter | false
type WalineHighlighter = (code: string, lang: string) => string
+Type: WalineTexRenderer | false
type WalineTexRenderer = (blockMode: boolean, tex: string) => string
+Type: WalineSearchOptions | false
interface WalineSearchImageData extends Record<string, unknown> {
+ /**
+ * Image link
+ */
+ src: string
+
+ /**
+ * Image title
+ *
+ * @description Used for alt attribute of image
+ */
+ title?: string
+
+ /**
+ * Image preview link
+ *
+ * @description For better loading performance, we will use this thumbnail first in the list
+ *
+ * @default src
+ */
+ preview?: string
+}
+
+type WalineSearchResult = WalineSearchImageData[]
+
+interface WalineSearchOptions {
+ /**
+ * Search action
+ */
+ search: (word: string) => Promise<WalineSearchResult>
+
+ /**
+ * Default result when opening list
+ *
+ * @default () => search('')
+ */
+ default?: () => Promise<WalineSearchResult>
+
+ /**
+ * Fetch more action
+ *
+ * @description It will be triggered when the list scrolls to the bottom. If your search service supports paging, you should set this to achieve infinite scrolling
+ *
+ * @default (word) => search(word)
+ */
+ more?: (word: string, currentCount: number) => Promise<WalineSearchResult>
+}
+Details: Customize search features, you can disable search function by setting it to false.
Type: string
Details:
reCAPTCHA V3 is a captcha service provided by Google. You can add reCAPTCHA V3 site key with recaptchaV3Key to enable it.
You should also set environment variable RECAPTCHA_V3_SECRET for server.
Type: boolean | string[]
Default: false
Details:
Add emoji interaction function to the article, set it to true to provide the default emoji, you can also customize the emoji image by setting the emoji url array, and supports a maximum of 8 emojis.
Type: WalineLocales
interface WalineLocales {
+ [localePath: string]: WalineLocale
+}
+You can directly configure serializable options in the plugin options:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Waline',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineWalineConfig function to customize Waline:
import { defineClientConfig } from 'vuepress/client'
+import { defineWalineConfig } from 'vuepress-plugin-comment2/client'
+
+defineWalineConfig({
+ // Waline config
+})
+
+export default defineClientConfig({
+ // ...
+})
+Type: string
Default: "_blog"
Details:
Key used when injecting info to route meta.
TIP
Setting to an empty key will inject to route meta directly instead of a field.
Type: boolean
Default: Whether using --debug flag
Details:
Whether enable hotReload in devServer.
To theme developers
It's disabled by default because it does have performance impact in sites with a lot of categories and types. And it can slow down hotReload speed when editing Markdown.
If users are adding or organizing your categories or tags, you may tell them to enable this, for the rest it's better to keep it disabled.
Also, you can try to detect number of pages in users project and decide whether to enable it.
Blog category config should be an array, while each item is controlling a "category" rule.
interface BlogCategoryOptions {
+ /**
+ * Unique category name
+ */
+ key: string
+
+ /**
+ * Function getting category from page
+ */
+ getter: (page: Page) => string[]
+
+ /**
+ * A custom function to sort the pages
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * Path pattern of page to be registered
+ *
+ * @description \`:key\` will be replaced by the "slugify" result of the original key
+ *
+ * @default \`/:key/\`
+ */
+ path?: string
+
+ /**
+ * Page layout name
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Frontmatter
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+
+ /**
+ * Item page path pattern or custom function to be registered
+ *
+ * @description When filling in a string, \`:key\` and \`:name\` will be replaced by the "slugify" result of the original key and name
+ *
+ * @default \`/:key/:name/\`
+ */
+ itemPath?: string | ((name: string) => string)
+
+ /**
+ * Item page layout name
+ *
+ * @default 'Layout'
+ */
+ itemLayout?: string
+
+ /**
+ * Items Frontmatter
+ */
+ itemFrontmatter?: (name: string, localePath: string) => Record<string, string>
+}
+Blog type config should be an array, while each item is controlling a "type" rule.
interface BlogTypeOptions {
+ /**
+ * Unique type name
+ */
+ key: string
+
+ /**
+ * A filter function to determine whether a page should be the type
+ */
+ filter: (page: Page) => boolean
+
+ /**
+ * A custom function to sort the pages
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * Page path to be registered
+ *
+ * @default '/:key/'
+ */
+ path?: string
+
+ /**
+ * Layout name
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Frontmatter
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+}
+You can import the following API from @vuepress/plugin-blog/client.
Blog category
const useBlogCategory: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogCategoryData<T>>
+Argument key should be the category unique key.
If no key is passed, the plugin will try to use the key in current path.
Blog category
const useBlogType: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogTypeData<T>>
+Argument key should be the type unique key.
If no key is passed, the plugin will try to use the key in current path.
Returning values are:
interface Article<T extends Record<string, unknown> = Record<string, unknown>> {
+ /** Article path */
+ path: string
+ /** Article info */
+ info: T
+}
+
+interface BlogCategoryData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** Category path */
+ path: string
+
+ /**
+ * Only available when current route matches an item path
+ */
+ currentItems?: Article<T>[]
+
+ /** Category map */
+ map: {
+ /** Unique key under current category */
+ [key: string]: {
+ /** Category path of the key */
+ path: string
+ /** Category items of the key */
+ items: Article<T>[]
+ }
+ }
+}
+
+interface BlogTypeData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** Type path */
+ path: string
+
+ /** Items under current type */
+ items: Article<T>[]
+}
+Type: string
Required: Yes
Details:
Deploy hostname.
Type: Author
type AuthorName = string
+
+interface AuthorInfo {
+ /**
+ * Author name
+ */
+ name: string
+
+ /**
+ * Author website
+ */
+ url?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+}
+
+type Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]
+Required: No
Details:
Default author.
Type: boolean
Default: true
Details:
Whether generate description automatically
Type: string | ((page: Page) => string | null)
Details:
Canonical link
Type: string
Details:
Fallback Image link when no image are found
Type: string
Details:
The age rating of the content, the format is [int]+, such as "13+".
Type: string
Details:
Fill in your twitter username.
Type: (page: Page) => boolean
Details:
Use this option to judge whether the page is an article.
Type:
function ogp(
+ /** OGP info inferred by plugin */
+ ogp: SeoContent,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+Required: No
Details:
Custom OPG Generator.
You can use this options to edit OGP tags.
Type:
function jsonLd(
+ /** JSON-LD Object inferred by plugin */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+Required: No
Details:
Custom JSON-LD Generator.
You can use this options to edit JSON-LD properties.
Type:
function customHead(
+ /** Head tag config */
+ head: HeadConfig[],
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+Required: No
Details:
You can use this options to edit tags injected to <head>.
(name: string) => string(name) => name.replace(/ _/g, '-').replace(/[:?*|\\\\/<>]/g, "").toLowerCase()booleantruestring<!-- more -->类型: string
默认值: "_blog"
详情： 注入文章信息至路由元数据时使用的键名。
提示
设置为空字符串会直接注入路由元数据 (而不是一个键下)。
类型: boolean
默认值: 是否使用 --debug 标记
详情： 是否在开发服务器中启用实时热重载。
致主题开发者
默认情况下它是禁用的，因为它确实会对具有很多分类和类别的站点产生性能影响，并且在编辑 Markdown 时会减慢热重载的速度。
如果用户正在添加或组织类别或标签，你可以告诉他们启用此功能，其余的时间最好禁用它。
此外，你可以尝试检测用户项目中的页面数并决定是否启用它。
博客分类配置应为一个数组，每一项控制一个分类规则。
interface BlogCategoryOptions {
+ /**
+ * 唯一的分类名称
+ */
+ key: string
+
+ /**
+ * 从页面中获取分类的函数
+ */
+ getter: (page: Page) => string[]
+
+ /**
+ * 页面排序器
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * 待注册的页面路径图案
+ *
+ * @description \`:key\` 将会被替换为原 key 的 slugify 结果
+ *
+ * @default \`/:key/\`
+ */
+ path?: string | false
+
+ /**
+ * 页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Front Matter 配置
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+
+ /**
+ * 待注册的项目页面路径图案或自定义函数
+ *
+ * @description 当填入字符串的时候, \`:key\` 和 \`:name\` 会被自动替换为原始的 key、name 的 slugify 结果。
+ *
+ * @default \`/:key/:name/\`
+ */
+ itemPath?: string | ((name: string) => string) | false
+
+ /**
+ * 项目页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ itemLayout?: string
+
+ /**
+ * 项目 Front Matter 配置
+ */
+ itemFrontmatter?: (name: string, localePath: string) => Record<string, string>
+}
+博客类型配置应为一个数组，每一项控制一个类型规则。
interface BlogTypeOptions {
+ /**
+ * 唯一的类型名称
+ */
+ key: string
+
+ /**
+ * 一个过滤函数来决定页面是否满足此类型
+ */
+ filter: (page: Page) => boolean
+
+ /**
+ * 页面排序器
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * 待注册的页面路径
+ *
+ * @default '/:key/'
+ */
+ path?: string | false
+
+ /**
+ * 页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Front Matter 配置
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+}
+你可以从 @vuepress/plugin-blog/client 导入下列 API:
博客分类
const useBlogCategory: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogCategoryData<T>>
+参数 key 为需要获取的键名。如果未传入 key，会尝试使用与当前路径匹配的 key。
博客类型
const useBlogType: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogTypeData<T>>
+参数 key 为需要获取的键名。如果未传入 key，会尝试使用与当前路径匹配的 key。
详细的返回值如下:
interface Article<T extends Record<string, unknown> = Record<string, unknown>> {
+ /** 文章路径 */
+ path: string
+ /** 文章信息 */
+ info: T
+}
+
+interface BlogCategoryData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** 分类路径 */
+ path: string
+
+ /**
+ * 仅当当前路径和某个子项目匹配时可用
+ */
+ currentItems?: Article<T>[]
+
+ /** 分类映射 */
+ map: {
+ /** 当前分类下全局唯一的 key */
+ [key: string]: {
+ /** 对应键值的分类路径 */
+ path: string
+ /** 对应键值的项目 */
+ items: Article<T>[]
+ }
+ }
+}
+
+interface BlogTypeData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** 类别路径 */
+ path: string
+
+ /** 当前类别下的项目 */
+ items: Article<T>[]
+}
+stringbooleantruebooleantruebooleantrue"top" | "bottom""top"类型: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | \`https://\${string}\`
+默认值: "light"
详情：
Giscus 在日间模式下使用的主题
应为一个内置主题关键词或者一个 CSS 链接。
类型: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | \`https://\${string}\`
+默认值: "dark"
详情：
Giscus 在夜间模式下使用的主题
应为一个内置主题关键词或者一个 CSS 链接。
你可以直接在插件选项中配置可序列化的选项:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Giscus',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineGiscusConfig 函数来配置 Giscus。
import { defineClientConfig } from 'vuepress/client'
+import { defineGiscusConfig } from 'vuepress-plugin-comment2/client'
+
+defineGiscusConfig({
+ // Giscus 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+booleanfalseType: AppManifest
Details:
You can fill with an object which will be parsed to manifest.webmanifest.
TIP
Some options have their fallback if you don't set them.
siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.description || siteConfig.locales['/'].description || "A site built with vuepress"siteConfig.locales['/'].lang || "en-US"context.basecontext.base"standalone""#46bd87""#ffffff""portrait-primary"falseType: string
Details:
Link of favicon.ico.
WARNING
We recommend you to set favicon for your site.
Type: string
Default: "#46bd87"
Details:
Theme Color of the pwa.
Type: boolean
Default: false
Details:
Whether cache HTML files besides home page and 404 page.
Type: boolean
Default: false
Details:
Whether cache pictures
Type: number
Default: 2048
Details:
Max size allowed to be cached, with KB unit
WARNING
This option has the highest priority, and any files exceeding this value will be excluded.
So if you generate very large HTML or JS files, please consider increasing this value, otherwise your PWA may not work normally in offline mode.
Type: number
Default: 1024
Details: Max picture size allowed to be cached, with KB unit
The value must not be greater than maxSize option
Type: "disabled" | "available" | "hint" | "force"
Default: "available"
Details: Control logic when new content is found.
"disabled": Do nothing even when new service worker is available. After new service work succeeds installing and starts waiting, it will control page and provide new content in next visit.
"available": Only display update popup when the new service worker is available
"hint": Display a hint to let user choose to refresh immediately
This is helpful when you want users to see new docs immediately.
TIP
If users choose to refresh, the current service worker will be unregister, and request will start coming to web. Later the new service worker will start installing and control current page after installed.
"force": unregister current service worker immediately then refresh to get new content
DANGER
Although this ensures users are viewing the latest content, it may affect viewing experiences.
TIP
How docs are updated is controlled by a previous version, so the current option only effect next update from this version.
Special settings for better supporting Safari, ignoring these options are safe.
string"black" | "white""black"stringSpecial settings for Microsoft tiles, ignoring these options are safe.
stringstringthemeColorstring"PwaFoundPopup"string"PwaReadyPopup"booleanfalseType: PwaPluginLocaleConfig
interface PwaPluginLocaleData {
+ /**
+ * Install button text
+ */
+ install: string
+
+ /**
+ * iOS install hint text
+ */
+ iOSInstall: string
+
+ /**
+ * Cancel button text
+ */
+ cancel: string
+
+ /**
+ * Close button text
+ */
+ close: string
+
+ /**
+ * Previous image text
+ */
+ prevImage: string
+
+ /**
+ * Next image text
+ */
+ nextImage: string
+
+ /**
+ * Install explain text
+ */
+ explain: string
+
+ /**
+ * Description label text
+ */
+ desc: string
+
+ /**
+ * Feature label text
+ */
+ feature: string
+
+ /**
+ * Update hint text
+ */
+ hint: string
+
+ /**
+ * Update available text
+ */
+ update: string
+}
+
+interface PwaPluginLocaleConfig {
+ [localePath: string]: PwaPluginLocaleData
+}
+Details: Locales config for pwa plugin.
import { usePwaEvent } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+ event.on('ready', (registration) => {
+ console.log('Service worker is active.')
+ })
+ },
+}
+Details:
Force update the page when an update is found.
Example:
import { forceUpdate } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ forceUpdate()
+ })
+ },
+}
+Details:
Register service worker manually.
Parameters:
| Parameter | Type | Description |
|---|---|---|
| serviceWorkerPath | string | Path of the service worker |
| hooks | object | Hooks of service worker |
| showStatus | boolean | Log service worker status in console |
interface Hooks {
+ registrationOptions?: RegistrationOptions
+ ready?: (registration: ServiceWorkerRegistration) => void
+ registered?: (registration: ServiceWorkerRegistration) => void
+ cached?: (registration: ServiceWorkerRegistration) => void
+ updated?: (registration: ServiceWorkerRegistration) => void
+ updatefound?: (registration: ServiceWorkerRegistration) => void
+ offline?: () => void
+ error?: (error: Error) => void
+}
+import { registerSW } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ registerSW('/service-worker.js', {
+ ready(registration) {
+ console.log('Service worker is active.')
+ },
+ })
+ })
+ },
+}
+Details:
Activate the waiting service worker.
Parameters:
| Parameter | Type | Description |
|---|---|---|
| registration | ServiceWorkerRegistration | The registration of the service worker you want activate |
import { usePwaEvent, skipWaiting } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+
+ event.on('updated', (registration) => {
+ console.log('The waiting service worker is available.')
+ // activate the waiting service worker
+ skipWaiting(registration)
+ })
+ },
+}
+Details:
Unregister service worker manually.
Example:
import { unregisterSW } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ unregisterSW()
+ })
+ },
+}
+You can customize the style via CSS variables:
:root {
+ --pwa-z-index: 10;
+ --pwa-color: #2c3e50;
+ --pwa-bg-color: #ffffff;
+ --pwa-border-color: #3eaf7c;
+ --pwa-shadow-color: rgb(0 0 0 / 15%);
+ --pwa-btn-text-color: #ffffff;
+ --pwa-btn-bg-color: #3eaf7c;
+ --pwa-btn-hover-bg-color: #4abf8a;
+ --pwa-content-color: #333;
+ --pwa-content-light-color: #666;
+}
+Type: string
Details:
Hostname to be deployed, e.g.: https://example.com
Config of this section can be used as normal config, and can also be used in the locales option.
Type: boolean
Default: true
Details:
Enable color mode switching or not.
If set to true, a button to switch color mode will be displayed in the navbar.
Type: string
Default: /
Details:
Specify the path of the homepage.
This will be used for:
Type: false | (NavbarItem | NavbarGroup | string)[]
Default: []
Details:
Configuration of navbar.
Set to false to disable navbar.
To configure the navbar items, you can set it to a navbar array, each item of which could be a NavbarItem object, a NavbarGroup object, or a string:
NavbarItem object should have a text field and a link field, could have an optional activeMatch field.NavbarGroup object should have a text field and a children field. The children field should be a navbar array, too.NavbarItem object, using the page title as text, and the page route path as link.Example 1:
export default {
+ theme: defaultTheme({
+ navbar: [
+ // NavbarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ },
+ // NavbarGroup
+ {
+ text: 'Group',
+ children: ['/group/foo.md', '/group/bar.md'],
+ },
+ // string - page file path
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // nested group - max depth is 2
+ {
+ text: 'Group',
+ children: [
+ {
+ text: 'SubGroup',
+ children: ['/group/sub/foo.md', '/group/sub/bar.md'],
+ },
+ ],
+ },
+ // control when should the item be active
+ {
+ text: 'Group 2',
+ children: [
+ {
+ text: 'Always active',
+ link: '/',
+ // this item will always be active
+ activeMatch: '/',
+ },
+ {
+ text: 'Active on /foo/',
+ link: '/not-foo/',
+ // this item will be active when current route path starts with /foo/
+ // regular expression is supported
+ activeMatch: '^/foo/',
+ },
+ ],
+ },
+ ],
+ }),
+}
+Type: null | string
Details:
Specify the url of logo image.
The logo image will be displayed at the left end of the navbar.
Set to null to disable logo.
Example:
export default {
+ theme: defaultTheme({
+ // public file path
+ logo: '/hero.png',
+ // url
+ logo: 'https://vuejs.org/images/logo.png',
+ }),
+}
+Type: null | string
Details:
Specify the url of logo image to be used in dark mode.
You can make use of this option if you want to use different logo config in dark mode.
Set to null to disable logo in dark mode. Omit this option to use logo in dark mode.
Also see:
Type: null | string
Details:
Specify the alt text of the logo image.
If not specified, defaults to be the same as the site title.
Type: string
Details:
Specify the repository url of your project.
This will be used as the link of the repository link, which will be displayed as the last item of the navbar.
export default {
+ theme: defaultTheme({
+ // If you set it in the form of \`organization/repository\`
+ // we will take it as a GitHub repo
+ repo: 'vuejs/vuepress',
+ // You can also set it to a URL directly
+ repo: 'https://gitlab.com/foo/bar',
+ }),
+}
+Set to false to disable sidebar.
If you set it to 'auto', the sidebar will be automatically generated from the page headers.
To configure the sidebar items manually, you can set this option to a sidebar array, each item of which could be a SidebarItem object or a string:
SidebarItem object should have a text field, could have an optional link field, an optional children field and an optional collapsible field. The children field should be a sidebar array. The collapsible field controls whether the item is collapsible.SidebarItem object, whose text is the page title, link is the page route path, and children is automatically generated from the page headers.If you want to set different sidebar for different sub paths, you can set this option to a sidebar object:
'heading' to automatically generate the sidebar from the page headers for just the corresponding path.export default {
+ theme: defaultTheme({
+ // sidebar array
+ // all pages will use the same sidebar
+ sidebar: [
+ // SidebarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ children: [
+ // SidebarItem
+ {
+ text: 'github',
+ link: 'https://github.com',
+ children: [],
+ },
+ // string - page file path
+ '/foo/bar.md',
+ ],
+ },
+ // string - page file path
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // sidebar object
+ // pages under different sub paths will use different sidebar
+ sidebar: {
+ '/guide/': [
+ {
+ text: 'Guide',
+ children: ['/guide/introduction.md', '/guide/getting-started.md'],
+ },
+ ],
+ '/reference/': 'heading',
+ },
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // collapsible sidebar
+ sidebar: {
+ '/reference/': [
+ {
+ text: 'VuePress Reference',
+ collapsible: true,
+ children: ['/reference/cli.md', '/reference/config.md'],
+ },
+ {
+ text: 'Bundlers Reference',
+ collapsible: true,
+ children: [
+ '/reference/bundler/vite.md',
+ '/reference/bundler/webpack.md',
+ ],
+ },
+ ],
+ },
+ }),
+}
+Details:
Set the maximum depth of the sidebar children which are automatically generated from the page headers.
0 to disable all levels of headers.1 to include <h2> headers.2 to include <h2> and <h3> headers.Type: string
Details:
Specify the pattern of the edit this page link.
This will be used for generating the edit this page link.
If you don't set this option, the pattern will be inferred from the docsRepo option. But if your documentation repository is not hosted on a common platform, for example, GitHub, GitLab, Bitbucket, Gitee, etc., you have to set this option explicitly to make the edit this page link work.
Usage:
| Pattern | Description |
|---|---|
:repo | The docs repo url, i.e. docsRepo |
:branch | The docs repo branch, i.e. docsBranch |
:path | The path of the page source file, i.e. docsDir joins the relative path of the page file |
Example:
export default {
+ theme: defaultTheme({
+ docsRepo: 'https://gitlab.com/owner/name',
+ docsBranch: 'master',
+ docsDir: 'docs',
+ editLinkPattern: ':repo/-/edit/:branch/:path',
+ }),
+}
+The generated link will look like 'https://gitlab.com/owner/name/-/edit/master/docs/path/to/file.md'.
Type: string
Details:
Specify the repository url of your documentation source files.
This will be used for generating the edit this page link.
If you don't set this option, it will use the repo option by default. But if your documentation source files are in a different repository, you will need to set this option.
Type: string
Default: 'main'
Details:
Specify the repository branch of your documentation source files.
This will be used for generating the edit this page link.
Type: string
Default: ''
Details:
Specify the directory of your documentation source files in the repository.
This will be used for generating the edit this page link.
stringbooleantruebooleantruebooleantrue"top" | "bottom""top"Type: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | \`https://\${string}\`
+Default: "light"
Details:
Giscus theme used in lightmode
Should be a built-in theme keyword or a css link starting with https://.
Type: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | \`https://\${string}\`
+Default: "dark"
Details:
Giscus theme used in darkmode
Should be a built-in theme keyword or a css link starting with https://.
You can directly configure serializable options in the plugin options:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Giscus',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineGiscusConfig function to customize Giscus:
import { defineClientConfig } from 'vuepress/client'
+import { defineGiscusConfig } from 'vuepress-plugin-comment2/client'
+
+defineGiscusConfig({
+ // Giscus config
+})
+
+export default defineClientConfig({
+ // ...
+})
+Type: string
Required: Yes
Details:
The domain name where the current site is deployed, the plugin needs this option to work.
Type: string[]
Details:
Extra link to be included.
If you have some links not including in VuePress Router (normally in public directory or generated by other tools directly), you may need this option.
Example: ['/about.html', '/api/']
Type: string[]
Default: ['/404.html']
Details:
Urls excluding from sitemap, starting with absolute path.
By default, all the urls generated by VuePress (excluding 404 page) will be added into sitemap.
Type: boolean
Default: false
Details:
Whether enabled in devServer.
TIP
For performance reasons, we do not provide hot reload. Reboot your devServer to sync your changes.
Type: string
Default: "http://localhost:${port}"
Details:
Hostname to use in devServer
Type: string
Default value: "sitemap.xml"
Details:
The output filename, relative to output directory.
Type: string
Default value: "sitemap.xsl"
Details:
Output xsl filename, relative to dest folder.
Type: string
Default value: "@vuepress/plugin-sitemap/templates/sitemap.xsl"
Details:
XSL content used as template.
Type: number
Default: 0.5
Details:
Page priority, from 0 to 1.
Type: (page: Page, app: App) => string
Details:
Last modify time getter. By default, the plugin will use the timestamp generated by git plugin.
stringYou can directly configure serializable options in the plugin options:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Twikoo',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineTwikooConfig function to customize Twikoo:
import { defineClientConfig } from 'vuepress/client'
+import { defineTwikooConfig } from 'vuepress-plugin-comment2/client'
+
+defineTwikooConfig({
+ // Twikoo config
+})
+
+export default defineClientConfig({
+ // ...
+})
+el pageTitle, pageKey 和 site 选项为插件的保留选项，将从 VuePress 配置中自动推断，不可设置。
imgUploader 和 avatarURLBuilder 这两个函数选项只能在客户端配置。
你可以直接在插件选项中配置可序列化的选项:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineArtalkConfig 函数来配置 Artalk。
import { defineClientConfig } from 'vuepress/client'
+import { defineArtalkConfig } from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // Artalk 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+The el pageTitle, pageKey and site options are reserved for plugins, they will be inferred from VuePress config.
Two function options imgUploader and avatarURLBuilder can only be set on client side.
You can directly configure serializable options in the plugin options:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineArtalkConfig function to customize Artalk:
import { defineClientConfig } from 'vuepress/client'
+import { defineArtalkConfig } from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // Artalk config
+})
+
+export default defineClientConfig({
+ // ...
+})
+string类型: (WalineEmojiInfo | WalineEmojiPresets)[] | false
type WalineEmojiPresets = \`http://\${string}\` | \`https://\${string}\`
+
+interface WalineEmojiInfo {
+ /**
+ * 选项卡上的 Emoji 名称
+ */
+ name: string
+ /**
+ * 所在文件夹链接
+ */
+ folder?: string
+ /**
+ * Emoji 通用路径前缀
+ */
+ prefix?: string
+ /**
+ * Emoji 图片的类型，会作为文件扩展名使用
+ */
+ type?: string
+ /**
+ * 选项卡显示的 Emoji 图标
+ */
+ icon: string
+ /**
+ * Emoji 图片列表
+ */
+ items: string[]
+}
+默认值: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
类型: WalineCommentSorting
默认值: 'latest'
详情：
评论列表排序方式。可选值: 'latest', 'oldest', 'hottest'
类型: string[]
默认值: ['nick', 'mail', 'link']
详情：
评论者相关属性。可选值: 'nick', 'mail', 'link'
类型: string[]
默认值: []
详情：
设置必填项，默认匿名，可选值:
[]['nick']['nick', 'mail']string'enable'登录模式状态，可选值:
'enable': 启用登录 (默认)'disable': 禁用登录，用户只能填写信息评论'force': 强制登录，用户必须注册并登录才可发布评论类型: number | [number, number]
默认值: 0
详情：
评论字数限制。填入单个数字时为最大字数限制。设置为 0 时无限制。
number10类型: WalineImageUploader | false
详情:
type WalineImageUploader = (image: File) => Promise<string>
+类型: WalineHighlighter | false
type WalineHighlighter = (code: string, lang: string) => string
+类型: WalineTexRenderer | false
type WalineTexRenderer = (blockMode: boolean, tex: string) => string
+类型: WalineSearchOptions | false
interface WalineSearchImageData extends Record<string, unknown> {
+ /**
+ * 图片链接
+ */
+ src: string
+
+ /**
+ * 图片标题
+ *
+ * @description 用于图片的 alt 属性
+ */
+ title?: string
+
+ /**
+ * 图片缩略图
+ *
+ * @description 为了更好的加载性能，我们会优先在列表中使用此缩略图
+ *
+ * @default src
+ */
+ preview?: string
+}
+
+type WalineSearchResult = WalineSearchImageData[]
+
+interface WalineSearchOptions {
+ /**
+ * 搜索操作
+ */
+ search: (word: string) => Promise<WalineSearchResult>
+
+ /**
+ * 打开列表时展示的默认结果
+ *
+ * @default () => search('')
+ */
+ default?: () => Promise<WalineSearchResult>
+
+ /**
+ * 获取更多的操作
+ *
+ * @description 会在列表滚动到底部时触发，如果你的搜索服务支持分页功能，你应该设置此项实现无限滚动
+ *
+ * @default (word) => search(word)
+ */
+ more?: (word: string, currentCount: number) => Promise<WalineSearchResult>
+}
+详情：自定义搜索功能，设置 false 可禁用搜索。
类型: string
详情：
reCAPTCHA V3 是 Google 提供的验证码服务，配置 reCAPTCHA V3 网站密钥即可开启该功能。
服务端需要同步配置 RECAPTCHA_V3_SECRET 环境变量。
类型: boolean | string[]
默认值: false
详情：
为文章增加表情互动功能，设置为 true 提供默认表情，也可以通过设置表情地址数组来自定义表情图片，最大支持 8 个表情。
类型: WalineLocales
interface WalineLocales {
+ [localePath: string]: WalineLocale
+}
+你可以直接在插件选项中配置可序列化的选项:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Waline',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineWalineConfig 函数来配置 Waline。
import { defineClientConfig } from 'vuepress/client'
+import { defineWalineConfig } from 'vuepress-plugin-comment2/client'
+
+defineWalineConfig({
+ // Waline 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+npm i -D @vuepress/plugin-container@next
+import { containerPlugin } from '@vuepress/plugin-container'
+
+export default {
+ plugins: [
+ containerPlugin({
+ // options
+ }),
+ ],
+}
+::: <type> [info]
+[content]
+:::
+type is required and should be specified via type option.info is optional, and the default value can be specified via defaultInfo in locales option.content can be any valid markdown content.TIP
This plugin can be used multiple times to support different types of containers.
Type: Record<string, { defaultInfo: string }>
Details:
The default info of the container in different locales.
If this option is not specified, the default info will fallback to the uppercase of the type option.
Example:
export default {
+ plugins: [
+ containerPlugin({
+ type: 'tip',
+ locales: {
+ '/': {
+ defaultInfo: 'TIP',
+ },
+ '/zh/': {
+ defaultInfo: '提示',
+ },
+ },
+ }),
+ ],
+}
+Type: (info: string) => string
Default:
(info: string): string =>
+ \`<div class="custom-container \${type}">\${info ? \`<p class="custom-container-title">\${info}</p>\` : ''}\\n\`
+Details:
A function to render the starting tag of the container.
The first param is the info part of container syntax.
This option will not take effect if you don't specify the after option.
Type: (info: string) => string
Default:
(): string => '</div>\\n'
+Details:
A function to render the ending tag of the container.
The first param is the info part of container syntax.
This option will not take effect if you don't specify the before option.
type MarkdownItContainerRenderFunction = (
+ tokens: Token[],
+ index: number,
+ options: any,
+ env: MarkdownEnv,
+ self: Renderer,
+) => string
+npm i -D @vuepress/plugin-container@next
+import { containerPlugin } from '@vuepress/plugin-container'
+
+export default {
+ plugins: [
+ containerPlugin({
+ // 配置项
+ }),
+ ],
+}
+::: <type> [info]
+[content]
+:::
+type 是必需的，应通过 type 配置项来指定。info 是可选的，其默认值可以通过 locales 的 defaultInfo 配置项来指定。content 可是任何合法的 Markdown 内容。提示
该插件可以被多次使用，以便支持不同类型的容器。
类型： Record<string, { defaultInfo: string }>
详情：
容器在不同 locales 下的默认 info 。
如果没有指定该配置项，默认 info 会使用大写的 type 。
示例：
export default {
+ plugins: [
+ containerPlugin({
+ type: 'tip',
+ locales: {
+ '/': {
+ defaultInfo: 'TIP',
+ },
+ '/zh/': {
+ defaultInfo: '提示',
+ },
+ },
+ }),
+ ],
+}
+类型： (info: string) => string
默认值：
(info: string): string =>
+ \`<div class="custom-container \${type}">\${info ? \`<p class="custom-container-title">\${info}</p>\` : ''}\\n\`
+类型： (info: string) => string
默认值：
(): string => '</div>\\n'
+type MarkdownItContainerRenderFunction = (
+ tokens: Token[],
+ index: number,
+ options: any,
+ env: MarkdownEnv,
+ self: Renderer,
+) => string
+This plugin will automatically add a copy button to the top right corner of each code block on PC devices.
The default selector matches @vuepress/theme-default, so you might need to change it when integrating your own theme.
npm i -D @vuepress/plugin-copy-code@next
+import { copyCodePlugin } from '@vuepress/plugin-copy-code'
+
+export default {
+ plugins: [
+ copyCodePlugin({
+ // options
+ }),
+ ],
+}
+Type: string | string[]
Default: '.theme-default-content div[class*="language-"] pre'
Details:
Code block selector
Type: boolean
Default: false
Details:
Whether to display copy button on the mobile device
Type: number
Default: 2000
Details:
Hint display time, setting it to 0 will disable the hint.
Type: number
Default: 800
Details:
The delay of registering copy code buttons, in ms.
If the theme you are using has a switching animation, it is recommended to configure this option to Switch animation duration + 200.
Type: CopyCodePluginLocaleConfig
interface CopyCodePluginLocaleData {
+ /**
+ * Copy text
+ */
+ copy: string
+
+ /**
+ * Copied text
+ */
+ copied: string
+}
+
+interface CopyCodePluginLocaleConfig {
+ [localePath: string]: CopyCodePluginLocaleData
+}
+Required: No
Details:
Locales config for copy code plugin.
Example:
import { copyCodePlugin } from '@vuepress/plugin-copy-code'
+
+export default {
+ locales: {
+ '/': {
+ // this is a supported language
+ lang: 'en-US',
+ },
+ '/xx/': {
+ // the plugin does not support this language
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ copyCodePlugin({
+ locales: {
+ '/': {
+ // Override copy button label text
+ copy: 'Copy Codes from code block',
+ },
+
+ '/xx/': {
+ // Complete locale config for \`mm-NN\` language here
+ },
+ },
+ }),
+ ],
+}
+You can customize the icon of the copy button via CSS variables:
:root {
+ --code-copy-icon: url("copy-button.svg");
+ --code-copied-icon: url("copied-button.svg");
+ --copy-code-color: #9e9e9e;
+ --copy-code-hover: rgb(0 0 0 / 50%);
+}
+此插件会自动在 PC 设备上为每个代码块右上角添加复制按钮。
默认选择器匹配 @vuepress/theme-default，所以在你自己的主题中集成时可能需要调整它。
npm i -D @vuepress/plugin-copy-code@next
+import { copyCodePlugin } from '@vuepress/plugin-copy-code'
+
+export default {
+ plugins: [
+ copyCodePlugin({
+ // options
+ }),
+ ],
+}
+类型：string | string[]
默认值：'.theme-default-content div[class*="language-"] pre'
详情:
代码块选择器
类型：boolean
默认值：false
详情:
是否展示在移动端
类型：number
默认值：2000
详情:
提示消息显示时间，设置为 0 会禁用提示。
类型：number
默认值：800
详情:
注册复制按钮的延时，单位 ms。
如果你使用的主题有切换动画，建议配置此选项为 切换动画时长 + 200
类型：CopyCodePluginLocaleConfig
interface CopyCodePluginLocaleData {
+ /**
+ * 复制文字
+ */
+ copy: string
+
+ /**
+ * 已复制文字
+ */
+ copied: string
+}
+
+interface CopyCodePluginLocaleConfig {
+ [localePath: string]: CopyCodePluginLocaleData
+}
+必填：否
详情:
复制按钮插件的国际化配置。
示例：
import { copyCodePlugin } from '@vuepress/plugin-copy-code'
+
+export default {
+ locales: {
+ '/': {
+ // 这是一个支持的语言
+ lang: 'zh-CN',
+ },
+ '/xx/': {
+ // 这是一个没有收到插件支持的语言
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ copyCodePlugin({
+ locales: {
+ '/': {
+ // 覆盖复制按钮标签文字
+ copy: '复制此段代码',
+ },
+
+ '/xx/': {
+ // 在这里完整设置 \`mm-NN\` 的多语言配置
+ },
+ },
+ }),
+ ],
+}
+你可以通过 CSS 变量来自定义复制按钮的样式：
:root {
+ --code-copy-icon: url("copy-button.svg");
+ --code-copied-icon: url("copied-button.svg");
+ --copy-code-color: #9e9e9e;
+ --copy-code-hover: rgb(0 0 0 / 50%);
+}
+此插件可以在访问者从你的站点复制内容时，自动追加版权信息，也可以禁止站点的复制或者选择。
npm i -D @vuepress/plugin-copyright@next
+import { copyrightPlugin } from '@vuepress/plugin-copyright'
+
+export default {
+ plugins: [
+ copyrightPlugin({
+ // options
+ }),
+ ],
+}
+此插件默认全局禁用。你可以:
copy: true 手动开启。global: true 让其全局生效，并在页面的 frontmatter 中设置 copy: false 禁用它。处于不打扰用户的考虑，默认配置下仅当复制长度超过 100 时才会追加版权信息。如果你希望改变这个触发值，你可以插件选项中设置 triggerLength，或在页面 frontmatter 单独设置 copy.triggerLength。
你可以通过插件的 author 和 license 选项设置全局作者和协议信息。
如果文档的不同部分拥有不同的作者和协议，你可以通过 authorGetter 和 licenseGetter 传入一个使用当前页面对象作为参数的函数 (page: Page) => string 并通过它返回相应信息。
插件会默认通过模板从作者、协议和页面链接生成版权信息，并在复制时追加。如果你认为这不够灵活，你可以设置 copyrightGetter 返回一个完全由你自定义的版权信息，或返回 null 以使用默认模板。
如果你希望禁止用户复制较长内容，你可以在插件选项中设置 maxLength 控制这个临界值，或在页面 frontmatter 单独设置 copy.maxLength。
disableCopy 或在页面 frontmatter 中设置 copy.disableCopy 来禁用复制，后者具有更高优先级。disableSelection 或在页面 frontmatter 中设置 copy.disableSelection 来禁用文字选择。此选项具有更高优先级stringstring(page: Page) => string | null(page: Page) => string | null(page: Page) => string | nullnumber100number00 意味着无限制。booleanfalsebooleanfalsebooleanfalse类型：string
详情：
首选部署位置。
例子
如果你在 https://myblog.com 和 https://blog.com/username/ 下部署相同的内容，你可能希望选择一个站点作为首选链接。
canonical 设置为 https://myblog.comcanonical 设置为 https://blog.com/username/这样，在另一个站点触发的版权信息也会指向你的首选站点。
类型：CopyrightPluginLocaleConfig
interface CopyrightPluginLocaleData {
+ /**
+ * 作者文字
+ *
+ * @description \`:author\` 将会被作者替换
+ */
+ author: string
+
+ /**
+ * 协议文字
+ *
+ * @description \`:license\` 会被当前协议替换
+ */
+ license: string
+
+ /**
+ * 链接文字
+ *
+ * @description \`:link\` 会替换为当前页面链接
+ */
+ link: string
+}
+
+interface CopyrightPluginLocaleConfig {
+ [localePath: string]: CopyrightPluginLocaleData
+}
+详情：版权插件的国际化配置。
示例：
import { copyrightPlugin } from '@vuepress/plugin-copyright'
+
+export default {
+ locales: {
+ '/': {
+ // this is a supported language
+ lang: 'en-US',
+ },
+ '/xx/': {
+ // the plugin does not support this language
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ copyrightPlugin({
+ locales: {
+ '/': {
+ // Override link text
+ link: 'Original posted at :link',
+ },
+
+ '/xx/': {
+ // Complete locale config for \`mm-NN\` language here
+ },
+ },
+ }),
+ ],
+}
+number100number00 意味着无限制。booleanfalsebooleanfalseThis plugin can automatically append copyright information when visitors copy content from your site, and can also prohibit site copying or selection.
npm i -D @vuepress/plugin-copyright@next
+import { copyrightPlugin } from '@vuepress/plugin-copyright'
+
+export default {
+ plugins: [
+ copyrightPlugin({
+ // options
+ }),
+ ],
+}
+This plugin is disabled globally by default, you can:
copy: true in page frontmatterglobal: true in plugin options to enable it globally, and set copy: false in page frontmatter to disable it.To avoid disturbing visitors, copyright information will be appended only when the copied content length is greater than 100. Set triggerLength in plugin options if you want to change this threshold, or via copy.triggerLength in page frontmatter.
You can set default author and license information via author and license in plugin options.
If your site have different authors and license in different pages, you can set authorGetter and licenseGetter with function (page: Page) => string that takes the current page object as parameter and returns the corresponding information.
The plugin will generate copyright information from author, license, and page link via template by default, and append it when copying. If you think that this is not flexible enough, you can set copyrightGetter option to return a completely customized information with Page object or return null to use the default template.
If you want to prevent users copying long content, you can set maxLength in plugin options to customize this limit, or via copy.maxLength in page frontmatter.
disableCopy in plugin options or copy.disableCopy in page frontmatter, the latter has higher priority.disableSelection in plugin options or copy.disableSelection in page frontmatter. This option has higher priority.stringstring(page: Page) => string | null(page: Page) => string | null(page: Page) => string | nullnumber100number00 means no limit.booleanfalsebooleanfalsebooleanfalsestringExample
If you are deploying same content under https://myblog.com and https://blog.com/username/, you may want to prefer one site as reference link.
canonical to https://myblog.comcanonical to https://blog.com/username/So copyright message triggered on another site also points to your preferred site.
Type: CopyrightPluginLocaleConfig
interface CopyrightPluginLocaleData {
+ /**
+ * Author text
+ *
+ * @description \`:author\` will be replaced by author
+ */
+ author: string
+
+ /**
+ * License text
+ *
+ * @description \`:license\` will be replaced by current license
+ */
+ license: string
+
+ /**
+ * Link text
+ *
+ * @description \`:link\` will be replaced by current page link
+ */
+ link: string
+}
+
+interface CopyrightPluginLocaleConfig {
+ [localePath: string]: CopyrightPluginLocaleData
+}
+Details: Locale config for copyright plugin.
Example:
import { copyrightPlugin } from '@vuepress/plugin-copyright'
+
+export default {
+ locales: {
+ '/': {
+ // this is a supported language
+ lang: 'en-US',
+ },
+ '/xx/': {
+ // the plugin does not support this language
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ copyrightPlugin({
+ locales: {
+ '/': {
+ // Override link text
+ link: 'Original posted at :link',
+ },
+
+ '/xx/': {
+ // Complete locale config for \`mm-NN\` language here
+ },
+ },
+ }),
+ ],
+}
+number100number00 means no limit.booleanfalsebooleanfalseTIP
Default theme will add DocSearch to the navbar once you configure this plugin correctly.
This plugin may not be used directly in other themes, so you'd better refer to the documentation of your theme for more details.
npm i -D @vuepress/plugin-docsearch@next
+import { docsearchPlugin } from '@vuepress/plugin-docsearch'
+
+export default {
+ plugins: [
+ docsearchPlugin({
+ // options
+ }),
+ ],
+}
+new Crawler({
+ appId: 'YOUR_APP_ID',
+ apiKey: 'YOUR_API_KEY',
+ rateLimit: 8,
+ startUrls: [
+ // These are urls which algolia start to craw
+ // If your site is divided in to mutiple parts,
+ // you may want to set mutiple entry links
+ 'https://YOUR_WEBSITE_URL/',
+ ],
+ sitemaps: [
+ // if you are using sitemap plugins (e.g.: @vuepress-plugin/sitemap), you may provide one
+ 'https://YOUR_WEBSITE_URL/sitemap.xml',
+ ],
+ ignoreCanonicalTo: false,
+ exclusionPatterns: [
+ // You can use this to stop algolia crawing some paths
+ ],
+ discoveryPatterns: [
+ // These are urls which algolia looking for,
+ 'https://YOUR_WEBSITE_URL/**',
+ ],
+ // Crawler schedule, set it according to your docs update frequency
+ schedule: 'at 02:00 every 1 day',
+ actions: [
+ // you may have mutiple actions, especially when you are deploying mutiple docs under one domain
+ {
+ // name the index with name you like
+ indexName: 'YOUR_INDEX_NAME',
+ // paths where the index take effect
+ pathsToMatch: ['https://YOUR_WEBSITE_URL/**'],
+ // controls how algolia extracts records from your site
+ recordExtractor: ({ $, helpers }) => {
+ // options for @vuepress/theme-default
+ return helpers.docsearch({
+ recordProps: {
+ lvl0: {
+ selectors: '.sidebar-heading.active',
+ defaultValue: 'Documentation',
+ },
+ lvl1: '.theme-default-content h1',
+ lvl2: '.theme-default-content h2',
+ lvl3: '.theme-default-content h3',
+ lvl4: '.theme-default-content h4',
+ lvl5: '.theme-default-content h5',
+ lvl6: '.theme-default-content h6',
+ content: '.theme-default-content p, .theme-default-content li',
+ },
+ indexHeadings: true,
+ })
+ },
+ },
+ ],
+ initialIndexSettings: {
+ // controls how index are initialized
+ // only has effects before index are initialize
+ // you may need to delete your index and recraw after modification
+ YOUR_INDEX_NAME: {
+ attributesForFaceting: ['type', 'lang'],
+ attributesToRetrieve: ['hierarchy', 'content', 'anchor', 'url'],
+ attributesToHighlight: ['hierarchy', 'hierarchy_camel', 'content'],
+ attributesToSnippet: ['content:10'],
+ camelCaseAttributes: ['hierarchy', 'hierarchy_radio', 'content'],
+ searchableAttributes: [
+ 'unordered(hierarchy_radio_camel.lvl0)',
+ 'unordered(hierarchy_radio.lvl0)',
+ 'unordered(hierarchy_radio_camel.lvl1)',
+ 'unordered(hierarchy_radio.lvl1)',
+ 'unordered(hierarchy_radio_camel.lvl2)',
+ 'unordered(hierarchy_radio.lvl2)',
+ 'unordered(hierarchy_radio_camel.lvl3)',
+ 'unordered(hierarchy_radio.lvl3)',
+ 'unordered(hierarchy_radio_camel.lvl4)',
+ 'unordered(hierarchy_radio.lvl4)',
+ 'unordered(hierarchy_radio_camel.lvl5)',
+ 'unordered(hierarchy_radio.lvl5)',
+ 'unordered(hierarchy_radio_camel.lvl6)',
+ 'unordered(hierarchy_radio.lvl6)',
+ 'unordered(hierarchy_camel.lvl0)',
+ 'unordered(hierarchy.lvl0)',
+ 'unordered(hierarchy_camel.lvl1)',
+ 'unordered(hierarchy.lvl1)',
+ 'unordered(hierarchy_camel.lvl2)',
+ 'unordered(hierarchy.lvl2)',
+ 'unordered(hierarchy_camel.lvl3)',
+ 'unordered(hierarchy.lvl3)',
+ 'unordered(hierarchy_camel.lvl4)',
+ 'unordered(hierarchy.lvl4)',
+ 'unordered(hierarchy_camel.lvl5)',
+ 'unordered(hierarchy.lvl5)',
+ 'unordered(hierarchy_camel.lvl6)',
+ 'unordered(hierarchy.lvl6)',
+ 'content',
+ ],
+ distinct: true,
+ attributeForDistinct: 'url',
+ customRanking: [
+ 'desc(weight.pageRank)',
+ 'desc(weight.level)',
+ 'asc(weight.position)',
+ ],
+ ranking: [
+ 'words',
+ 'filters',
+ 'typo',
+ 'attribute',
+ 'proximity',
+ 'exact',
+ 'custom',
+ ],
+ highlightPreTag: '<span class="algolia-docsearch-suggestion--highlight">',
+ highlightPostTag: '</span>',
+ minWordSizefor1Typo: 3,
+ minWordSizefor2Typos: 7,
+ allowTyposOnNumericTokens: false,
+ minProximity: 1,
+ ignorePlurals: true,
+ advancedSyntax: true,
+ attributeCriteriaComputedByMinProximity: true,
+ removeWordsIfNoResults: 'allOptional',
+ },
+ },
+})
+The above recordProps is the configuration used for the default theme. You can modify them according to the theme you are using.
Notice that the initialIndexSettings.YOUR_INDEX_NAME.attributesForFaceting fields must include 'lang' to make this plugin work properly.
Type: Record<string, DocsearchPluginOptions>
Details:
Options of this plugin in different locales.
All other options of this plugin are acceptable in locale config.
Example:
export default {
+ plugins: [
+ docsearchPlugin({
+ appId: '<APP_ID>',
+ apiKey: '<API_KEY>',
+ indexName: '<INDEX_NAME>',
+ locales: {
+ '/': {
+ placeholder: 'Search Documentation',
+ translations: {
+ button: {
+ buttonText: 'Search Documentation',
+ },
+ },
+ },
+ '/zh/': {
+ placeholder: '搜索文档',
+ translations: {
+ button: {
+ buttonText: '搜索文档',
+ },
+ },
+ },
+ },
+ }),
+ ],
+}
+Type: boolean
Default: true
Details:
Whether to inject the default styles of DocSearch or not.
If you think the default styles of DocSearch is not compatible with your site, you can try to override the default styles, or set this option to false to totally exclude the default styles.
When this option is disabled, you need to import your own styles for DocSearch. Also notice that all styles customization in Styles section would be unavailable.
:root {
+ --docsearch-primary-color: rgb(84, 104, 255);
+ --docsearch-text-color: rgb(28, 30, 33);
+ --docsearch-spacing: 12px;
+ --docsearch-icon-stroke-width: 1.4;
+ --docsearch-highlight-color: var(--docsearch-primary-color);
+ --docsearch-muted-color: rgb(150, 159, 175);
+ --docsearch-container-background: rgba(101, 108, 133, 0.8);
+ --docsearch-logo-color: rgba(84, 104, 255);
+
+ /* modal */
+ --docsearch-modal-width: 560px;
+ --docsearch-modal-height: 600px;
+ --docsearch-modal-background: rgb(245, 246, 247);
+ --docsearch-modal-shadow: inset 1px 1px 0 0 rgba(255, 255, 255, 0.5), 0 3px
+ 8px 0 rgba(85, 90, 100, 1);
+
+ /* searchbox */
+ --docsearch-searchbox-height: 56px;
+ --docsearch-searchbox-background: rgb(235, 237, 240);
+ --docsearch-searchbox-focus-background: #fff;
+ --docsearch-searchbox-shadow: inset 0 0 0 2px var(--docsearch-primary-color);
+
+ /* hit */
+ --docsearch-hit-height: 56px;
+ --docsearch-hit-color: rgb(68, 73, 80);
+ --docsearch-hit-active-color: #fff;
+ --docsearch-hit-background: #fff;
+ --docsearch-hit-shadow: 0 1px 3px 0 rgb(212, 217, 225);
+
+ /* key */
+ --docsearch-key-gradient: linear-gradient(
+ -225deg,
+ rgb(213, 219, 228) 0%,
+ rgb(248, 248, 248) 100%
+ );
+ --docsearch-key-shadow: inset 0 -2px 0 0 rgb(205, 205, 230), inset 0 0 1px 1px
+ #fff, 0 1px 2px 1px rgba(30, 35, 90, 0.4);
+
+ /* footer */
+ --docsearch-footer-height: 44px;
+ --docsearch-footer-background: #fff;
+ --docsearch-footer-shadow: 0 -1px 0 0 rgb(224, 227, 232), 0 -3px 6px 0 rgba(69, 98, 155, 0.12);
+}
+Details:
This plugin will register a <Docsearch /> component globally, and you can use it without any props.
Put this component to where you want to place the docsearch button. For example, default theme puts this component to the end of the navbar.
TIP
This component is mainly used for theme development. You don't need to use it directly in most cases.
提示
当你正确配置该插件后，默认主题会把 DocSearch 按钮添加到导航栏。
该插件不一定能在其他主题中直接使用，因此你应参考主题本身的文档来获取更多信息。
npm i -D @vuepress/plugin-docsearch@next
+import { docsearchPlugin } from '@vuepress/plugin-docsearch'
+
+export default {
+ plugins: [
+ docsearchPlugin({
+ // 配置项
+ }),
+ ],
+}
+new Crawler({
+ appId: 'YOUR_APP_ID',
+ apiKey: 'YOUR_API_KEY',
+ rateLimit: 8,
+ startUrls: [
+ // 这是 Algolia 开始抓取网站的初始地址
+ // 如果你的网站被分为数个独立部分，你可能需要在此设置多个入口链接
+ 'https://YOUR_WEBSITE_URL/',
+ ],
+ sitemaps: [
+ // 如果你在使用 Sitemap 插件 (如: @vuepress-plugin/sitemap)，你可以提供 Sitemap 链接
+ 'https://YOUR_WEBSITE_URL/sitemap.xml',
+ ],
+ ignoreCanonicalTo: false,
+ exclusionPatterns: [
+ // 你可以通过它阻止 Algolia 抓取某些 URL
+ ],
+ discoveryPatterns: [
+ // 这是 Algolia 抓取 URL 的范围
+ 'https://YOUR_WEBSITE_URL/**',
+ ],
+ // 爬虫执行的计划时间，可根据文档更新频率设置
+ schedule: 'at 02:00 every 1 day',
+ actions: [
+ // 你可以拥有多个 action，特别是你在一个域名下部署多个文档时
+ {
+ // 使用适当的名称为索引命名
+ indexName: 'YOUR_INDEX_NAME',
+ // 索引生效的路径
+ pathsToMatch: ['https://YOUR_WEBSITE_URL/**'],
+ // 控制 Algolia 如何抓取你的站点
+ recordExtractor: ({ $, helpers }) => {
+ // @vuepress/theme-default 的选项
+ return helpers.docsearch({
+ recordProps: {
+ lvl0: {
+ selectors: '.sidebar-heading.active',
+ defaultValue: 'Documentation',
+ },
+ lvl1: '.theme-default-content h1',
+ lvl2: '.theme-default-content h2',
+ lvl3: '.theme-default-content h3',
+ lvl4: '.theme-default-content h4',
+ lvl5: '.theme-default-content h5',
+ lvl6: '.theme-default-content h6',
+ content: '.theme-default-content p, .theme-default-content li',
+ },
+ indexHeadings: true,
+ })
+ },
+ },
+ ],
+ initialIndexSettings: {
+ // 控制索引如何被初始化，这仅当索引尚未生成时有效
+ // 你可能需要在修改后手动删除并重新生成新的索引
+ YOUR_INDEX_NAME: {
+ attributesForFaceting: ['type', 'lang'],
+ attributesToRetrieve: ['hierarchy', 'content', 'anchor', 'url'],
+ attributesToHighlight: ['hierarchy', 'hierarchy_camel', 'content'],
+ attributesToSnippet: ['content:10'],
+ camelCaseAttributes: ['hierarchy', 'hierarchy_radio', 'content'],
+ searchableAttributes: [
+ 'unordered(hierarchy_radio_camel.lvl0)',
+ 'unordered(hierarchy_radio.lvl0)',
+ 'unordered(hierarchy_radio_camel.lvl1)',
+ 'unordered(hierarchy_radio.lvl1)',
+ 'unordered(hierarchy_radio_camel.lvl2)',
+ 'unordered(hierarchy_radio.lvl2)',
+ 'unordered(hierarchy_radio_camel.lvl3)',
+ 'unordered(hierarchy_radio.lvl3)',
+ 'unordered(hierarchy_radio_camel.lvl4)',
+ 'unordered(hierarchy_radio.lvl4)',
+ 'unordered(hierarchy_radio_camel.lvl5)',
+ 'unordered(hierarchy_radio.lvl5)',
+ 'unordered(hierarchy_radio_camel.lvl6)',
+ 'unordered(hierarchy_radio.lvl6)',
+ 'unordered(hierarchy_camel.lvl0)',
+ 'unordered(hierarchy.lvl0)',
+ 'unordered(hierarchy_camel.lvl1)',
+ 'unordered(hierarchy.lvl1)',
+ 'unordered(hierarchy_camel.lvl2)',
+ 'unordered(hierarchy.lvl2)',
+ 'unordered(hierarchy_camel.lvl3)',
+ 'unordered(hierarchy.lvl3)',
+ 'unordered(hierarchy_camel.lvl4)',
+ 'unordered(hierarchy.lvl4)',
+ 'unordered(hierarchy_camel.lvl5)',
+ 'unordered(hierarchy.lvl5)',
+ 'unordered(hierarchy_camel.lvl6)',
+ 'unordered(hierarchy.lvl6)',
+ 'content',
+ ],
+ distinct: true,
+ attributeForDistinct: 'url',
+ customRanking: [
+ 'desc(weight.pageRank)',
+ 'desc(weight.level)',
+ 'asc(weight.position)',
+ ],
+ ranking: [
+ 'words',
+ 'filters',
+ 'typo',
+ 'attribute',
+ 'proximity',
+ 'exact',
+ 'custom',
+ ],
+ highlightPreTag: '<span class="algolia-docsearch-suggestion--highlight">',
+ highlightPostTag: '</span>',
+ minWordSizefor1Typo: 3,
+ minWordSizefor2Typos: 7,
+ allowTyposOnNumericTokens: false,
+ minProximity: 1,
+ ignorePlurals: true,
+ advancedSyntax: true,
+ attributeCriteriaComputedByMinProximity: true,
+ removeWordsIfNoResults: 'allOptional',
+ },
+ },
+})
+上述 recordProps 是用于默认主题的配置，你可以根据你使用的主题来修改它们。
注意 initialIndexSettings.YOUR_INDEX_NAME.attributesForFaceting 字段必须包含 'lang'，否则该插件将无法正常工作。
类型： Record<string, DocsearchPluginOptions>
详情：
在不同 locales 下对该插件进行不同的配置。
该插件的所有其他选项都可以在 locale 中进行配置。
示例：
export default {
+ plugins: [
+ docsearchPlugin({
+ appId: '<APP_ID>',
+ apiKey: '<API_KEY>',
+ indexName: '<INDEX_NAME>',
+ locales: {
+ '/': {
+ placeholder: 'Search Documentation',
+ translations: {
+ button: {
+ buttonText: 'Search Documentation',
+ },
+ },
+ },
+ '/zh/': {
+ placeholder: '搜索文档',
+ translations: {
+ button: {
+ buttonText: '搜索文档',
+ },
+ },
+ },
+ },
+ }),
+ ],
+}
+类型： boolean
默认值： true
详情：
是否注入 DocSearch 的默认样式。
如果你认为 DocSearch 的默认样式和你的站点不兼容，你可以尝试覆盖默认样式，或者将该选项设置为 false 来完全移除默认样式。
当该选项被禁用时，你需要为 DocSearch 引入你自己的样式。同时要注意，你也无法再使用 样式 章节中提到的样式自定义能力。
:root {
+ --docsearch-primary-color: rgb(84, 104, 255);
+ --docsearch-text-color: rgb(28, 30, 33);
+ --docsearch-spacing: 12px;
+ --docsearch-icon-stroke-width: 1.4;
+ --docsearch-highlight-color: var(--docsearch-primary-color);
+ --docsearch-muted-color: rgb(150, 159, 175);
+ --docsearch-container-background: rgba(101, 108, 133, 0.8);
+ --docsearch-logo-color: rgba(84, 104, 255);
+
+ /* modal */
+ --docsearch-modal-width: 560px;
+ --docsearch-modal-height: 600px;
+ --docsearch-modal-background: rgb(245, 246, 247);
+ --docsearch-modal-shadow: inset 1px 1px 0 0 rgba(255, 255, 255, 0.5), 0 3px
+ 8px 0 rgba(85, 90, 100, 1);
+
+ /* searchbox */
+ --docsearch-searchbox-height: 56px;
+ --docsearch-searchbox-background: rgb(235, 237, 240);
+ --docsearch-searchbox-focus-background: #fff;
+ --docsearch-searchbox-shadow: inset 0 0 0 2px var(--docsearch-primary-color);
+
+ /* hit */
+ --docsearch-hit-height: 56px;
+ --docsearch-hit-color: rgb(68, 73, 80);
+ --docsearch-hit-active-color: #fff;
+ --docsearch-hit-background: #fff;
+ --docsearch-hit-shadow: 0 1px 3px 0 rgb(212, 217, 225);
+
+ /* key */
+ --docsearch-key-gradient: linear-gradient(
+ -225deg,
+ rgb(213, 219, 228) 0%,
+ rgb(248, 248, 248) 100%
+ );
+ --docsearch-key-shadow: inset 0 -2px 0 0 rgb(205, 205, 230), inset 0 0 1px 1px
+ #fff, 0 1px 2px 1px rgba(30, 35, 90, 0.4);
+
+ /* footer */
+ --docsearch-footer-height: 44px;
+ --docsearch-footer-background: #fff;
+ --docsearch-footer-shadow: 0 -1px 0 0 rgb(224, 227, 232), 0 -3px 6px 0 rgba(69, 98, 155, 0.12);
+}
+详情：
该插件会全局注册一个 <Docsearch /> 组件，你可以不传入任何 Props 来使用它。
将该组件放置在你想要显示 docsearch 按钮的地方。例如，默认主题将这个组件放在了导航栏的末尾。
提示
该组件主要用于主题开发。在大多数情况下你不需要直接使用该组件。
VuePress 默认主题有着大量的用户，因此我们对它进行了一些便于继承的设计，以便用户轻松进行定制化。
默认主题的 Layout 布局提供了一些插槽：
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottom在它们的帮助下，你可以很容易地添加或替换内容。下面通过一个示例来介绍一下如何使用布局插槽来继承默认主题。
首先，创建一个客户端配置文件 .vuepress/client.ts ：
import { defineClientConfig } from 'vuepress/client'
+import Layout from './layouts/Layout.vue'
+
+export default defineClientConfig({
+ layouts: {
+ Layout,
+ },
+})
+接下来，创建 .vuepress/layouts/Layout.vue ，并使用由默认主题的 Layout 布局提供的插槽：
<script setup>
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+</script>
+
+<template>
+ <ParentLayout>
+ <template #page-bottom>
+ <div class="my-footer">This is my custom page footer</div>
+ </template>
+ </ParentLayout>
+</template>
+
+<style lang="css">
+.my-footer {
+ text-align: center;
+}
+</style>
+此时默认的 Layout 布局已经被你的本地布局覆盖，将会在除了首页外的所有页面添加一个自定义的页脚：
布局插槽十分实用，但有时候你可能会觉得它不够灵活。默认主题同样提供了替换单个组件的能力。
',14),d={href:"https://github.com/vuepress/ecosystem/tree/main/themes/theme-default/src/client/components",target:"_blank",rel:"noopener noreferrer"},y=n("code",null,"@theme",-1),m={href:"https://v2.vuepress.vuejs.org/zh/reference/plugin-api.html#alias",target:"_blank",rel:"noopener noreferrer"},C=n("code",null,"HomeFooter.vue",-1),u=n("code",null,"@theme/HomeFooter.vue",-1),v=l(`接下来，如果你想要替换 HomeFooter.vue 组件，只需要在配置文件 .vuepress/config.ts 中覆盖这个别名即可：
import { defaultTheme } from '@vuepress/theme-default'
+import { getDirname, path } from 'vuepress/utils'
+import { defineUserConfig } from 'vuepress'
+
+const __dirname = getDirname(import.meta.url)
+
+export default defineUserConfig({
+ theme: defaultTheme(),
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+})
+除了在 .vuepress/config.ts 和 .vuepress/client.ts 中直接扩展默认主题以外，你可以通过继承默认主题来开发一个你自己的主题：
import { defaultTheme, type DefaultThemeOptions } from '@vuepress/theme-default'
+import type { Theme } from 'vuepress/core'
+import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export const childTheme = (options: DefaultThemeOptions): Theme => {
+ return {
+ name: 'vuepress-theme-child',
+ extends: defaultTheme(options),
+
+ // 在子主题的客户端配置文件中覆盖布局
+ // 注意，你在发布到 NPM 之前会将 TS 构建为 JS ，因此这里需要设置为 JS 文件的路径
+ clientConfigFile: path.resolve(__dirname, './client.js'),
+
+ // 覆盖组件别名
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+ }
+}
+VuePress default theme is widely used by users, so it is designed to be extendable, allowing users to make their own customization with ease.
Default theme's Layout provides some slots:
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottomWith the help of them, you can add or replace content easily. Here comes an example to introduce how to extend default theme with layout slots.
Firstly, create a client config file .vuepress/client.ts:
import { defineClientConfig } from 'vuepress/client'
+import Layout from './layouts/Layout.vue'
+
+export default defineClientConfig({
+ layouts: {
+ Layout,
+ },
+})
+Next, create the .vuepress/layouts/Layout.vue, and make use of the slots that provided by the Layout of default theme:
<script setup>
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+</script>
+
+<template>
+ <ParentLayout>
+ <template #page-bottom>
+ <div class="my-footer">This is my custom page footer</div>
+ </template>
+ </ParentLayout>
+</template>
+
+<style lang="css">
+.my-footer {
+ text-align: center;
+}
+</style>
+Then the default Layout layout has been overridden by your own local layout, which will add a custom footer to every normal pages in default theme (excluding homepage):
The layout slots are useful, but sometimes you might find it's not flexible enough. Default theme also provides the ability to replace a single component.
',14),y={href:"https://v2.vuepress.vuejs.org/plugin-api.html#alias",target:"_blank",rel:"noopener noreferrer"},D={href:"https://github.com/vuepress/ecosystem/tree/main/themes/theme-default/src/client/components",target:"_blank",rel:"noopener noreferrer"},m=e("code",null,"@theme",-1),u=e("code",null,"HomeFooter.vue",-1),C=e("code",null,"@theme/HomeFooter.vue",-1),v=l(`Then, if you want to replace the HomeFooter.vue component, just override the alias in your config file .vuepress/config.ts:
import { defaultTheme } from '@vuepress/theme-default'
+import { getDirname, path } from 'vuepress/utils'
+import { defineUserConfig } from 'vuepress'
+
+const __dirname = getDirname(import.meta.url)
+
+export default defineUserConfig({
+ theme: defaultTheme(),
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+})
+Instead of extending the default theme directly in .vuepress/config.ts and .vuepress/client.ts, you can also develop your own theme extending the default theme:
import { defaultTheme, type DefaultThemeOptions } from '@vuepress/theme-default'
+import type { Theme } from 'vuepress/core'
+import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export const childTheme = (options: DefaultThemeOptions): Theme => {
+ return {
+ name: 'vuepress-theme-child',
+ extends: defaultTheme(options),
+
+ // override layouts in child theme's client config file
+ // notice that you would build ts to js before publishing to npm,
+ // so this should be the path to the js file
+ clientConfigFile: path.resolve(__dirname, './client.js'),
+
+ // override component alias
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+ }
+}
+This plugin has been integrated into the default theme.
npm i -D @vuepress/plugin-external-link-icon@next
+import { externalLinkIconPlugin } from '@vuepress/plugin-external-link-icon'
+
+export default {
+ plugins: [
+ externalLinkIconPlugin({
+ // options
+ }),
+ ],
+}
+Type: Record<string, { openInNewWindow: string }>
Details:
The a11y text of the external link icon in different locales.
If this option is not specified, it will fallback to default text.
Example:
export default {
+ plugins: [
+ externalLinkIconPlugin({
+ locales: {
+ '/': {
+ openInNewWindow: 'open in new window',
+ },
+ '/zh/': {
+ openInNewWindow: '在新窗口打开',
+ },
+ },
+ }),
+ ],
+}
+Type: boolean
Details:
Whether to append an external link icon to external links in current page.
You can customize the style of the external link icon via CSS variables:
:root {
+ --external-link-icon-color: #aaa;
+}
+Details:
This plugin will register a <ExternalLinkIcon /> component globally, and you can use it without any props.
TIP
This component is mainly used for theme development. You don't need to use it directly in most cases.
该插件已经集成到默认主题中。
npm i -D @vuepress/plugin-external-link-icon@next
+import { externalLinkIconPlugin } from '@vuepress/plugin-external-link-icon'
+
+export default {
+ plugins: [
+ externalLinkIconPlugin({
+ // 配置项
+ }),
+ ],
+}
+类型： Record<string, { openInNewWindow: string }>
详情：
外部链接图标在不同 locales 下的 A11y 文字。
如果没有指定该配置项，它会降级使用默认文字。
示例：
export default {
+ plugins: [
+ externalLinkIconPlugin({
+ locales: {
+ '/': {
+ openInNewWindow: 'open in new window',
+ },
+ '/zh/': {
+ openInNewWindow: '在新窗口打开',
+ },
+ },
+ }),
+ ],
+}
+类型： boolean
详情：
是否在当前页面的外部链接的后面添加外部链接图标。
你可以通过 CSS 变量来自定义外部链接图标的样式：
:root {
+ --external-link-icon-color: #aaa;
+}
+详情：
该插件会全局注册一个 <ExternalLinkIcon /> 组件，你可以不传入任何 Props 来使用它。
提示
该组件主要用于主题开发。在大多数情况下你不需要直接使用该组件。
Type: string
Details:
Add extra class name to this page.
Example:
---
+pageClass: custom-page-class
+---
+Then you can customize styles of this page in .vuepress/styles/index.scss file:
.theme-container.custom-page-class {
+ /* page styles */
+}
+Frontmatter in this section will only take effect in home pages.
Type: boolean
Details:
Specify whether the page is homepage or a normal page.
If you don't set this frontmatter or set it to false, the page would be a normal page.
Example:
---
+home: true
+---
+Type: string
Details:
Specify the url of the hero image.
Example:
---
+# public file path
+heroImage: /images/hero.png
+# url
+heroImage: https://vuejs.org/images/logo.png
+---
+Type: string
Details:
Specify the alt attribute of the hero image.
This will fallback to the heroText.
Array<{
+ text: string
+ link: string
+ type?: 'primary' | 'secondary'
+}>
+Details:
Configuration of the action buttons.
Example:
---
+actions:
+ - text: Get Started
+ link: /guide/getting-started.html
+ type: primary
+ - text: Introduction
+ link: /guide/introduction.html
+ type: secondary
+---
+Array<{
+ title: string
+ details: string
+}>
+Details:
Configuration of the features list.
Example:
---
+features:
+ - title: Simplicity First
+ details: Minimal setup with markdown-centered project structure helps you focus on writing.
+ - title: Vue-Powered
+ details: Enjoy the dev experience of Vue, use Vue components in markdown, and develop custom themes with Vue.
+ - title: Performant
+ details: VuePress generates pre-rendered static HTML for each page, and runs as an SPA once a page is loaded.
+---
+Type: string
Details:
Specify the content of the footer.
Type: boolean
Details:
Allow HTML in footer or not.
If you set it to true, the footer will be treated as HTML code.
Frontmatter in this section will only take effect in normal pages.
Type: NavLink | string
Details:
Specify the link of the previous page.
If you don't set this frontmatter, the link will be inferred from the sidebar config.
To configure the prev link manually, you can set this frontmatter to a NavLink object or a string:
NavLink object should have a text field and a link field.NavLink object, whose text is the page title, and link is the page route path.Example:
---
+# NavLink
+prev:
+ text: Get Started
+ link: /guide/getting-started.html
+
+# NavLink - external url
+prev:
+ text: GitHub
+ link: https://github.com
+
+# string - page file path
+prev: /guide/getting-started.md
+
+# string - page file relative path
+prev: ../../guide/getting-started.md
+---
+Type: NavLink | string
Details:
Specify the link of the next page.
If you don't set this frontmatter, the link will be inferred from the sidebar config.
The type is the same as prev frontmatter.
类型：SitemapFrontmatterOptions | false
详情：
false 表示将页面排除在 sitemap 之外。
类型：number
默认值：0.5
详情：
页面优先级，范围 0 至 1。
类型： string
详情：
为当前页面添加额外的类名。
示例：
---
+pageClass: custom-page-class
+---
+然后你可以在 .vuepress/styles/index.scss 文件中为这个页面添加自定义样式：
.theme-container.custom-page-class {
+ /* 页面样式 */
+}
+本章节中的 Frontmatter 只会在首页中生效。
类型： boolean
详情：
设定该页面是首页还是普通页面。
如果你不设置该 Frontmatter 或将其设为 false ，则该页面会是一个 普通页面
示例：
---
+home: true
+---
+类型： string
详情：
首页图片的 URL 。
示例：
---
+# Public 文件路径
+heroImage: /images/hero.png
+# URL
+heroImage: https://vuejs.org/images/logo.png
+---
+类型： string
详情：
首页图片的 alt 属性。
如果不设置，则默认使用 heroText 。
Array<{
+ text: string
+ link: string
+ type?: 'primary' | 'secondary'
+}>
+详情：
配置首页按钮。
示例：
---
+actions:
+ - text: 快速上手
+ link: /zh/guide/getting-started.html
+ type: primary
+ - text: 项目简介
+ link: /zh/guide/introduction.html
+ type: secondary
+---
+Array<{
+ title: string
+ details: string
+}>
+详情：
配置首页特性列表。
示例：
---
+features:
+ - title: 简洁至上
+ details: 以 Markdown 为中心的项目结构，以最少的配置帮助你专注于写作。
+ - title: Vue 驱动
+ details: 享受 Vue 的开发体验，可以在 Markdown 中使用 Vue 组件，又可以使用 Vue 来开发自定义主题。
+ - title: 高性能
+ details: VuePress 会为每个页面预渲染生成静态的 HTML，同时，每个页面被加载的时候，将作为 SPA 运行。
+---
+类型： string
详情：
首页的页脚。
类型： boolean
详情：
是否允许页脚中使用 HTML 。
如果设置为 true ，那么 footer 会被作为 HTML 代码处理。
本章节中的 Frontmatter 只会在普通页面中生效。
类型： NavLink | string
详情：
上一个页面的链接。
如果你不设置该 Frontmatter ，该链接会自动根据侧边栏配置进行推断。
为了手动配置上一页面的链接，你可以将其设置为一个 NavLink 对象或者一个字符串：
NavLink 对象应该有一个 text 字段和一个 link 字段。NavLink 对象，将页面标题作为 text ，将页面路由路径作为 link 。示例：
---
+# NavLink
+prev:
+ text: Get Started
+ link: /guide/getting-started.html
+
+# NavLink - 外部 URL
+prev:
+ text: GitHub
+ link: https://github.com
+
+# 字符串 - 页面文件路径
+prev: /guide/getting-started.md
+
+# 字符串 - 页面文件相对路径
+prev: ../../guide/getting-started.md
+---
+类型： NavLink | string
详情：
下一个页面的链接。
如果你不设置该 Frontmatter ，该链接会自动根据侧边栏配置进行推断。
类型和 prev Frontmatter 相同。
你可以通过配置每个页面的 Frontmatter，来对每个 Feed 项目生成进行单独的控制。
默认情况下，所有文章均会被添加至 feed 流。如果你想在 feed 中移除特定页面，你可以在 frontmatter 中设置 feed: false。
string由 VuePress 自动生成，默认为页面的 h1 内容
string页面描述
Date页面的发布日期
boolean该页面是否是文章
如果此项设置为
false，则该页不会包含在最终的 feed 中。
string页面版权信息
string页面的封面/分享图，需为完整链接或绝对链接。
stringFeed 项目的标题
stringFeed 项目的描述
stringFeed 项目的内容
FeedAuthor[] | FeedAuthorFeed 项目的作者
interface FeedAuthor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+FeedContributor[] | FeedContributorFeed 项目的贡献者
interface FeedContributor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+stringFeed 项目的标识符，用于标识 Feed 项目。
你应该确保每个 Feed 项目有全局唯一的 guid。
Type: SitemapFrontmatterOptions | false
Details:
false means exclude the page from sitemap.
Type: number
Default: 0.5
Details:
Page priority, range from 0 to 1.
You can control each feed item generation by setting page frontmatter.
By default, all articles are added to the feed stream. Set feed: false in frontmatter to remove a page from feed.
stringAutomatically generated by VuePress, defaults to the h1 content of the page
stringDescription of the page
DateDate when the page was published
booleanWhether the page is an article
If this is set to
false, the page will not be included in the final feed.
stringPage copyright information
stringImage used as page cover , should be full link or absolute link.
stringThe title of the feed item
stringDescription of the feed item
stringThe content of the feed item
FeedAuthor[] | FeedAuthorThe author of the feed item
interface FeedAuthor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+FeedContributor[] | FeedContributorContributors to feed item
interface FeedContributor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+stringThe identifier of feed item, used to identify the feed item.
You should ensure every feed has a unique guid.
You can take full control of feed items generation by setting getter in the plugin options.
(page: Page) => stringItem title getter
(page: Page) => stringItem link getter
(page: Page) => string | undefinedItem description getter
TIP
Due to Atom support HTML in summary, so you can return HTML content here if possible, but the content must start with mark html:.
(page: Page) => stringItem content getter
(page: Page) => FeedAuthor[]Item author getter.
The getter should return an empty array when author information is missing.
interface FeedAuthor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => FeedCategory[] | undefinedItem category getter.
interface FeedCategory {
+ /**
+ * Category Name
+ */
+ name: string
+
+ /**
+ * A string that identifies a categorization taxonomy
+ *
+ * @description rss format only
+ */
+ domain?: string
+
+ /**
+ * the categorization scheme via a URI
+ *
+ * @description atom format only
+ */
+ scheme?: string
+}
+(page: Page) => FeedEnclosure | undefinedItem enclosure getter.
interface FeedEnclosure {
+ /**
+ * Enclosure link
+ */
+ url: string
+
+ /**
+ * what its type is
+ *
+ * @description should be a standard MIME Type, rss format only
+ */
+ Type: string
+
+ /**
+ * Size in bytes
+ *
+ * @description rss format only
+ */
+ length?: number
+}
+(page: Page) => Date | undefinedItem release date getter
(page: Page) => DateItem last update date getter
(page: Page) => stringItem Image Getter
Ensure it's returning a full URL
(page: Page) => FeedContributor[]Item Contributor Getter
The getter should return an empty array when contributor information is missing.
interface FeedContributor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => string | undefinedItem copyright getter
`,46),i=[t];function r(p,o){return e(),n("div",null,i)}const d=s(l,[["render",r],["__file","getter.html.vue"]]),u=JSON.parse('{"path":"/plugins/feed/getter.html","title":"Feed Getter","lang":"en-US","frontmatter":{"description":"Feed Getter You can take full control of feed items generation by setting getter in the plugin options. getter.title Type: (page: Page) => string Item title getter getter.link T...","head":[["link",{"rel":"alternate","hreflang":"zh-cn","href":"https://ecosystem.vuejs.press/ecosystem/zh/plugins/feed/getter.html"}],["meta",{"property":"og:url","content":"https://ecosystem.vuejs.press/ecosystem/plugins/feed/getter.html"}],["meta",{"property":"og:site_name","content":"VuePress Ecosystem"}],["meta",{"property":"og:title","content":"Feed Getter"}],["meta",{"property":"og:description","content":"Feed Getter You can take full control of feed items generation by setting getter in the plugin options. getter.title Type: (page: Page) => string Item title getter getter.link T..."}],["meta",{"property":"og:type","content":"article"}],["meta",{"property":"og:locale","content":"en-US"}],["meta",{"property":"og:locale:alternate","content":"zh-CN"}],["meta",{"property":"og:updated_time","content":"2024-02-01T04:46:03.000Z"}],["meta",{"property":"article:modified_time","content":"2024-02-01T04:46:03.000Z"}],["script",{"type":"application/ld+json"},"{\\"@context\\":\\"https://schema.org\\",\\"@type\\":\\"Article\\",\\"headline\\":\\"Feed Getter\\",\\"image\\":[\\"\\"],\\"dateModified\\":\\"2024-02-01T04:46:03.000Z\\",\\"author\\":[]}"],["link",{"rel":"alternate","type":"application/atom+xml","href":"https://ecosystem.vuejs.press/ecosystem/atom.xml","title":"VuePress Ecosystem Atom Feed"}],["link",{"rel":"alternate","type":"application/json","href":"https://ecosystem.vuejs.press/ecosystem/feed.json","title":"VuePress Ecosystem JSON Feed"}],["link",{"rel":"alternate","type":"application/rss+xml","href":"https://ecosystem.vuejs.press/ecosystem/rss.xml","title":"VuePress Ecosystem RSS Feed"}]]},"headers":[{"level":2,"title":"getter.title","slug":"getter-title","link":"#getter-title","children":[]},{"level":2,"title":"getter.link","slug":"getter-link","link":"#getter-link","children":[]},{"level":2,"title":"getter.description","slug":"getter-description","link":"#getter-description","children":[]},{"level":2,"title":"getter.content","slug":"getter-content","link":"#getter-content","children":[]},{"level":2,"title":"getter.author","slug":"getter-author","link":"#getter-author","children":[]},{"level":2,"title":"getter.category","slug":"getter-category","link":"#getter-category","children":[]},{"level":2,"title":"getter.enclosure","slug":"getter-enclosure","link":"#getter-enclosure","children":[]},{"level":2,"title":"getter.publishDate","slug":"getter-publishdate","link":"#getter-publishdate","children":[]},{"level":2,"title":"getter.lastUpdateDate","slug":"getter-lastupdatedate","link":"#getter-lastupdatedate","children":[]},{"level":2,"title":"getter.image","slug":"getter-image","link":"#getter-image","children":[]},{"level":2,"title":"getter.contributor","slug":"getter-contributor","link":"#getter-contributor","children":[]},{"level":2,"title":"getter.copyright","slug":"getter-copyright","link":"#getter-copyright","children":[]}],"git":{"updatedTime":1706762763000,"contributors":[{"name":"Mr.Hope","email":"mister-hope@outlook.com","commits":2}]},"autoDesc":true,"filePathRelative":"plugins/feed/getter.md"}');export{d as comp,u as data}; diff --git a/assets/getter.html-zrG8Ss32.js b/assets/getter.html-zrG8Ss32.js new file mode 100644 index 0000000000..d5681a76b8 --- /dev/null +++ b/assets/getter.html-zrG8Ss32.js @@ -0,0 +1,91 @@ +import{_ as s,o as e,c as n,e as a}from"./app-3y2wReKQ.js";const l={},t=a(`你可以通过控制插件选项中的 getter 来完全控制 Feed 项目的生成。
(page: Page) => string项目标题获取器
(page: Page) => string项目链接获取器
(page: Page) => string | undefined项目描述获取器
提示
因为 Atom 在摘要中支持 HTML，所以如果可能的话，你可以在这里返回 HTML 内容，但内容必须以标记 html: 开头。
(page: Page) => string项目内容获取器
(page: Page) => FeedAuthor[]项目作者获取器。
获取器应在作者信息缺失时返回空数组。
interface FeedAuthor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => FeedCategory[] | undefined项目分类获取器。
interface FeedCategory {
+ /**
+ * 分类名称
+ */
+ name: string
+
+ /**
+ * 标识分类法的字符串
+ *
+ * @description rss format only
+ */
+ domain?: string
+
+ /**
+ * URI 标识的分类 scheme
+ *
+ * @description atom format only
+ */
+ scheme?: string
+}
+(page: Page) => FeedEnclosure | undefined项目附件获取器。
interface FeedEnclosure {
+ /**
+ * Enclosure 地址
+ */
+ url: string
+
+ /**
+ * 类型
+ *
+ * @description 应为一个标准的 MIME 类型，rss format only
+ */
+ type: string
+
+ /**
+ * 按照字节数计算的大小
+ *
+ * @description rss format only
+ */
+ length?: number
+}
+(page: Page) => Date | undefined项目发布日期获取器
(page: Page) => Date项目最后更新日期获取器
(page: Page) => string项目图片获取器
确保返回一个完整的 URL。
(page: Page) => FeedContributor[]项目贡献者获取器
获取器应在贡献者信息缺失时返回空数组。
interface FeedContributor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => string | undefined项目版权获取器
`,46),i=[t];function p(r,c){return e(),n("div",null,i)}const d=s(l,[["render",p],["__file","getter.html.vue"]]),u=JSON.parse('{"path":"/zh/plugins/feed/getter.html","title":"Feed 获取器","lang":"zh-CN","frontmatter":{"description":"Feed 获取器 你可以通过控制插件选项中的 getter 来完全控制 Feed 项目的生成。 getter.title 类型：(page: Page) => string 项目标题获取器 getter.link 类型：(page: Page) => string 项目链接获取器 getter.description 类型：(page: Page) =...","head":[["link",{"rel":"alternate","hreflang":"en-us","href":"https://ecosystem.vuejs.press/ecosystem/plugins/feed/getter.html"}],["meta",{"property":"og:url","content":"https://ecosystem.vuejs.press/ecosystem/zh/plugins/feed/getter.html"}],["meta",{"property":"og:site_name","content":"VuePress 生态系统"}],["meta",{"property":"og:title","content":"Feed 获取器"}],["meta",{"property":"og:description","content":"Feed 获取器 你可以通过控制插件选项中的 getter 来完全控制 Feed 项目的生成。 getter.title 类型：(page: Page) => string 项目标题获取器 getter.link 类型：(page: Page) => string 项目链接获取器 getter.description 类型：(page: Page) =..."}],["meta",{"property":"og:type","content":"article"}],["meta",{"property":"og:locale","content":"zh-CN"}],["meta",{"property":"og:locale:alternate","content":"en-US"}],["meta",{"property":"og:updated_time","content":"2024-02-01T04:46:03.000Z"}],["meta",{"property":"article:modified_time","content":"2024-02-01T04:46:03.000Z"}],["script",{"type":"application/ld+json"},"{\\"@context\\":\\"https://schema.org\\",\\"@type\\":\\"Article\\",\\"headline\\":\\"Feed 获取器\\",\\"image\\":[\\"\\"],\\"dateModified\\":\\"2024-02-01T04:46:03.000Z\\",\\"author\\":[]}"],["link",{"rel":"alternate","type":"application/atom+xml","href":"https://ecosystem.vuejs.press/ecosystem/zh/atom.xml","title":"VuePress 生态系统 Atom Feed"}],["link",{"rel":"alternate","type":"application/json","href":"https://ecosystem.vuejs.press/ecosystem/zh/feed.json","title":"VuePress 生态系统 JSON Feed"}],["link",{"rel":"alternate","type":"application/rss+xml","href":"https://ecosystem.vuejs.press/ecosystem/zh/rss.xml","title":"VuePress 生态系统 RSS Feed"}]]},"headers":[{"level":2,"title":"getter.title","slug":"getter-title","link":"#getter-title","children":[]},{"level":2,"title":"getter.link","slug":"getter-link","link":"#getter-link","children":[]},{"level":2,"title":"getter.description","slug":"getter-description","link":"#getter-description","children":[]},{"level":2,"title":"getter.content","slug":"getter-content","link":"#getter-content","children":[]},{"level":2,"title":"getter.author","slug":"getter-author","link":"#getter-author","children":[]},{"level":2,"title":"getter.category","slug":"getter-category","link":"#getter-category","children":[]},{"level":2,"title":"getter.enclosure","slug":"getter-enclosure","link":"#getter-enclosure","children":[]},{"level":2,"title":"getter.publishDate","slug":"getter-publishdate","link":"#getter-publishdate","children":[]},{"level":2,"title":"getter.lastUpdateDate","slug":"getter-lastupdatedate","link":"#getter-lastupdatedate","children":[]},{"level":2,"title":"getter.image","slug":"getter-image","link":"#getter-image","children":[]},{"level":2,"title":"getter.contributor","slug":"getter-contributor","link":"#getter-contributor","children":[]},{"level":2,"title":"getter.copyright","slug":"getter-copyright","link":"#getter-copyright","children":[]}],"git":{"updatedTime":1706762763000,"contributors":[{"name":"Mr.Hope","email":"mister-hope@outlook.com","commits":2}]},"autoDesc":true,"filePathRelative":"zh/plugins/feed/getter.md"}');export{d as comp,u as data}; diff --git a/assets/giscus-7BMGhbDA.js b/assets/giscus-7BMGhbDA.js new file mode 100644 index 0000000000..db345b1f75 --- /dev/null +++ b/assets/giscus-7BMGhbDA.js @@ -0,0 +1,66 @@ +/** + * @license + * Copyright 2019 Google LLC + * SPDX-License-Identifier: BSD-3-Clause + */const H=globalThis,V=H.ShadowRoot&&(H.ShadyCSS===void 0||H.ShadyCSS.nativeShadow)&&"adoptedStyleSheets"in Document.prototype&&"replace"in CSSStyleSheet.prototype,q=Symbol(),J=new WeakMap;let ot=class{constructor(t,e,s){if(this._$cssResult$=!0,s!==q)throw Error("CSSResult is not constructable. Use `unsafeCSS` or `css` instead.");this.cssText=t,this.t=e}get styleSheet(){let t=this.o;const e=this.t;if(V&&t===void 0){const s=e!==void 0&&e.length===1;s&&(t=J.get(e)),t===void 0&&((this.o=t=new CSSStyleSheet).replaceSync(this.cssText),s&&J.set(e,t))}return t}toString(){return this.cssText}};const ut=i=>new ot(typeof i=="string"?i:i+"",void 0,q),$t=(i,...t)=>{const e=i.length===1?i[0]:t.reduce((s,r,o)=>s+(n=>{if(n._$cssResult$===!0)return n.cssText;if(typeof n=="number")return n;throw Error("Value passed to 'css' function must be a 'css' function result: "+n+". Use 'unsafeCSS' to pass non-literal values, but take care to ensure page security.")})(r)+i[o+1],i[0]);return new ot(e,i,q)},_t=(i,t)=>{if(V)i.adoptedStyleSheets=t.map(e=>e instanceof CSSStyleSheet?e:e.styleSheet);else for(const e of t){const s=document.createElement("style"),r=H.litNonce;r!==void 0&&s.setAttribute("nonce",r),s.textContent=e.cssText,i.appendChild(s)}},F=V?i=>i:i=>i instanceof CSSStyleSheet?(t=>{let e="";for(const s of t.cssRules)e+=s.cssText;return ut(e)})(i):i;/** + * @license + * Copyright 2017 Google LLC + * SPDX-License-Identifier: BSD-3-Clause + */const{is:gt,defineProperty:ft,getOwnPropertyDescriptor:mt,getOwnPropertyNames:At,getOwnPropertySymbols:yt,getPrototypeOf:St}=Object,A=globalThis,Q=A.trustedTypes,vt=Q?Q.emptyScript:"",Y=A.reactiveElementPolyfillSupport,U=(i,t)=>i,L={toAttribute(i,t){switch(t){case Boolean:i=i?vt:null;break;case Object:case Array:i=i==null?i:JSON.stringify(i)}return i},fromAttribute(i,t){let e=i;switch(t){case Boolean:e=i!==null;break;case Number:e=i===null?null:Number(i);break;case Object:case Array:try{e=JSON.parse(i)}catch{e=null}}return e}},K=(i,t)=>!gt(i,t),Z={attribute:!0,type:String,converter:L,reflect:!1,hasChanged:K};Symbol.metadata??(Symbol.metadata=Symbol("metadata")),A.litPropertyMetadata??(A.litPropertyMetadata=new WeakMap);class E extends HTMLElement{static addInitializer(t){this._$Ei(),(this.l??(this.l=[])).push(t)}static get observedAttributes(){return this.finalize(),this._$Eh&&[...this._$Eh.keys()]}static createProperty(t,e=Z){if(e.state&&(e.attribute=!1),this._$Ei(),this.elementProperties.set(t,e),!e.noAccessor){const s=Symbol(),r=this.getPropertyDescriptor(t,s,e);r!==void 0&&ft(this.prototype,t,r)}}static getPropertyDescriptor(t,e,s){const{get:r,set:o}=mt(this.prototype,t)??{get(){return this[e]},set(n){this[e]=n}};return{get(){return r==null?void 0:r.call(this)},set(n){const a=r==null?void 0:r.call(this);o.call(this,n),this.requestUpdate(t,a,s)},configurable:!0,enumerable:!0}}static getPropertyOptions(t){return this.elementProperties.get(t)??Z}static _$Ei(){if(this.hasOwnProperty(U("elementProperties")))return;const t=St(this);t.finalize(),t.l!==void 0&&(this.l=[...t.l]),this.elementProperties=new Map(t.elementProperties)}static finalize(){if(this.hasOwnProperty(U("finalized")))return;if(this.finalized=!0,this._$Ei(),this.hasOwnProperty(U("properties"))){const e=this.properties,s=[...At(e),...yt(e)];for(const r of s)this.createProperty(r,e[r])}const t=this[Symbol.metadata];if(t!==null){const e=litPropertyMetadata.get(t);if(e!==void 0)for(const[s,r]of e)this.elementProperties.set(s,r)}this._$Eh=new Map;for(const[e,s]of this.elementProperties){const r=this._$Eu(e,s);r!==void 0&&this._$Eh.set(r,e)}this.elementStyles=this.finalizeStyles(this.styles)}static finalizeStyles(t){const e=[];if(Array.isArray(t)){const s=new Set(t.flat(1/0).reverse());for(const r of s)e.unshift(F(r))}else t!==void 0&&e.push(F(t));return e}static _$Eu(t,e){const s=e.attribute;return s===!1?void 0:typeof s=="string"?s:typeof t=="string"?t.toLowerCase():void 0}constructor(){super(),this._$Ep=void 0,this.isUpdatePending=!1,this.hasUpdated=!1,this._$Em=null,this._$Ev()}_$Ev(){var t;this._$ES=new Promise(e=>this.enableUpdating=e),this._$AL=new Map,this._$E_(),this.requestUpdate(),(t=this.constructor.l)==null||t.forEach(e=>e(this))}addController(t){var e;(this._$EO??(this._$EO=new Set)).add(t),this.renderRoot!==void 0&&this.isConnected&&((e=t.hostConnected)==null||e.call(t))}removeController(t){var e;(e=this._$EO)==null||e.delete(t)}_$E_(){const t=new Map,e=this.constructor.elementProperties;for(const s of e.keys())this.hasOwnProperty(s)&&(t.set(s,this[s]),delete this[s]);t.size>0&&(this._$Ep=t)}createRenderRoot(){const t=this.shadowRoot??this.attachShadow(this.constructor.shadowRootOptions);return _t(t,this.constructor.elementStyles),t}connectedCallback(){var t;this.renderRoot??(this.renderRoot=this.createRenderRoot()),this.enableUpdating(!0),(t=this._$EO)==null||t.forEach(e=>{var s;return(s=e.hostConnected)==null?void 0:s.call(e)})}enableUpdating(t){}disconnectedCallback(){var t;(t=this._$EO)==null||t.forEach(e=>{var s;return(s=e.hostDisconnected)==null?void 0:s.call(e)})}attributeChangedCallback(t,e,s){this._$AK(t,s)}_$EC(t,e){var o;const s=this.constructor.elementProperties.get(t),r=this.constructor._$Eu(t,s);if(r!==void 0&&s.reflect===!0){const n=(((o=s.converter)==null?void 0:o.toAttribute)!==void 0?s.converter:L).toAttribute(e,s.type);this._$Em=t,n==null?this.removeAttribute(r):this.setAttribute(r,n),this._$Em=null}}_$AK(t,e){var o;const s=this.constructor,r=s._$Eh.get(t);if(r!==void 0&&this._$Em!==r){const n=s.getPropertyOptions(r),a=typeof n.converter=="function"?{fromAttribute:n.converter}:((o=n.converter)==null?void 0:o.fromAttribute)!==void 0?n.converter:L;this._$Em=r,this[r]=a.fromAttribute(e,n.type),this._$Em=null}}requestUpdate(t,e,s){if(t!==void 0){if(s??(s=this.constructor.getPropertyOptions(t)),!(s.hasChanged??K)(this[t],e))return;this.P(t,e,s)}this.isUpdatePending===!1&&(this._$ES=this._$ET())}P(t,e,s){this._$AL.has(t)||this._$AL.set(t,e),s.reflect===!0&&this._$Em!==t&&(this._$Ej??(this._$Ej=new Set)).add(t)}async _$ET(){this.isUpdatePending=!0;try{await this._$ES}catch(e){Promise.reject(e)}const t=this.scheduleUpdate();return t!=null&&await t,!this.isUpdatePending}scheduleUpdate(){return this.performUpdate()}performUpdate(){var s;if(!this.isUpdatePending)return;if(!this.hasUpdated){if(this.renderRoot??(this.renderRoot=this.createRenderRoot()),this._$Ep){for(const[o,n]of this._$Ep)this[o]=n;this._$Ep=void 0}const r=this.constructor.elementProperties;if(r.size>0)for(const[o,n]of r)n.wrapped!==!0||this._$AL.has(o)||this[o]===void 0||this.P(o,this[o],n)}let t=!1;const e=this._$AL;try{t=this.shouldUpdate(e),t?(this.willUpdate(e),(s=this._$EO)==null||s.forEach(r=>{var o;return(o=r.hostUpdate)==null?void 0:o.call(r)}),this.update(e)):this._$EU()}catch(r){throw t=!1,this._$EU(),r}t&&this._$AE(e)}willUpdate(t){}_$AE(t){var e;(e=this._$EO)==null||e.forEach(s=>{var r;return(r=s.hostUpdated)==null?void 0:r.call(s)}),this.hasUpdated||(this.hasUpdated=!0,this.firstUpdated(t)),this.updated(t)}_$EU(){this._$AL=new Map,this.isUpdatePending=!1}get updateComplete(){return this.getUpdateComplete()}getUpdateComplete(){return this._$ES}shouldUpdate(t){return!0}update(t){this._$Ej&&(this._$Ej=this._$Ej.forEach(e=>this._$EC(e,this[e]))),this._$EU()}updated(t){}firstUpdated(t){}}E.elementStyles=[],E.shadowRootOptions={mode:"open"},E[U("elementProperties")]=new Map,E[U("finalized")]=new Map,Y==null||Y({ReactiveElement:E}),(A.reactiveElementVersions??(A.reactiveElementVersions=[])).push("2.0.4");/** + * @license + * Copyright 2017 Google LLC + * SPDX-License-Identifier: BSD-3-Clause + */const P=globalThis,k=P.trustedTypes,X=k?k.createPolicy("lit-html",{createHTML:i=>i}):void 0,ht="$lit$",m=`lit$${(Math.random()+"").slice(9)}$`,at="?"+m,Et=`<${at}>`,v=document,N=()=>v.createComment(""),R=i=>i===null||typeof i!="object"&&typeof i!="function",ct=Array.isArray,bt=i=>ct(i)||typeof(i==null?void 0:i[Symbol.iterator])=="function",j=`[ +\f\r]`,w=/<(?:(!--|\/[^a-zA-Z])|(\/?[a-zA-Z][^>\s]*)|(\/?$))/g,tt=/-->/g,et=/>/g,y=RegExp(`>|${j}(?:([^\\s"'>=/]+)(${j}*=${j}*(?:[^ +\f\r"'\`<>=]|("|')|))|$)`,"g"),st=/'/g,it=/"/g,lt=/^(?:script|style|textarea|title)$/i,Ct=i=>(t,...e)=>({_$litType$:i,strings:t,values:e}),wt=Ct(1),b=Symbol.for("lit-noChange"),l=Symbol.for("lit-nothing"),rt=new WeakMap,S=v.createTreeWalker(v,129);function dt(i,t){if(!Array.isArray(i)||!i.hasOwnProperty("raw"))throw Error("invalid template strings array");return X!==void 0?X.createHTML(t):t}const Ut=(i,t)=>{const e=i.length-1,s=[];let r,o=t===2?"":"")),s]};class I{constructor({strings:t,_$litType$:e},s){let r;this.parts=[];let o=0,n=0;const a=t.length-1,h=this.parts,[d,u]=Ut(t,e);if(this.el=I.createElement(d,s),S.currentNode=this.el.content,e===2){const c=this.el.content.firstChild;c.replaceWith(...c.childNodes)}for(;(r=S.nextNode())!==null&&h.lengthThis plugin is mainly used to develop themes. You won't need to use it directly in most cases.
npm i -D @vuepress/plugin-git@next
+import { gitPlugin } from '@vuepress/plugin-git'
+
+export default {
+ plugins: [
+ gitPlugin({
+ // options
+ }),
+ ],
+}
+WARNING
This plugin will significantly slow down the speed of data preparation, especially when you have a lot of pages. You can consider disabling this plugin in dev mode to get better development experience.
Type: boolean
Default: true
Details:
Whether to collect page created time or not.
Type: boolean
Default: true
Details:
Whether to collect page updated time or not.
Type: boolean
Default: true
Details:
Whether to collect page contributors or not.
Type: string[]
Details:
An array of relative paths to be included when calculating page data.
Example:
---
+gitInclude:
+ - relative/path/to/file1
+ - relative/path/to/file2
+---
+This plugin will add a git field to page data.
After using this plugin, you can get the collected git information in page data:
import type { GitPluginPageData } from '@vuepress/plugin-git'
+import { usePageData } from 'vuepress/client'
+
+export default {
+ setup() {
+ const page = usePageData<GitPluginPageData>()
+ console.log(page.value.git)
+ },
+}
+Type: number
Details:
Unix timestamp in milliseconds of the first commit of the page.
This attribute would take the minimum of the first commit timestamps of the current page and the files listed in gitInclude.
Type: number
Details:
Unix timestamp in milliseconds of the last commit of the page.
This attribute would take the maximum of the last commit timestamps of the current page and the files listed in gitInclude.
GitContributor[]interface GitContributor {
+ name: string
+ email: string
+ commits: number
+}
+Details:
The contributors information of the page.
This attribute would also include contributors to the files listed in gitInclude.
该插件主要用于开发主题，大部分情况下你不需要直接使用它。
npm i -D @vuepress/plugin-git@next
+import { gitPlugin } from '@vuepress/plugin-git'
+
+export default {
+ plugins: [
+ gitPlugin({
+ // 配置项
+ }),
+ ],
+}
+注意
该插件会显著降低准备数据的速度，特别是在你的页面数量很多的时候。你可以考虑在 dev 模式下禁用该插件来获取更好的开发体验。
类型： boolean
默认值： true
详情：
是否收集页面的创建时间。
类型： boolean
默认值： true
详情：
是否收集页面的更新时间。
类型： boolean
默认值： true
详情：
是否收集页面的贡献者。
类型： string[]
详情：
文件相对路径组成的数组，该数组中的文件会在计算页面数据时被包含在内。
示例：
---
+gitInclude:
+ - relative/path/to/file1
+ - relative/path/to/file2
+---
+该插件会向页面数据中添加一个 git 字段。
在使用该插件后，可以在页面数据中获取该插件收集到的 Git 信息：
import type { GitPluginPageData } from '@vuepress/plugin-git'
+import { usePageData } from 'vuepress/client'
+
+export default {
+ setup() {
+ const page = usePageData<GitPluginPageData>()
+ console.log(page.value.git)
+ },
+}
+类型： number
详情：
页面第一次提交的 Unix 毫秒时间戳。
该属性将取当前页面及 gitInclude 中所列文件的第一次提交的时间戳的最小值。
类型： number
详情：
页面最后一次提交的 Unix 毫秒时间戳。
该属性将取当前页面及 gitInclude 中所列文件的最后一次提交的时间戳的最大值。
GitContributor[]interface GitContributor {
+ name: string
+ email: string
+ commits: number
+}
+详情：
页面的贡献者信息。
该属性将会包含 gitInclude 所列文件的贡献者。
npm i -D @vuepress/plugin-google-analytics@next
+import { googleAnalyticsPlugin } from '@vuepress/plugin-google-analytics'
+
+export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ // options
+ }),
+ ],
+}
+export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ id: 'G-XXXXXXXXXX',
+ }),
+ ],
+}
+export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ id: 'G-XXXXXXXXXX',
+ debug: true,
+ }),
+ ],
+}
+npm i -D @vuepress/plugin-google-analytics@next
+import { googleAnalyticsPlugin } from '@vuepress/plugin-google-analytics'
+
+export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ // 配置项
+ }),
+ ],
+}
+export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ id: 'G-XXXXXXXXXX',
+ }),
+ ],
+}
+export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ id: 'G-XXXXXXXXXX',
+ debug: true,
+ }),
+ ],
+}
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+// .vuepress/config.ts
+export default {
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo
+
+ // 在这里放置其他选项
+ // ...
+ }),
+ ],
+}
+import { defineClientConfig } from 'vuepress/client'
+import {
+ defineArtalkConfig,
+ // defineGiscusConfig,
+ // defineTwikooConfig,
+ // defineWalineConfig,
+} from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+有以下你需要注意的限制：
`,5),D=e("p",null,[e("code",null,"provider"),s("、多语言设置和其他资源相关选项必须在插件选项中设置。")],-1),g=e("p",null,"为确保 tree-shaking 有效，我们必须在 Node 一侧优化入口，以便打包器可以了解最终打包中应包含哪些资源。",-1),f=e("p",null,"不能序列化为 JSON 的选项必须在客户端配置中设置。",-1),C=e("p",null,"接收复杂值的选项（例如：函数）不能在插件选项中设置，因为插件运行在 Node.js 环境下，所以我们无法将这些值和它们的上下文传递给浏览器。",-1),_=i('该插件全局注册了一个组件 <CommentService />。
alias 和布局槽来插入组件。 我们建议你在 <PageNav /> 组件之后插入评论组件 (<CommentService />)，本页可作为一个 Demo 作为参考。默认情况下，<CommentService /> 组件是全局启用的，你可以在插件选项和页面 frontmatter 中使用 comment 选项来控制它。
comment: false 在本地禁用它。comment 设置为 false。 然后你可以在页面 frontmatter 中设置 comment: true 以在局部启用它。你可以在页面 frontmatter 中设置 commentID 选项来自定义评论 ID，该 ID 用于标识要用于页面的评论存储项。默认情况下，它将是页面的 path ，这意味着如果你将站点部署到多个位置，站点间具有相同内容的页面将共享相同的评论数据。
"Artalk" | "Giscus" | "Twikoo" | "Waline" | "None""None"booleantrueThe plugin works out of the box. Without any config, it will extract information from the page content as much as possible to complete the necessary tags required by OGP and JSON-LD.
By default, the plugin will read the site config and page frontmatter to automatically generate tags as much as possible. Such as site name, page title, page type, writing date, last update date, and article tags are all automatically generated.
The following are the <meta> tags and their values that will be injected into <head> by default:
The following are the <meta> tags and their value injected into <head> by default to satisfy OGP:
| Meta Name | Value |
|---|---|
og:url | options.hostname + path |
og:site_name | siteConfig.title |
og:title | page.title |
og:description | page.frontmatter.description || auto generated (when autoDescription is true in plugin options) |
og:type | "article" |
og:image | page.frontmatter.banner || page.frontmatter.cover || first image in page || fallbackImage in plugin options |
og:updated_time | page.git.updatedTime |
og:locale | page.lang |
og:locale:alternate | Other languages in siteData.locales |
twitter:card | "summary_large_image" (only available when image found) |
twitter:image:alt | page.title (only available when image found) |
article:author | page.frontmatter.author || options.author |
article:tag | page.frontmatter.tags || page.frontmatter.tag |
article:published_time | page.frontmatter.date || page.git.createdTime |
article:modified_time | page.git.updatedTime |
| Property Name | Value |
|---|---|
@context | "https://schema.org" |
@type | "NewsArticle" |
headline | page.title |
image | image in page || options.hostname + page.frontmatter.image || siteFavIcon in plugin options |
datePublished | page.frontmatter.date || page.git.createdTime |
dateModified | page.git.updatedTime |
author | page.frontmatter.author || options.author |
You can configure the head option in the page's frontmatter to add specific tags to the page <head> to enhance SEO. For example:
---
+head:
+ - - meta
+ - name: keywords
+ content: SEO plugin
+---
+Will automatically inject <meta name="keywords" content="SEO plugin" />.
The plugin also gives you full control over the build logic.
For most pages, there are basically only two types: articles and website, so the plugin provides the isArticle option to allow you to provide logic for identifying articles.
The option accepts a function in the format (page: Page) => boolean, by default all non-home pages generated from Markdown files are treated as articles.
TIP
If a page does fit into the "unpopular" genre like books, music, etc., you can handle them by setting the three options below.
You can use the plugin options ogp to pass in a function to modify the default OGP object to your needs and return it.
function ogp(
+ /** OGP Object inferred by plugin */
+ ogp: SeoContent,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+For example, if you are using a third-party theme and set a banner in frontmatter for each article according to the theme requirements, then you can pass in the following ogp:
seoPlugin({
+ ogp: (ogp, page) => ({
+ ...ogp,
+ 'og:image': page.frontmatter.banner || ogp['og:image'],
+ }),
+})
+Like OGP, you can use the plugin options jsonLd to pass in a function to modify the default JSON-LD object to your needs and return it.
function jsonLd(
+ /** JSON-LD Object inferred by plugin */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+If you are deploying your content to different sites, or same content under different URLs, you may need to set canonical option to provide a "Canonical Link" for your page. You can either set a string which will be appended before page route link, or adding a custom function (page: Page) => string | null to return a canonical link if necessary.
Example
If your sites are deployed under docs directory in example.com, but available in:
http://example.com/docs/xxxhttps://example.com/docs/xxxhttp://www.example.com/docs/xxxhttps://www.example.com/docs/xxx (primary)To let search engine results always be the primary choice, you may need to set canonical to https://www.example.com/docs/, so that search engine will know that the fourth URL is preferred to be indexed.
Sometimes you may need to fit other protocols or provide the corresponding SEO tags in the format provided by other search engines. In this case, you can use the customHead option, whose type is:
function customHead(
+ /** Head tag config */
+ head: HeadConfig[],
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+You should modify the head array in this function directly.
Search engine optimization (SEO) is the process of improving the quality and quantity of site traffic to a site or a web page from search engines. SEO targets unpaid traffic (known as "natural" or "organic" results) rather than direct traffic or paid traffic. Unpaid traffic may originate from different kinds of searches, including image search, video search, academic search, news search, and industry-specific vertical search engines.
As an internet marketing strategy, SEO considers how search engines work, the computer-programmed algorithms that dictate search engine behavior, what people search for, the actual search terms or keywords typed into search engines, and which search engines are preferred by their targeted audience. SEO is performed because a site will receive more visitors from a search engine when sites rank higher on the search engine results page (SERP). These visitors can then potentially be converted into customers.
本插件会为你的网站自动生成 Sitemap。为了使插件正常工作，你需要将部署的域名传递给插件的 hostname 选项。如果你想在开发服务器中预览，请配置 devServer 选项。
插件会自动根据页面的 Git 的时间戳生成页面的最后更新时间，同时会根据站点的多语言配置声明页面的其他语言版本替代地址。
默认情况下，所有除 404 页面以外的网站链接均会被添加进 Sitemap。
如果你希望在 VuePress 项目页面之外，添加其他页面链接到 Sitemap，请将它们变成数组传入插件的 extraUrls 选项。
如果你需要排除一些页面路径，你可以将它们变成数组传入到插件的 excludePaths 选项。你也可以在对应页面的 frontmatter 中，设置 sitemap 为 false。
你还可以通过插件的 sitemapFilename 选项控制输出的地址，此地址相对于输出目录，默认为 sitemap.xml。
页面默认的更新周期是 daily (每天)，如果你希望修改全部的页面周期，请在插件选项中设置 changefreq 。你也可以在页面的 frontmatter 中设置 sitemap.changefreq，页面具有更高的优先级。
合法的频率有:
"always""hourly""daily""weekly""monthly""yearly""never"你可以在插件中设置 priority 以提供一个默认值。同时你可以通过 frontmatter 中的 sitemap.priority 来为每个页面设置优先级。可接受的值为 0 到 1 的浮点数。
你可以通过插件的 modifyTimeGetter 来返回一个 ISO 字符串格式的时间，默认会通过 Git 插件生成。
以下是一个基于文件最后修改时间的例子。
// 基于文件最后修改时间
+({
+ modifyTimeGetter: (page, app) =>
+ fs.statSync(app.dir.source(page.filePathRelative)).mtime.toISOString();
+})
+网站地图 (Sitemap) 提供搜索引擎优化 (SEO):
网站地图通过使所有页面可被找到来增强搜索引擎优化的效果。
大部分搜索引擎只跟踪页面内有限数量的链接，因此当网站非常大的时候，网站地图对于使搜索引擎和访问者可以访问网站中的所有内容就变得必不可少了。
Sitemaps 是站点管理员向搜索引擎爬虫公布站点可被抓取页面的协议，sitemap 文件内容必须遵循 XML 格式的定义。每个 URL 可以包含更新的周期和时间、URL 在整个站点中的优先级。这样可以让搜索引擎更佳有效的抓取网站内容。
同步配置 robots.txt
由于 Sitemap 面向搜索引擎，配合此插件使用时，你最好保证你在 .vuepress/public 文件夹下放置了有效的 robots.txt，以允许搜索引擎收录。一个最简单的 robots.txt 如下 (允许所有搜索引擎访问所有路径)
User-agent: *
+
+Allow: /
+This plugin will automatically generate a Sitemap for your site. To let this plugin work, you need to pass the deployed domain name to the hostname option of the plugin. If you want to preview in devServer, set devServer options.
The plugin will automatically generate the last update time of the page based on the Git timestamp of the page, and will also declare the alternative links of the page in other languages according to the locales' config.
By default, all site links except 404 page will be added to the Sitemap.
To add other pages to the Sitemap outside the VuePress project page, please turn them into an array and pass to the extraUrls plugin option.
If you don't want certain pages to appear in the sitemap, you can turn their paths into an array and pass to the excludePaths plugin option, or set sitemap to false in the frontmatter of the corresponding page.
You can also control the output link through the sitemapFilename option of the plugin, the link is relative to output directory. By default, the plugin will use sitemap.xml.
The default update cycle of the page is daily (every day). To modify the entire page cycle, please set changefreq in the plugin options. You can also set sitemap.changefreq in the frontmatter of the page. Note that page has a higher priority.
The legal frequencies are:
"always""hourly""daily""weekly""monthly""yearly""never"You can set priority in the plugin to provide a default value. At the same time you can set the priority for each page through sitemap.priority in frontmatter. Acceptable values are floating point numbers from 0 to 1.
You can use option modifyTimeGetter to return a time in ISO string format, which is generated by the Git plugin by default.
The following is an example based on the last modification time of a file.
// Based on file last modified time
+({
+ modifyTimeGetter: (page, app) =>
+ fs.statSync(app.dir.source(page.filePathRelative)).mtime.toISOString();
+})
+Sitemaps provide SEO (Search Engine Optimization):
A sitemap enhances SEO by making all pages findable.
Most search engines only follow a limited number of links within a page, so when the site is very large, a sitemap becomes essential to make everything on the site accessible to search engines and visitors.
Sitemaps is a protocol for site administrators to publish pages that can be crawled on a site to search engine spiders. The content of sitemap files must follow the definition in XML format. Each URL can contain the update period and last update time, the priority of the URL across the site. This allows search engines to crawl site content better and more efficiently.
Together with robots.txt
Sitemap is basically used by search engines, when using this plugin, you'd better ensure that you have a valid robots.txt in the .vuepress/public directory to allow search engines spiders to visit your site. The simplest robots.txt is as follows (allow all search engines to access all paths)
User-agent: *
+
+Allow: /
+插件可为你生成以下三种格式的 feed 文件:
请按照需要生成的格式，在插件选项中设置 atom, json 或 rss 为 true。
为了正确生成 Feed 链接，你需要在插件选项中设置 hostname。
如果你想在开发服务器中预览 Feed，你需要在插件选项中设置 devServer: true。如果你没有使用默认的 http://localhost:{port}，你还需要设置 devHostname。
你可以通过设置 channel 选项来自自定义 Feed 频道的各项信息。
我们推荐进行如下设置:
channel.pubDate 中channel.ttl 中设置内容的更新周期(单位: 分钟)channel.copyright 设置版权信息channel.author 设置频道作者。With @vuepress/plugin-blog, you can easily bring blog feature into your theme.
The plugin filters all pages using filter option to drop pages you don't want.
By default, all pages generating from Markdown files but not homepage are considered as articles.
You can fully customize pages to collect through option filter, which accepts a function (page: Page) => boolean.
You should set getInfo option with a function accepting Page as argument and returning an object containing the info you want.
The plugin will collect all the info you want and write them to routeMeta field of each page, so you will be able to get this information through Composition API later.
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ filter: ({ filePathRelative, frontmatter }) => {
+ // drop those pages which is NOT generated from file
+ if (!filePathRelative) return false
+
+ // drop those pages in \`archives\` directory
+ if (filePathRelative.startsWith('archives/')) return false
+
+ // drop those pages which do not use default layout
+ if (frontmatter.home || frontmatter.layout) return false
+
+ return true
+ },
+
+ getInfo: ({ frontmatter, git = {}, data = {} }) => {
+ // getting page info
+ const info: Record<string, any> = {
+ author: frontmatter.author || '',
+ categories: frontmatter.categories || [],
+ date: frontmatter.date || git.createdTime || null,
+ tags: frontmatter.tags || [],
+ excerpt: data.excerpt || '',
+ }
+
+ return info
+ },
+ }),
+ // other plugins ...
+ ],
+}
+Basically, you would want 2 types of collection in your blog:
Category:
"Category" means grouping articles with their labels.
For example, each article may have their "categories" and "tags".
Type:
"Type" means identifying articles with conditions.
For example, you may want to describe some of your articles as diary.
After understanding description of these 2 types, you can set category and type options, each accepts an array, and each element represents a configuration.
Let's start with 2 examples here.
Imagine you are setting tags for each articles with tag field in page frontmatter. You want a tag mapping page in /tag/ with TagMap layout, and group each tag list with tagName in /tag/tagName with TagList layout, you probably need a configuration like this:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // other options ...
+ category: [
+ {
+ key: 'tag',
+ getter: ({ frontmatter }) => frontmatter.tag || [],
+ path: '/tag/',
+ layout: 'TagMap',
+ frontmatter: () => ({ title: 'Tag page' }),
+ itemPath: '/tag/:name/',
+ itemLayout: 'TagList',
+ itemFrontmatter: (name) => ({ title: \`Tag \${name}\` }),
+ },
+ ],
+ }),
+ // other plugins ...
+ ],
+}
+Also, you may want to star some of your articles, and display them to visitors. When you are setting star: true in frontmatter to mark them, you probably need a configuration like this to display them in /star/ path with StarList layout:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // other options ...
+ type: [
+ {
+ key: 'star',
+ filter: ({ frontmatter }) => frontmatter.star,
+ path: '/star/',
+ layout: 'StarList',
+ frontmatter: () => ({ title: 'Star page' }),
+ },
+ ],
+ }),
+ // other plugins ...
+ ],
+}
+When generating each page, the plugin will set following information under frontmatter.blog:
interface BlogFrontmatterOptions {
+ /** Current type of the page */
+ type: 'category' | 'type'
+ /** Unique key under current category or tag */
+ key: string
+ /**
+ * Current category name
+ *
+ * @description Only available in category item page
+ */
+ name?: string
+}
+So you can invoke useBlogCategory() and useBlogType() directly, and the result will be the category or type bind to current route.
Also, you can pass key you want as argument, then you will get information bind to that key.
So with node side settings above, you can get information about "tag" and "star" in client side:
TagMap layout:
<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+
+<template>
+ <div>
+ <h1>Tag page</h1>
+ <ul>
+ <li v-for="({ items, path }, name) in categoryMap.map">
+ <RouteLink :key="name" :to="path" class="category">
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </li>
+ </ul>
+ </div>
+</template>
+TagList layout:
<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+
+<template>
+ <div>
+ <h1>Tag page</h1>
+ <div class="category-wrapper">
+ <RouteLink
+ v-for="({ items, path }, name) in categoryMap.map"
+ :key="name"
+ :to="path"
+ class="category"
+ >
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </div>
+ <div class="article-wrapper" v-if="categoryMap.currentItems">
+ <div v-if="!categoryMap.currentItems.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in categoryMap.currentItems"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline
+ ? \`\${new Date(info.date).toLocaleDateString()}: \`
+ : '') + info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author"
+ >Author: {{ info.author }}</span
+ >
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag"
+ >Tag: {{ info.tag.join(', ') }}</span
+ >
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+ </div>
+</template>
+StarList layout:
<script setup lang="ts">
+import { useBlogType } from '@vuepress/plugin-blog/client'
+import { RouteLink } from 'vuepress/client'
+
+import ArticleList from '../components/ArticleList.vue'
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+
+const stars = useBlogType('star')
+</script>
+
+<template>
+ <div class="article-wrapper" v-if="stars.items">
+ <div v-if="!stars.items.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in stars.items"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline ? \`\${new Date(info.date).toLocaleDateString()}: \` : '') +
+ info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author">Author: {{ info.author }}</span>
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag">Tag: {{ info.tag.join(', ') }}</span>
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+</template>
+This plugin adds native i18n support, so your settings will be automatically applied to each language.
For example, if user has the following locales' config, and you are setting the "star" example above:
export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+}
+Then /zh/star/ and /star/ will both be available, and only articles under the correct locale will appear.
This plugin provides a built-in excerpt generator, which can be enabled by setting excerpt option to true.
Excerpt introduction
An excerpt is an HTML fragment that is used to display a short description of an article in the blog list, so the excerpt has the following restrictions:
isCustomElement option..vuepress/public or full URL to ensure they can be accessed in other places.The excerpt generator will try to find a valid excerpt separator from markdown contents, if it finds one, it will use content before the separator. The separator is default <!-- more -->, and you can customize it by setting excerptSeparator option.
If it cannot find a valid separator, it will parse content from the beginning of markdown file, and stop till its length reaches a preset value. The value is default 300, and you can customize it by setting excerptLength option.
To choose which page should generate excerpt, you can use excerptFilter option.
Example
Normally you may want to use frontmatter.description if users set them, so you can let filter function return false if frontmatter.description is not empty.
将你的 VuePress 站点变成渐进式网络应用程序 (PWA)[1]。
',3),h={href:"https://developers.google.com/web/tools/workbox/modules/workbox-build",target:"_blank",rel:"noopener noreferrer"},f={href:"https://github.com/yyx990803/register-service-worker",target:"_blank",rel:"noopener noreferrer"},y={class:"custom-container warning"},D=e("p",{class:"custom-container-title"},"注意",-1),m=t(`A PWA uses a Service Worker [2] (SW for short) to cache and proxy site content.
一个 PWA 使用 Service Worker [2:1] (简称 SW) 来获取并托管网站内容。
为了使你的网站符合 PWA 的要求，一个网络 App 清单[3]文件是必要的，并且你的 PWA 应满足可安装性[4]要求。
你可以通过设置 manifest 选项来自定义 manifest 文件，或者在 public 文件夹中提供 manifest.webmanifest 或 manifest.json。前者优先级更高。
插件会自动为你生成 manifest.webmanifest，并在每个页面的 <head> 中添加清单链接声明，但是 你至少应该通过 manifest.icons 或 PWA 插件中的其他选项设置一个有效的图标。
注意
可安装性[4:1]规范要求 manifest 中至少声明一个有效的图标。
所以如果你不配置 manifest.icons，访问者只能享受到 Service Worker 缓存带来的离线可访问性，而并不能作为 PWA 进行安装。
此外，该插件默认不处理清单中的任何内容，而是按原样输出。 这意味着，如果你计划部署到子目录，则应自行将 URL 前缀附加到自己的清单 Urls 中。如果你需要的所有东西都在 base 文件夹下，你可以在插件选项中设置 appendBase: true 让插件将 base 自动附加到任何地址。
为了更好的控制 Service Worker 可以预缓存的内容，插件提供了相关的缓存控制选项。
默认情况下插件会预缓存所有的 JS 和 CSS 文件，但仅缓存主页和 404 页面的 HTML。插件同时还会缓存字体文件 (woff, woff2, eot, ttf, otf) 和 SVG 图标。
如果你的站点只有少量重要图片，并希望它们在离线模式下显示，你可以通过设置 cacheImage 选项为 true 来缓存站点图片。
我们通过文件后缀名识别图片，任何以 .png, .jpg, .jpeg, .gif, .bmp, .webp 结尾的文件都会视为图片。
当你网站体积不大，并且希望文档完全离线可用时，你可以通过设置 cacheHTML 为 true 来缓存所有 HTML 页面。
为什么默认不缓存非主页和 404 页面
虽然说 VuePress 为所有的页面通过 SSG[5] 生成了 HTML 文件，但是这些文件主要用于 SEO[6]，并能够让你在后端不做 SPA[7] 配置的情况下能够直接访问任何链接。
VuePress 本质上是一个 SPA。这意味着你只需要缓存主页并从主页进入即可正常访问所有页面。所以默认不缓存其他 HTML 能够有效减小缓存大小 (可以缩减大约 40% 的体积)，加快 SW 更新速度。
但是这样做也有缺点，如果用户直接从非主页进入网站，首个页面的 HTML 文件仍需要从互联网加载。同时离线环境下，用户只能通过主页进入再自行导航到对应页面，直接访问某个链接会出现无法访问的提示。
为了防止在预缓存列表中包含大文件，任何 > 2 MB 的文件或 > 1 MB 的图片都将被忽略。 你可以通过 maxSize 和 maxImageSize 来自定义大小限制 (单位为 KB)。
我们提供 update 选项控制用户如何接收更新。
update 选项的默认值是 "available"，这意味着当网站内容更新后，新的 SW 会在后台静默安装，并在安装结束后弹窗提示用户新内容就绪。用户可以自主选择是否立即刷新查看新内容。这意味在新 SW 就绪前用户会访问旧版本网站。
如果你的文档仍在建设期，希望尽早提示用户他可能在阅读已过时的内容，你可以将其设置为 "hint"。这样用户在进入文档后数秒内就可以收到新内容已发布的通知。但这样做的负面效果是如果用户在新 SW 就绪前选择更新，那么他将在新 SW 安装并接管页面前，需要从互联网获取页面的全部资源。
如果你的文档很稳定，或者你在托管博客，不太关心用户立即接收到最新版本，你可以将其设置为 "disabled"，这意味着新的 SW 将在后台完全静默安装并在安装后等待，当旧版本 SW 控制的页面全部关闭后，新 SW 将再下次访问接管并提供用户新内容。此设置可以避免用户在访中被弹窗打扰。
如果你希望通过 SW 来加速用户在弱网或无网条件下的访问，但同时希望用户时刻访问新内容，你可以将此选项设置为 "force"。这意味着检测到新 SW 后旧 SW 将会被立刻销毁并且页面会被刷新以确保用户浏览最新内容。最大的缺点就是致新 SW 发布后，用户在重新进入网站后的几秒内会遇到预期之外的突然刷新，并且他们将必须通过互联网访问文档并完全重新安装最新的 SW。
当检测到新内容 (检测到新的 SW) 时，更新提示弹窗将会出现；当新内容就绪时，更新就绪弹窗将会出现。
如果你对默认的弹窗不满意，你可以自行编写组件更换。从 @vuepress/plugin-pwa/client 中导入 PwaFoundPopup 或 PwaReadyPopup 并使用其 slot 来自定义弹窗内容，然后将组件路径传递给 foundComponent 或 readyComponent 选项。
<script setup lang="ts">
+import { PwaFoundPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaFoundPopup v-slot="{ found, refresh }">
+ <div v-if="found">
+ 已找到新内容
+ <button @click="refresh">刷新</button>
+ </div>
+ </PwaFoundPopup>
+</template>
+<script setup lang="ts">
+import { PwaReadyPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaReadyPopup v-slot="{ isReady, reload }">
+ <div v-if="isReady">
+ 新内容已就绪
+ <button @click="reload">应用</button>
+ </div>
+ </PwaReadyPopup>
+</template>
+Service Worker 简要介绍
Service Worker 会在注册过程中获取注册在其中的所有文件并缓存它们。
注册成功后，Service Worker 激活，并开始代理并控制你的全部请求。
每当你想要通过浏览器发起访问请求后，Service Worker 将会查看其是否存在与自身缓存列表中，若存在则直接返回缓存好的结果，否则调用自身的 fetch 方法进行获取。你可以通过自定义 fetch 方法，来完全控制网页内资源获取请求的结果，比如在离线时提供一个 fallback 的网页。
每次用户重新打开网站时，Service Worker 会向自身注册时的地址发出校验命令，如果检测到新版本的 Service Worker，则会更新自身，并开始缓存注册在新 Service Worker 中的资源列表。成功获取内容更新后，Service Worker 将会触发 update 事件。可以通过此事件提示用户，比如将在右下角显示一个弹出窗口，提示用户新内容可用并允许用户触发更新。
可安装性
想要让网站可以注册为 PWA，网站需要自行成功注册有效的 Service Worker，同时拥有合法的 manifest 清单文件并在网站中声明它。
清单文件应至少包含 name(或 short_name) icons start_url。
SSG: Static Site Generating，静态站点生成。 ↩︎
The plugin can generate feed files in the following three formats for you:
Please set atom, json or rss to true in the plugin options according to the formats you want to generate.
To correctly generate feed links, you need to set hostname in the plugin options,
If you want to preview your feed in devServer, set devServer: true in plugin options. You may also need to set devHostname if you are not using the default http://localhost:{port}.
You can customize the feed channel information by setting the channel option.
We recommend the following settings:
channel.pubDatechannel.ttl (unit: minutes)channel.copyrightchannel.author.使用 @vuepress/plugin-blog，你可以轻松地将博客功能引入主题。
起步时，插件会首选过滤并选择那些需要作为文章的页面。这将剔除你不想要的页面，并在后续处理中排除它们。
默认情况下，所有从 Markdown 文件生成但不是主页的页面，都将被视作文章。
你可能需要设置 filter 选项来完全自定义要收集的页面。 filter 接受一个形状为 (page: Page) => boolean 的函数。
接着，你应该设置 getInfo 选项为一个接受 Page 作为参数并返回包含所需信息的对象的函数。这样稍后，你可以从组合 API 中获取这些信息。
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ filter: ({ filePathRelative, frontmatter }) => {
+ // 舍弃那些不是从 Markdown 文件生成的页面
+ if (!filePathRelative) return false
+
+ // 舍弃 \`archives\` 文件夹的页面
+ if (filePathRelative.startsWith('archives/')) return false
+
+ // 舍弃那些没有使用默认布局的页面
+ if (frontmatter.home || frontmatter.layout) return false
+
+ return true
+ },
+
+ getInfo: ({ frontmatter, git = {}, data = {} }) => {
+ // 获取页面信息
+ const info: Record<string, any> = {
+ author: frontmatter.author || '',
+ categories: frontmatter.categories || [],
+ date: frontmatter.date || git.createdTime || null,
+ tags: frontmatter.tags || [],
+ excerpt: data.excerpt || '',
+ }
+
+ return info
+ },
+ }),
+ // 其他插件 ...
+ ],
+}
+基本上，你的博客中需要两种“类型”:
类别:
“类别”是用文章的标签 (或类别) 对它们进行分组。
例如，每篇文章可能都有对应的“分类”和“标签”。
类型:
“类型”是过滤不同条件的文章。
例如，你的帖子中可能有日记或笔记。当帖子带有写作日期信息时，它可以称为“时间线项目”。
了解这两种类型的描述后，你可以设置 category 和 type 选项，它们都接受一个数组，每个元素代表一个配置。
让我们从此处 2 个例子开始。
假设你想为每篇文章设置标签，并且你正在通过 frontmatter.tag 设置它们。同时，你想要在 /tag/ 中使用 TagMap 布局的标签页面，并在/tag/标签名称 中使用 TagList 布局对标签按名称进行分组，你可能需要这样的配置:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // 其他配置 ...
+ category: [
+ {
+ key: 'tag',
+ getter: ({ frontmatter }) => frontmatter.tag || [],
+ path: '/tag/',
+ layout: 'TagMap',
+ frontmatter: () => ({ title: '标签页' }),
+ itemPath: '/tag/:name/',
+ itemLayout: 'TagList',
+ itemFrontmatter: (name) => ({ title: \`\${name}标签\` }),
+ },
+ ],
+ }),
+ // 其他插件 ...
+ ],
+}
+此外，你可能希望为你的一些文章加注星标，并将其展示给访问者。当你在 frontmatter 中设置 star: true 来标记它们时，你可能需要这样的配置来在 /star/ 路径中以 StarList 布局显示它们:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // 其他配置 ...
+ type: [
+ {
+ key: 'star',
+ filter: ({ frontmatter }) => frontmatter.star,
+ path: '/star/',
+ layout: 'StarList',
+ frontmatter: () => ({ title: '星标文章' }),
+ },
+ ],
+ }),
+ // 其他插件 ...
+ ],
+}
+当生成每个页面时，插件将在 frontmatter.blog 中设置如下信息
interface BlogFrontmatterOptions {
+ /** 当前页面的类型 */
+ type: 'category' | 'type'
+ /** 在当前分类或类别下全局唯一的 key */
+ key: string
+ /**
+ * 当前的分类名称
+ *
+ * @description 仅在分类子项目页面中可用
+ */
+ name?: string
+}
+所以你可以直接调用 useBlogCategory() 和 useBlogType()，结果将是当前路由绑定的类别或类型。
此外，你可以通过传递所需的 key 作为参数，来将获得绑定到该 key 的信息。
对于上方的 Node 配置而言，你可以在客户端通过如下方式获取 tag 和 star 的信息:
TagMap 布局:
<template>
+ <div>
+ <h1>Tag page</h1>
+ <ul>
+ <li v-for="({ items, path }, name) in categoryMap.map">
+ <RouteLink :key="name" :to="path" class="category">
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </li>
+ </ul>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+TagList 布局:
<template>
+ <div>
+ <h1>Tag page</h1>
+ <div class="category-wrapper">
+ <RouteLink
+ v-for="({ items, path }, name) in categoryMap.map"
+ :key="name"
+ :to="path"
+ class="category"
+ >
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </div>
+ <div class="article-wrapper" v-if="categoryMap.currentItems">
+ <div v-if="!categoryMap.currentItems.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in categoryMap.currentItems"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline
+ ? \`\${new Date(info.date).toLocaleDateString()}: \`
+ : '') + info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author"
+ >Author: {{ info.author }}</span
+ >
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag"
+ >Tag: {{ info.tag.join(', ') }}</span
+ >
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+StarList 布局:
<template>
+ <div class="article-wrapper" v-if="stars.items">
+ <div v-if="!stars.items.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in stars.items"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline ? \`\${new Date(info.date).toLocaleDateString()}: \` : '') +
+ info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author">Author: {{ info.author }}</span>
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag">Tag: {{ info.tag.join(', ') }}</span>
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogType } from '@vuepress/plugin-blog/client'
+
+import ArticleList from '../components/ArticleList.vue'
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+
+const stars = useBlogType('star')
+</script>
+该插件添加了原生多语言支持，因此你的设置将自动应用于每种语言。
例如，如果用户进行了以下 locales 配置，并且你正在设置上面的“star”示例:
export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+}
+那么 /zh/star/ 和 /star/ 都将可用，并且只会显示对应语言下的文章。
这个插件提供了一个内置的摘要生成器，可以通过将 excerpt 选项设置为 true 来启用。
摘要介绍
摘要是一个 HTML 片段，被用于在博客列表中显示文章的简短描述，所以摘要有如下限制:
isCustomElement 选项。.vuepress/public 的绝对路径或完整路径以确保它们可以在其他地址被访问。摘要生成器将尝试从 Frontmatter 内容中找到有效的摘要分隔符，如果找到，它将使用分隔符之前的内容，分隔符默认为 <!-- more -->，并且你可以通过 excerptSeparator 选项来自定义它。
如果找不到有效的分隔符，它将从 Markdown 文件的开头开始解析内容，直到长度达到预设值时停止。该值默认为 300，你可以通过设置 excerptLength 选项来自定义它。
要选择哪个页面应该生成摘要，你可以使用 excerptFilter 选项。
示例
通常，如果用户设置了 frontmatter.description，你可能希望使用它们，因此如果 frontmatter.description 不为空，你可以让过滤器函数返回 false。
Make your VuePress site a Progressive Web Application (PWA)[1].
',3),u={href:"https://developers.google.com/web/tools/workbox/modules/workbox-build",target:"_blank",rel:"noopener noreferrer"},f={href:"https://github.com/yyx990803/register-service-worker",target:"_blank",rel:"noopener noreferrer"},g={class:"custom-container warning"},y=e("p",{class:"custom-container-title"},"WARNING",-1),m=n(`A PWA uses a Service Worker [2] (SW for short) to cache and proxy site content.
To make your website fully compliant with PWA, a Web app manifests [3] file is needed, and your pwa should satisfy the installability [4] specification.
You can set manifest option to customize the manifest file, or provide a manifest.webmanifest or manifest.json in public folder. The former has higher priority.
The plugin will automatically generate manifest.webmanifest for you and add manifest link declaration in each page, while you should still at least set a valid icon through manifest.icons or other icon related options in the PWA plugin.
WARNING
The installability [4:1] specification requires at least one valid icon to be declared in the manifest.
So if you do not configure manifest.icons, visitors can only enjoy the offline accessibility brought by the Service Worker cache, while cannot install your site as a PWA.
Besides the plugin does not process anything in the manifest by default, but outputs them as-is. This means that if you plan to deploy to a subdirectory, you should append the URL prefix to manifest Urls yourself. If everything you need is all under base directory, you can set appendBase: true in plugin options to let the plugin append base to any links in manifest.
To better control what the Service Worker can pre-cache, the plugin provides related options for cache control.
By default, the plugin will pre-cache all js css files, and only homepage and 404 html are cached. The plugin will also cache font files (woff, woff2, eot, ttf, otf) and SVG icons.
If your site has only a few important images, and want them displayed in offline mode, you can cache site images by setting cacheImage: true .
We recognize images by file extension. Any files ending with .png, .jpg, .jpeg, .gif, .bmp, .webp will be regarded as images.
If you have small sites, and would like to make document fully offline available, you can set cacheHTML to true to cache all HTML files.
Why only home and 404 page been cached by default?
Though VuePress generates HTML files through SSG[5] for all pages, these files are mainly used for SEO[6] and allow you to directly configure the backend without SPA[7] Visit any link.
VuePress is essentially an SPA. This means that you only need to cache the home page and enter from the home page to access all pages normally. Therefore, not caching other HTML by default can effectively reduce the cache size (40% smaller in size) and speed up the SW update speed.
But this also has the disadvantage. If the user enters the site directly from a non-home page, the HTML file for the first page still needs to be loaded from the internet. Also, in offline environment, users can only enter through the homepage and then navigate to the corresponding page by themselves. If they directly access a link, an inaccessible prompt will appear.
To prevent large files from being included in the pre-cache list, any files > 2 MB or images > 1 MB will be omitted. You can customize these limits with maxSize and maxImageSize options (in KB unit).
We provide the update option to control how users receive updates.
The default value of the update option is "available", which means that when new content available, the new SW will be installed and its resources will be fetched silently in the background. A pop-up window appears once the new SW is ready, and users can choose whether to refresh immediately to view new content. This means users are reading old content before a new SW is ready.
If your project is still in building stage, and you want to alert the user that he may be reading outdated content, you can set this to "hint". This allows users to be notified that new content has been published within seconds after visiting docs. But the negative effect of this is that if the user chooses to update before the new SW is ready, he will need to get all the resources of the page from the internet before the new SW installs and controls the page.
If your docs are stable, or you're hosting a blog and don't care much about users receiving the latest version right away, you can set this to "disabled", which means that the new SW will be installed completely silently in the background and start waiting, when all pages controlled by old SW are all closed, the new SW will start to take control and provide users with new content during next visit. This setting can prevent users from being disturbed during the visit.
To speed up user access under weak or no network conditions through SW, but also want users to always access new content, you can set this option to "force". This means any old SW will be removed as soon as a new SW is detected, and all pages are refreshed to ensure the user is browsing the latest content. The biggest disadvantage is that all users will experience unexpected sudden refresh within seconds after reentering an updated site.
When new content is detected (new SW detected), a update found popup appears; and when the new content is ready, an update ready popup appears.
If you are not satisfied with the default popup content, you can use your own component. Import PwaFoundPopup or PwaReadyPopup from @vuepress/plugin-pwa/client and use its slot to customize the popup content, then pass the component path to foundComponent or readyComponent option:
<script setup lang="ts">
+import { PwaFoundPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaFoundPopup v-slot="{ found, refresh }">
+ <div v-if="found">
+ New content is found.
+ <button @click="refresh">Refresh</button>
+ </div>
+ </PwaFoundPopup>
+</template>
+<script setup lang="ts">
+import { PwaReadyPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaReadyPopup v-slot="{ isReady, reload }">
+ <div v-if="isReady">
+ New content is ready.
+ <button @click="reload">Apply</button>
+ </div>
+ </PwaReadyPopup>
+</template>
+Service Worker Introduction
The Service Worker will get and cache all the files registered in it during the registration process.
After the registration complete, the Service Worker is activated, and starts to proxy and control all your requests.
Whenever you want to initiate an access request through the browser, the Service Worker will check whether it exists in its own cache list, if it exists, it will directly return the cached result, otherwise it will call its own fetch method to get it. You can use a custom fetch method to fully control the result of the request for resources in the web page, such as providing a fallback web page when offline.
Every time the user reopens the site, the Service Worker will request to the link when it was registered. If a new version of Service Worker is detected, it will update itself and start caching the list of resources registered in the new Service Worker . After the content update is successfully obtained, the Service Worker will trigger the update event. The user can be notified through this event, for example, a pop-up window will be displayed in the lower right corner, prompting the user that new content is available and allowing the user to trigger an update.
Installable
To let the site be registered as a PWA, the site needs to successfully register a valid service worker by itself, and declare a valid manifest file with its link in meta tag.
The manifest file should contain at least name (or short_name) icons start_url.
On safari, the maximum cache size of the service worker is 50 MB. ↩︎ ↩︎
SSG: Static Site Generation, ↩︎
SEO: Search Engine Optimization. ↩︎
SPA: Single Page Application, most of them only have the homepage, and use history mode to handle routing instead of actually navigating between pages. ↩︎
import { commentPlugin } from 'vuepress-plugin-comment2'
+
+// .vuepress/config.ts
+export default {
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo
+
+ // other options here
+ // ...
+ }),
+ ],
+}
+import { defineClientConfig } from 'vuepress/client'
+import {
+ defineArtalkConfig,
+ // defineGiscusConfig,
+ // defineTwikooConfig,
+ // defineWalineConfig,
+} from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+But here are some limitations you should remember:
`,5),y=e("p",null,[e("code",null,"provider"),n(", locales and other resource related option must be set in plugin options.")],-1),f=e("p",null,"To ensure tree-shaking works, we must optimize entries at node so that bundler can understand which resource should be included in the final bundle.",-1),b=e("p",null,"Options which can not be serialized to JSON must be set in client config.",-1),D=e("p",null,"Options that receives function values can not be set in plugin options, as plugins are running under Node.js environment, so we can not pass these values and their contexts to browser.",-1),C=a('This plugin globally registers a component <CommentService />.
alias and layout slots to insert the component. We recommended you to insert the comment component (<CommentService />) after the <PageNav /> component, and the current page is a demo with default theme.By default, <CommentService /> component is enabled globally, and you can use comment option in both plugin options and page frontmatter to control it.
comment: false in page frontmatter.comment to false in the plugin options. Then you can set comment: true in page frontmatter to enable it locally.You can set commentID option in page frontmatter to customize comment ID, which is used to identify comment storage item to use for a page. By default it will be the path of the page, which means if you are deploying the site to multiple places, page with same content across sites will share the same comment data.
"Artalk" | "Giscus" | "Twikoo" | "Waline" | "None""None"booleantrue插件开箱即用，在不做任何配置的情况下，会尽可能通过页面内容，提取对应的信息补全 OGP 与 JSON-LD 所需的必要标签。
默认情况下，插件会读取站点配置、主题配置与页面的 frontmatter 来尽可能自动生成。诸如站点名称，页面标题，页面类型，写作日期，最后更新日期，文章标签均会自动生成。
| 属性名称 | 值 |
|---|---|
og:url | options.hostname + path |
og:site_name | siteConfig.title |
og:title | page.title |
og:description | page.frontmatter.description || 自动生成 (当插件选项中的 autoDescription 为 true 时) |
og:type | "article" |
og:image | page.frontmatter.banner || page.frontmatter.cover || 页面的第一张图片|| 插件选项的 fallbackImage |
og:updated_time | page.git.updatedTime |
og:locale | page.lang |
og:locale:alternate | siteData.locales 包含的其他语言 |
twitter:card | "summary_large_image" (仅在找到图片时) |
twitter:image:alt | page.title (仅在找到图片时) |
article:author | page.frontmatter.author || options.author |
article:tag | page.frontmatter.tags || page.frontmatter.tag |
article:published_time | page.frontmatter.date || page.git.createdTime |
article:modified_time | page.git.updatedTime |
| 属性名 | 值 |
|---|---|
@context | "https://schema.org" |
@type | "NewsArticle" |
headline | page.title |
image | 页面中的图片|| options.hostname + page.frontmatter.image |
datePublished | page.frontmatter.date || page.git.createdTime |
dateModified | page.git.updatedTime |
author | page.frontmatter.author || options.author |
你可以在页面的 frontmatter 中配置 head 选项，自主添加特定标签到页面 <head> 以增强 SEO。
如:
---
+head:
+ - - meta
+ - name: keywords
+ content: SEO plugin
+---
+会自动注入 <meta name="keywords" content="SEO plugin" />。
本插件也支持你完全控制生成逻辑。
对于大多数页面，基本只有文章和网页两种类型，所以插件提供了 isArticle 选项让你提供辨别文章的逻辑。
选项接受一个 (page: Page) => boolean 格式的函数，默认情况下从 Markdown 文件生成的非主页页面都会被视为文章。
提示
如果某个网页的确符合图书、音乐之类的“冷门”类型，你可以通过设置下方三个选项处理它们。
你可以使用插件选项的 ogp 传入一个函数来按照你的需要修改默认 OGP 对象并返回。
function ogp(
+ /** 插件推断的 OGP 信息 */
+ ogp: SeoContent,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+比如你在使用某个第三方主题，并按照主题要求为每篇文章在 Front Matter 中设置了 banner，那你可以传入这样的 ogp:
seoPlugin({
+ ogp: (ogp, page) => ({
+ ...ogp,
+ 'og:image': page.frontmatter.banner || ogp['og:image'],
+ }),
+})
+同 OGP，你可以使用插件选项的 jsonLd 传入一个函数来按照你的需要修改默认 JSON-LD 对象并返回。
function jsonLd(
+ /** 由插件推断出的 JSON-LD 对象 */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+如果你将内容部署到不同的站点，或不同 URL 下的相同内容，你可能需要设置 canonical 选项为你的页面提供 “规范链接”。 你可以设置一个字符串，这样它会附加在页面路由链接之前，或者添加一个自定义函数 (page: Page) => string | null 返回规范链接。
例子
如果你的站点部署在 example.com 的 docs 文件夹下，但同时在下列网址中可用:
http://example.com/docs/xxxhttps://example.com/docs/xxxhttp://www.example.com/docs/xxxhttps://www.example.com/docs/xxx (首选)要让搜索引擎结果始终是首选，你可能需要将 canonical 设置为 https://www.example.com/docs/，以便搜索引擎知道首选第四个 URL 作为索引结果。
有些时候你可能需要符合其他协议或按照其他搜索引擎提供的格式提供对应的 SEO 标签，此时你可以使用 customHead 选项，其类型为:
function customHead(
+ /** head 标签配置 */
+ head: HeadConfig[],
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+你应该直接修改传入的 head 参数。
搜索引擎优化 (Search Engine Optimization)，是一种透过了解搜索引擎的运作规则来调整网站，以及提高目的网站在有关搜索引擎内排名的方式。由于不少研究发现，搜索引擎的用户往往只会留意搜索结果最前面的几个条目，所以不少网站都希望透过各种形式来影响搜索引擎的排序，让自己的网站可以有优秀的搜索排名。 所谓“针对搜索引擎作最优化的处理”，是指为了要让网站更容易被搜索引擎接受。搜索引擎会将网站彼此间的内容做一些相关性的资料比对，然后再由浏览器将这些内容以最快速且接近最完整的方式，呈现给搜索者。搜索引擎优化就是通过搜索引擎的规则进行优化，为用户打造更好的用户体验，最终的目的就是做好用户体验。
npm i -D @vuepress/plugin-seo@next
+import { seoPlugin } from '@vuepress/plugin-seo'
+
+export default {
+ plugins: [
+ seoPlugin({
+ // 选项
+ }),
+ ],
+}
+npm i -D @vuepress/plugin-sitemap@next
+import { sitemapPlugin } from '@vuepress/plugin-sitemap'
+
+export default {
+ plugins: [
+ sitemapPlugin({
+ // 选项
+ }),
+ ],
+}
+npm i -D @vuepress/plugin-feed@next
+import { feedPlugin } from '@vuepress/plugin-feed'
+
+export default {
+ plugins: [
+ feedPlugin({
+ // options
+ }),
+ ],
+}
+npm i -D @vuepress/plugin-blog@next
+import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ plugins: [
+ blogPlugin({
+ // options
+ }),
+ ],
+}
+A safe comment system with backend.
npm i -D @waline/client
+Enter the app, then select Settings > App Keys at the left bottom corner. You will see APP ID, APP Key and Master Key of your app. We will use them later
Click the dark button above, it will redirect you to vercel to deploy with waline template.
TIP
If you haven't logged in, we recommend you to sign in with GitHub.
Input your Vercel project name then click Create.
Repo which named you input before will be created and initialized automatically base on waline example template by Vercel.
After one minute or two, vercel should finish the deployment. Click Go to Dashboard button to redirect to your application dashboard.
Click Settings menu on the top, and Environment Variables button on the side to go to environment variables setting page. Then set LEAN_ID, LEAN_KEY and LEAN_MASTER_KEY. The variables' value should be the ones you got in the previous step. APP ID is the value of LEAN_ID, and APP Key to LEAN_KEY, Master Key to LEAN_MASTER_KEY.
To let your environment variables setting active, you need redeploy your application. Click Deployments menu on the top and find the latest deployment at the top of list, click Redeploy button in the right dropdown menu.
If everything is ok, vercel will redirect to Overview page to start redeployment. Wait a moment the STATUS will change to Ready. Now you can click Visit to visit the site. This link is your server address.
Click Settings - Domains to go to domain setting page.
Input domain you want to assign and click Add button.
Add a new CNAME record in your domain service server.
| Type | Name | Value |
|---|---|---|
| CNAME | example | cname.vercel-dns.com |
You can use your own domain to visit waline comment system after go into effect. 🎉
Set provider: "Waline" in the plugin options, and set serverURL as the link obtained in the previous step.
Then, place the <CommentService> component at a suitable location in your site (usually at the bottom of the page), you will be able to see the comment box.
一个有后端的安全评论系统。
npm i -D @waline/client
+进入应用，选择左下角的 设置 > 应用 Key。你可以看到你的 APP ID,APP Key 和 Master Key。请记录它们，以便后续使用。
设置 > 域名绑定 > API 访问域名 > 绑定新域名 > 输入域名 > 确定。点击上方按钮，跳转至 Vercel 进行 Server 端部署。
::: note
如果你未登录的话，Vercel 会让你注册或登录，请使用 GitHub 账户进行快捷登录。
:::
输入一个你喜欢的 Vercel 项目名称并点击 Create 继续:
此时 Vercel 会基于 Waline 模板帮助你新建并初始化仓库，仓库名为你之前输入的项目名。
一两分钟后，满屏的烟花会庆祝你部署成功。此时点击 Go to Dashboard 可以跳转到应用的控制台。
点击顶部的 Settings - Environment Variables 进入环境变量配置页，并配置三个环境变量 LEAN_ID, LEAN_KEY 和 LEAN_MASTER_KEY 。它们的值分别对应上一步在 LeanCloud 中获得的 APP ID, APP KEY, Master Key。
::: note
如果你使用 LeanCloud 国内版，请额外配置 LEAN_SERVER 环境变量，值为你绑定好的域名。
:::
环境变量配置完成之后点击顶部的 Deployments 点击顶部最新的一次部署右侧的 Redeploy 按钮进行重新部署。该步骤是为了让刚才设置的环境变量生效。
此时会跳转到 Overview 界面开始部署，等待片刻后 STATUS 会变成 Ready。此时请点击 Visit ，即可跳转到部署好的网站地址，此地址即为你的服务端地址。
点击顶部的 Settings - Domains 进入域名配置页
输入需要绑定的域名并点击 Add
在域名服务器商处添加新的 CNAME 解析记录
| Type | Name | Value |
|---|---|---|
| CNAME | example | cname.vercel-dns.com |
等待生效，你可以通过自己的域名来访问了🎉
在插件选项中设置 provider: "Waline"，同时设置服务端地址 serverURL 为上一步获取到的值。
此时，将 <CommentService> 组件放置在你网站中合适的位置 (通常是页面的底部)，即可使用 Waline 评论功能。
请配置 provider: "Giscus" 并将 data-repo, data-repo-id, data-category 和 data-category-id 作为插件选项传入 repo, repoId, category categoryId。
默认情况下，Giscus 使用 light 或 dark 主题 (基于夜间模式状态)。
::: info 夜间模式
为了能使 Giscus 应用正确的主题，你需要为 <CommentService /> 通过 darkmode 属性传入一个布尔值，代表当前是否开启夜间模式。
:::
如果你想在日间模式和夜间模式下自定义主题，你可以设置 lightTheme 和 darkTheme 选项，使用内置主题关键字或以 https:// 开头的自定义 css 链接。
npm i -D @vuepress/plugin-seo@next
+import { seoPlugin } from '@vuepress/plugin-seo'
+
+export default {
+ plugins: [
+ seoPlugin({
+ // options
+ }),
+ ],
+}
+npm i -D @vuepress/plugin-sitemap@next
+import { sitemapPlugin } from '@vuepress/plugin-sitemap'
+
+export default {
+ plugins: [
+ sitemapPlugin({
+ // options
+ }),
+ ],
+}
+npm i -D twikoo
+部署共有四种方式。
| 部署方式 | 描述 |
|---|---|
| 一键部署 | [不建议] 虽然方便，但是仅支持按量计费环境——也就是说，一键部署的环境，当免费资源用尽后，将会产生费用。且按量计费环境无法切换为包年包月环境。免费额度数据库读操作数只有 500 次 / 天，无法支撑 Twikoo 的运行需求。 |
| 手动部署 | [建议] 手动部署到腾讯云云开发环境，在中国大陆访问速度较快。由于基础版 1 已从 0 元涨价至 6.9 元 / 月，需要付费购买环境才能部署。 |
| 命令行部署 | [不建议] 仅针对有 Node.js 经验的开发者。 |
| Vercel 部署 | [建议] 适用于想要免费部署的用户，在中国大陆访问速度较慢。 |
提示
twikoo.init() 时额外指定环境 region: "ap-guangzhou"包年包月，套餐版本基础版 1，超出免费额度不会收费函数名称请填写 twikoo，创建方式请选择 空白函数，运行环境请选择 Nodejs 10.15，函数内存请选择 128MB，点击“下一步”
清空输入框中的示例代码，复制以下代码、粘贴到“函数代码”输入框中，点击“确定”
exports.main = require('twikoo-func').main
+创建完成后，点击“twikoo”进入云函数详情页，进入“函数代码”标签，点击“文件 - 新建文件”，输入 package.json，回车
复制以下代码、粘贴到代码框中，点击“保存并安装依赖”
{ "dependencies": { "twikoo-func": "1.5.0" } }
+克隆本仓库
git clone https://github.com/imaegoo/twikoo.git # 或 git clone https://e.coding.net/imaegoo/twikoo/twikoo.git
+cd twikoo
+安装依赖项
npm install -g yarn # 如 yarn 已安装，可以跳过此步
+yarn install
+授权云开发环境 (此命令会弹出浏览器要求授权，需在有图形界面的系统下进行)
yarn run login
+自动部署
yarn deploy -e 你的环境id
+npm i -D @vuepress/plugin-blog@next
+import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ plugins: [
+ blogPlugin({
+ // 选项
+ }),
+ ],
+}
+Install @vuepress/theme-default :
npm install @vuepress/theme-default@next
+import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ // set theme config here
+ }),
+}
+npm i -D @vuepress/plugin-comment@next
+import { commentPlugin } from '@vuepress/plugin-comment'
+
+export default {
+ plugins: [
+ commentPlugin({
+ // 选项
+ }),
+ ],
+}
+npm i -D @vuepress/plugin-comment@next
+import { commentPlugin } from '@vuepress/plugin-comment'
+
+export default {
+ plugins: [
+ commentPlugin({
+ // options
+ }),
+ ],
+}
+Artalk 是一款简洁的自托管评论系统，你可以在服务器上轻松部署并置入前端页面中。
来到你的博客，或是任意位置，放置 Artalk 评论框，让页面具备丰富的社会化功能。
npm i -D artalk
+提示
插件保留 el 选项在页面自行插入 Artalk。同时插件会自动根据 VuePress 信息为你自动设置 pageTitle, pageKey 和 site 选项。
为了能使 Artalk 应用正确的主题，你需要通过 darkmode 属性向 <CommentService /> 传入一个布尔值，代表当前是否开启夜间模式。
npm i -D @vuepress/plugin-feed@next
+import { feedPlugin } from '@vuepress/plugin-feed'
+
+export default {
+ plugins: [
+ feedPlugin({
+ // 选项
+ }),
+ ],
+}
+npm i -D @vuepress/plugin-pwa@next
+import { pwaPlugin } from '@vuepress/plugin-pwa'
+
+export default {
+ plugins: [
+ pwaPlugin({
+ // 选项
+ }),
+ ],
+}
+Artalk is a neat self-hosted commenting system that you can easily deploy on your server and put into your front-end page.
Come to your blog, or anywhere, place the Artalk comment box, so that the page has rich social functions.
npm i -D artalk
+TIP
The plugin retains the el option and inserts Artalk itself on the page. At the same time, the plugin will automatically set the pageTitle, pageKey and site options for you according to the VuePress information.
To let Artalk apply the correct theme, you need to pass a boolean value to <CommentService /> through darkmode prop, representing whether the dark mode is currently enabled.
安装默认主题：
npm i -D @vuepress/theme-default@next
+在配置文件中指定主题：
import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ // 在这里添加主题配置
+ }),
+}
+Please set provider: "Giscus" and pass data-repo, data-repo-id, data-category and data-category-id as plugin options as repo, repoId, category categoryId.
By default, the theme of Giscus is light or dark (based on darkmode status).
Darkmode
To let Giscus apply the correct theme, you need to pass a boolean value to <CommentService /> via darkmode property, indicating whether darkmode is currently enabled.
If you want to customize theme in lightmode and darkmode, you can set lightTheme and darkTheme option with a built-in theme keyword or a custom CSS link starting with https://.
npm i -D twikoo
+npm i -D @vuepress/plugin-pwa@next
+import { pwaPlugin } from '@vuepress/plugin-pwa'
+
+export default {
+ plugins: [
+ pwaPlugin({
+ // options
+ }),
+ ],
+}
+此插件将检查您的 markdown 文件中的死链接。
此插件已集成到默认主题中。
npm i -D @vuepress/plugin-links-check@next
+import { linksCheckPlugin } from '@vuepress/plugin-links-check'
+
+export default {
+ plugins: [
+ linksCheckPlugin({
+ // 选项
+ }),
+ ],
+}
+类型：boolean
默认值：true
详情：
是否在开发服务器中检查 markdown 中的死链接
类型：boolean | 'error'
默认值：true
详情：
是否在构建中检查 markdown 中的死链接。如果设置为 'error'，则构建将在存在死链接时失败。
类型：(string | RegExp)[] | ((link: string, isDev: boolean) => boolean)
详情：
应该从检查中排除的链接。您可以使用字符串或正则表达式的列表，或者返回布尔值的函数。
示例：
linksCheckPlugin({
+ exclude: [
+ // 通过字符串排除链接
+ '/exclude-link',
+ // 通过正则表达式排除链接
+ /\\/exclude-link-regex/,
+ ],
+
+ // 或者通过函数排除链接
+ exclude: (link, isDev) => {
+ if (isDev) {
+ return link.startsWith('/exclude-link-dev')
+ }
+ return link.startsWith('/exclude-link-build')
+ },
+})
+This plugin will check dead links in your markdown files.
This plugin has been integrated into the default theme.
npm i -D @vuepress/plugin-links-check@next
+import { linksCheckPlugin } from '@vuepress/plugin-links-check'
+
+export default {
+ plugins: [
+ linksCheckPlugin({
+ // options
+ }),
+ ],
+}
+Type: boolean
Default: true
Details:
Whether check dead links in markdown in devServer
Type: boolean | 'error'
Default: true
Details:
Whether check dead links in markdown in build. If set to 'error', the build will fail if there are dead links.
Type: (string | RegExp)[] | ((link: string, isDev: boolean) => boolean)
Details:
The links that should be excluded from checking. You can use a list of strings or regular expressions, or a function that returns a boolean.
Example:
linksCheckPlugin({
+ exclude: [
+ // exclude links by string
+ '/exclude-link',
+ // exclude links by regex
+ /\\/exclude-link-regex/,
+ ],
+
+ // or exclude links by function
+ exclude: (link, isDev) => {
+ if (isDev) {
+ return link.startsWith('/exclude-link-dev')
+ }
+ return link.startsWith('/exclude-link-build')
+ },
+})
+类型： string
详情：
选择语言菜单 的 aria-label 属性。
它主要是为了站点的可访问性 (a11y) 。
export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+ theme: defaultTheme({
+ locales: {
+ '/': {
+ selectLanguageName: 'English',
+ },
+ '/zh/': {
+ selectLanguageName: '简体中文',
+ },
+ },
+ }),
+}
+类型：null | string
详情：
导航栏中主导航 aria-label 属性的值。
类型：null | string
详情：
下一页/上一页导航 aria-label 属性的值
类型： string
默认值： 'Edit this page'
详情：
编辑此页 链接的文字。
类型： string
默认值： 'Last Updated'
详情：
最近更新时间戳 标签的文字。
类型： string
默认值： 'Contributors'
详情：
贡献者列表 标签的文字。
类型： string[]
默认值： ['Not Found']
详情：
404 页面的提示信息。
当用户进入 404 页面时，会从数组中随机选取一条信息进行展示。
类型： string
默认值： 'Back to home'
详情：
404 页面中 返回首页 链接的文字。
类型： string
默认值： 'toggle sidebar'
详情：
切换侧边栏按钮的标题文字。
它主要是为了站点的可访问性 (a11y) 。
类型： string
默认值： 'Prev'
详情：
上一页按钮的文字。
类型： string
默认值： 'Next'
详情：
下一页按钮的文字。
Type: string
Details:
Specify the aria-label attribute of the select language menu.
This is mainly for a11y purpose.
export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+ theme: defaultTheme({
+ locales: {
+ '/': {
+ selectLanguageName: 'English',
+ },
+ '/zh/': {
+ selectLanguageName: '简体中文',
+ },
+ },
+ }),
+}
+Type: null | string
Details:
aria-label value for main navigation in navbar.
Type: null | string
Details:
aria-label value for next/previous page navigation.
Type: string
Default: 'Edit this page'
Details:
Specify the text of the edit this page link.
Type: string
Default: 'Last Updated'
Details:
Specify the text of the last updated timestamp label.
Type: string
Default: 'Contributors'
Details:
Specify the text of the contributors list label.
Type: string[]
Default: ['Not Found']
Details:
Specify the messages of the 404 page.
The message will be randomly picked from the array when users enter the 404 page.
Type: string
Default: 'Back to home'
Details:
Specify the text of the back to home link in the 404 page.
Type: string
Default: 'toggle sidebar'
Details:
Title text for sidebar toggle button.
This is mainly for a11y purpose.
Type: string
Default: 'Prev'
Details:
Text for the previous page navigation button.
Type: string
Default: 'Next'
Details:
Text for the next page navigation button.
使用：
::: <type> [title]
+[content]
+:::
+type 是必需的， title 和 content 是可选的。
支持的 type 有：
输入
::: tip
+这是一个提示
+:::
+
+::: warning
+这是一个警告
+:::
+
+::: danger
+这是一个危险警告
+:::
+
+::: details
+这是一个 details 标签
+:::
+输出
提示
这是一个提示
注意
这是一个警告
警告
这是一个危险警告
这是一个 details 标签
输入
::: danger STOP
+危险区域，禁止通行
+:::
+
+::: details 点击查看代码
+
+\`\`\`ts
+console.log('你好，VuePress！')
+\`\`\`
+
+:::
+输出
STOP
危险区域，禁止通行
console.log('你好，VuePress！')
+输入
:::: code-group
+::: code-group-item FOO
+
+\`\`\`ts
+const foo = 'foo'
+\`\`\`
+
+:::
+
+::: code-group-item BAR
+
+\`\`\`ts
+const bar = 'bar'
+\`\`\`
+
+:::
+::::
+输出
`,17),E=s("div",{class:"language-typescript","data-ext":"ts","data-title":"ts"},[s("pre",{class:"shiki dark-plus",style:{"background-color":"#1E1E1E",color:"#D4D4D4"},tabindex:"0"},[s("code",null,[s("span",{class:"line"},[s("span",{style:{color:"#569CD6"}},"const"),s("span",{style:{color:"#4FC1FF"}}," foo"),s("span",{style:{color:"#D4D4D4"}}," = "),s("span",{style:{color:"#CE9178"}},"'foo'")]),e(` +`),s("span",{class:"line"})])])],-1),x=s("div",{class:"language-typescript","data-ext":"ts","data-title":"ts"},[s("pre",{class:"shiki dark-plus",style:{"background-color":"#1E1E1E",color:"#D4D4D4"},tabindex:"0"},[s("code",null,[s("span",{class:"line"},[s("span",{style:{color:"#569CD6"}},"const"),s("span",{style:{color:"#4FC1FF"}}," bar"),s("span",{style:{color:"#D4D4D4"}}," = "),s("span",{style:{color:"#CE9178"}},"'bar'")]),e(` +`),s("span",{class:"line"})])])],-1);function w(F,z){const i=l("NpmBadge"),o=l("RouteLink"),t=l("CodeGroupItem"),c=l("CodeGroup");return d(),u("div",null,[m,n(i,{package:"@vuepress/theme-default"}),v,s("ul",null,[s("li",null,[y,s("ul",null,[h,b,g,_,s("li",null,[n(o,{to:"/zh/themes/default/components.html#codegroup"},{default:a(()=>[e("CodeGroup")]),_:1}),e(" 和 "),n(o,{to:"/zh/themes/default/components.html#codegroupitem"},{default:a(()=>[e("CodeGroupItem")]),_:1}),e(" 的别名： "),k])])]),C]),f,n(c,null,{default:a(()=>[n(t,{title:"FOO"},{default:a(()=>[E]),_:1}),n(t,{title:"BAR"},{default:a(()=>[x]),_:1})]),_:1})])}const V=r(D,[["render",w],["__file","markdown.html.vue"]]),P=JSON.parse('{"path":"/zh/themes/default/markdown.html","title":"Markdown","lang":"zh-CN","frontmatter":{"description":"Markdown","head":[["link",{"rel":"alternate","hreflang":"en-us","href":"https://ecosystem.vuejs.press/ecosystem/themes/default/markdown.html"}],["meta",{"property":"og:url","content":"https://ecosystem.vuejs.press/ecosystem/zh/themes/default/markdown.html"}],["meta",{"property":"og:site_name","content":"VuePress 生态系统"}],["meta",{"property":"og:title","content":"Markdown"}],["meta",{"property":"og:description","content":"Markdown"}],["meta",{"property":"og:type","content":"article"}],["meta",{"property":"og:locale","content":"zh-CN"}],["meta",{"property":"og:locale:alternate","content":"en-US"}],["meta",{"property":"og:updated_time","content":"2024-01-30T09:08:43.000Z"}],["meta",{"property":"article:modified_time","content":"2024-01-30T09:08:43.000Z"}],["script",{"type":"application/ld+json"},"{\\"@context\\":\\"https://schema.org\\",\\"@type\\":\\"Article\\",\\"headline\\":\\"Markdown\\",\\"image\\":[\\"\\"],\\"dateModified\\":\\"2024-01-30T09:08:43.000Z\\",\\"author\\":[]}"],["link",{"rel":"alternate","type":"application/atom+xml","href":"https://ecosystem.vuejs.press/ecosystem/zh/atom.xml","title":"VuePress 生态系统 Atom Feed"}],["link",{"rel":"alternate","type":"application/json","href":"https://ecosystem.vuejs.press/ecosystem/zh/feed.json","title":"VuePress 生态系统 JSON Feed"}],["link",{"rel":"alternate","type":"application/rss+xml","href":"https://ecosystem.vuejs.press/ecosystem/zh/rss.xml","title":"VuePress 生态系统 RSS Feed"}]]},"headers":[{"level":2,"title":"自定义容器","slug":"自定义容器","link":"#自定义容器","children":[]}],"git":{"updatedTime":1706605723000,"contributors":[{"name":"Mr.Hope","email":"mister-hope@outlook.com","commits":1}]},"autoDesc":true,"filePathRelative":"zh/themes/default/markdown.md"}');export{V as comp,P as data}; diff --git a/assets/markdown.html-pSTb5Ufr.js b/assets/markdown.html-pSTb5Ufr.js new file mode 100644 index 0000000000..1427f7eda8 --- /dev/null +++ b/assets/markdown.html-pSTb5Ufr.js @@ -0,0 +1,50 @@ +import{_ as r,r as l,o as d,c as u,a as e,b as s,d as n,w as a,e as i}from"./app-3y2wReKQ.js";const m={},D=s("h1",{id:"markdown",tabindex:"-1"},[s("a",{class:"header-anchor",href:"#markdown"},[s("span",null,"Markdown")])],-1),v=s("h2",{id:"custom-containers",tabindex:"-1"},[s("a",{class:"header-anchor",href:"#custom-containers"},[s("span",null,"Custom Containers")])],-1),y=i(`Usage:
::: <type> [title]
+[content]
+:::
+The type is required, and the title and content are optional.
Supported type :
Input
::: tip
+This is a tip
+:::
+
+::: warning
+This is a warning
+:::
+
+::: danger
+This is a dangerous warning
+:::
+
+::: details
+This is a details block
+:::
+Output
TIP
This is a tip
WARNING
This is a warning
DANGER
This is a dangerous warning
This is a details block
Input
::: danger STOP
+Danger zone, do not proceed
+:::
+
+::: details Click me to view the code
+
+\`\`\`ts
+console.log('Hello, VuePress!')
+\`\`\`
+
+:::
+Output
STOP
Danger zone, do not proceed
console.log('Hello, VuePress!')
+Input
:::: code-group
+::: code-group-item FOO
+
+\`\`\`ts
+const foo = 'foo'
+\`\`\`
+
+:::
+
+::: code-group-item BAR
+
+\`\`\`ts
+const bar = 'bar'
+\`\`\`
+
+:::
+::::
+Output
`,17),f=s("div",{class:"language-typescript","data-ext":"ts","data-title":"ts"},[s("pre",{class:"shiki dark-plus",style:{"background-color":"#1E1E1E",color:"#D4D4D4"},tabindex:"0"},[s("code",null,[s("span",{class:"line"},[s("span",{style:{color:"#569CD6"}},"const"),s("span",{style:{color:"#4FC1FF"}}," foo"),s("span",{style:{color:"#D4D4D4"}}," = "),s("span",{style:{color:"#CE9178"}},"'foo'")]),n(` +`),s("span",{class:"line"})])])],-1),w=s("div",{class:"language-typescript","data-ext":"ts","data-title":"ts"},[s("pre",{class:"shiki dark-plus",style:{"background-color":"#1E1E1E",color:"#D4D4D4"},tabindex:"0"},[s("code",null,[s("span",{class:"line"},[s("span",{style:{color:"#569CD6"}},"const"),s("span",{style:{color:"#4FC1FF"}}," bar"),s("span",{style:{color:"#D4D4D4"}}," = "),s("span",{style:{color:"#CE9178"}},"'bar'")]),n(` +`),s("span",{class:"line"})])])],-1);function x(F,T){const p=l("NpmBadge"),o=l("RouteLink"),t=l("CodeGroupItem"),c=l("CodeGroup");return d(),u("div",null,[D,e(p,{package:"@vuepress/theme-default"}),v,s("ul",null,[s("li",null,[y,s("ul",null,[h,g,b,k,s("li",null,[n("Alias of "),e(o,{to:"/themes/default/components.html#codegroup"},{default:a(()=>[n("CodeGroup")]),_:1}),n(" and "),e(o,{to:"/themes/default/components.html#codegroupitem"},{default:a(()=>[n("CodeGroupItem")]),_:1}),n(": "),_])])]),C]),E,e(c,null,{default:a(()=>[e(t,{title:"FOO"},{default:a(()=>[f]),_:1}),e(t,{title:"BAR"},{default:a(()=>[w]),_:1})]),_:1})])}const A=r(m,[["render",x],["__file","markdown.html.vue"]]),O=JSON.parse('{"path":"/themes/default/markdown.html","title":"Markdown","lang":"en-US","frontmatter":{"description":"Markdown","head":[["link",{"rel":"alternate","hreflang":"zh-cn","href":"https://ecosystem.vuejs.press/ecosystem/zh/themes/default/markdown.html"}],["meta",{"property":"og:url","content":"https://ecosystem.vuejs.press/ecosystem/themes/default/markdown.html"}],["meta",{"property":"og:site_name","content":"VuePress Ecosystem"}],["meta",{"property":"og:title","content":"Markdown"}],["meta",{"property":"og:description","content":"Markdown"}],["meta",{"property":"og:type","content":"article"}],["meta",{"property":"og:locale","content":"en-US"}],["meta",{"property":"og:locale:alternate","content":"zh-CN"}],["meta",{"property":"og:updated_time","content":"2024-01-30T09:08:43.000Z"}],["meta",{"property":"article:modified_time","content":"2024-01-30T09:08:43.000Z"}],["script",{"type":"application/ld+json"},"{\\"@context\\":\\"https://schema.org\\",\\"@type\\":\\"Article\\",\\"headline\\":\\"Markdown\\",\\"image\\":[\\"\\"],\\"dateModified\\":\\"2024-01-30T09:08:43.000Z\\",\\"author\\":[]}"],["link",{"rel":"alternate","type":"application/atom+xml","href":"https://ecosystem.vuejs.press/ecosystem/atom.xml","title":"VuePress Ecosystem Atom Feed"}],["link",{"rel":"alternate","type":"application/json","href":"https://ecosystem.vuejs.press/ecosystem/feed.json","title":"VuePress Ecosystem JSON Feed"}],["link",{"rel":"alternate","type":"application/rss+xml","href":"https://ecosystem.vuejs.press/ecosystem/rss.xml","title":"VuePress Ecosystem RSS Feed"}]]},"headers":[{"level":2,"title":"Custom Containers","slug":"custom-containers","link":"#custom-containers","children":[]}],"git":{"updatedTime":1706605723000,"contributors":[{"name":"Mr.Hope","email":"mister-hope@outlook.com","commits":1}]},"autoDesc":true,"filePathRelative":"themes/default/markdown.md"}');export{A as comp,O as data}; diff --git a/assets/medium-zoom.html-CHAkQyiv.js b/assets/medium-zoom.html-CHAkQyiv.js new file mode 100644 index 0000000000..2518751b6a --- /dev/null +++ b/assets/medium-zoom.html-CHAkQyiv.js @@ -0,0 +1,31 @@ +import{_ as t,r as a,o as i,c,a as n,b as s,d as e,e as o}from"./app-3y2wReKQ.js";const r={},d=s("h1",{id:"medium-zoom",tabindex:"-1"},[s("a",{class:"header-anchor",href:"#medium-zoom"},[s("span",null,"medium-zoom")])],-1),m={href:"https://github.com/francoischalifour/medium-zoom#readme",target:"_blank",rel:"noopener noreferrer"},u=o(`该插件已经集成到默认主题中。
npm i -D @vuepress/plugin-medium-zoom@next
+import { mediumZoomPlugin } from '@vuepress/plugin-medium-zoom'
+
+export default {
+ plugins: [
+ mediumZoomPlugin({
+ // 配置项
+ }),
+ ],
+}
+类型： string
默认值： ':not(a) > img'
详情：
可缩放的图片的选择器。
默认情况下，该插件会使 <a> 标签以外的所有图片都支持缩放。
类型： number
默认值： 500
详情：
以毫秒为单位的延迟。
在切换路由进入一个新页面时，该插件会在一定延迟后才使页面内的图片支持缩放。
你可以通过 zoomOptions 对大部分的缩放样式进行自定义，不过作为补充，该插件同样提供了一些 CSS 变量：
:root {
+ --medium-zoom-z-index: 100;
+ --medium-zoom-bg-color: #ffffff;
+ --medium-zoom-opacity: 1;
+}
+import { nextTick } from 'vue'
+import { useMediumZoom } from '@vuepress/plugin-medium-zoom/client'
+
+export default {
+ setup() {
+ const zoom = useMediumZoom()
+
+ // ... 进行了一些操作，在当前页面添加了新的图片
+
+ // 此时你可能需要手动调用 \`refresh\` 来让这些新图片支持缩放
+ nextTick(() => {
+ zoom.refresh()
+ })
+ },
+}
+This plugin has been integrated into the default theme.
npm i -D @vuepress/plugin-medium-zoom@next
+import { mediumZoomPlugin } from '@vuepress/plugin-medium-zoom'
+
+export default {
+ plugins: [
+ mediumZoomPlugin({
+ // options
+ }),
+ ],
+}
+Type: string
Default: ':not(a) > img'
Details:
Selector of zoomable images.
By default this plugin will make all images zoomable except those inside <a> tags.
Type: number
Default: 500
Details:
Delay in milliseconds.
After navigating to a new page, this plugin will make images zoomable with a delay.
You can customize most of the zoom styles via zoomOptions, while this plugin also provides some CSS variables for additional customization:
:root {
+ --medium-zoom-z-index: 100;
+ --medium-zoom-bg-color: #ffffff;
+ --medium-zoom-opacity: 1;
+}
+import { nextTick } from 'vue'
+import { useMediumZoom } from '@vuepress/plugin-medium-zoom/client'
+
+export default {
+ setup() {
+ const zoom = useMediumZoom()
+
+ // ... do something to add new images in current page
+
+ // then you may need to call \`refresh\` manually to make those new images zoomable
+ nextTick(() => {
+ zoom.refresh()
+ })
+ },
+}
+This plugin has been integrated into the default theme.
npm i -D @vuepress/plugin-nprogress@next
+import { nprogressPlugin } from '@vuepress/plugin-nprogress'
+
+export default {
+ plugins: [nprogressPlugin()],
+}
+You can customize the style of the progress bar via CSS variables:
:root {
+ --nprogress-color: #29d;
+ --nprogress-z-index: 1031;
+}
+该插件已经集成到默认主题中。
npm i -D @vuepress/plugin-nprogress@next
+import { nprogressPlugin } from '@vuepress/plugin-nprogress'
+
+export default {
+ plugins: [nprogressPlugin()],
+}
+你可以通过 CSS 变量来自定义进度条的样式：
:root {
+ --nprogress-color: #29d;
+ --nprogress-z-index: 1031;
+}
+These functions generate common information for your pages.
Get the excerpt of the page.
export interface PageExcerptOptions {
+ /**
+ * Excerpt separator
+ *
+ * @default "<!-- more -->"
+ */
+ separator?: string
+
+ /**
+ * Length of excerpt
+ *
+ * @description Excerpt length will be the minimal possible length reaching this value
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * Tags which is considered as custom elements
+ *
+ * @description This is used to determine whether a tag is a custom element since all unknown tags are removed in excerpt.
+ */
+ isCustomElement?: (tagName: string) => boolean
+
+ /**
+ * Whether keep page title (first h1) in excerpt
+ *
+ * @default false
+ */
+ keepPageTitle?: boolean
+
+ /**
+ * Whether preserve tags like line numbers and highlight lines for code blocks
+ *
+ * @default false
+ */
+ keepFenceDom?: boolean
+}
+
+export const getPageExcerpt: (
+ app: App,
+ page: Page,
+ options?: PageExcerptOptions,
+) => string
+Get plain text of the page.
export interface PageTextOptions {
+ /**
+ * Whether convert text to single line content
+ *
+ * @default false
+ */
+ singleLine?: boolean
+
+ /**
+ * Length of text
+ *
+ * @description Text length will be the minimal possible length reaching this value
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * Tags to be removed
+ *
+ * @description Table and code blocks are removed by default.
+ *
+ * @default ['table', 'pre']
+ */
+ removedTags?: string[]
+}
+
+export const getPageText: (
+ app: App,
+ page: Page,
+ options?: PageTextOptions,
+) => string
+这些函数为你的页面生成常见信息。
获取页面摘要。
export interface PageExcerptOptions {
+ /**
+ * 摘要分隔符
+ *
+ * @default "<!-- more -->"
+ */
+ separator?: string
+
+ /**
+ * 摘要的长度
+ *
+ * @description 摘要的长度会尽可能的接近这个值
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * 被认为是自定义元素的标签
+ *
+ * @description 用于判断一个标签是否是自定义元素，因为在摘要中，所有的未知标签都会被移除。
+ */
+ isCustomElement?: (tagName: string) => boolean
+
+ /**
+ * 是否保留页面标题 (第一个 h1)
+ *
+ * @default false
+ */
+ keepPageTitle?: boolean
+
+ /**
+ * 是否保留代码块的标签，诸如行号和高亮行
+ *
+ * @default false
+ */
+ keepFenceDom?: boolean
+}
+
+export const getPageExcerpt: (
+ app: App,
+ page: Page,
+ options?: PageExcerptOptions,
+) => string
+获取页面纯文本。
export interface PageTextOptions {
+ /**
+ * 是否将文字转换成单行内容
+ *
+ * @default false
+ */
+ singleLine?: boolean
+
+ /**
+ * 文字的长度
+ *
+ * @description 文字的长度会尽可能的接近这个值
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * 需要移除的标签
+ *
+ * @description 默认情况下表格和代码块会被移除
+ *
+ * @default ['table', 'pre']
+ */
+ removedTags?: string[]
+}
+
+export const getPageText: (
+ app: App,
+ page: Page,
+ options?: PageTextOptions,
+) => string
+为你的主题提供调色板功能。
该插件主要用于开发主题，并且已经集成到默认主题中。大部分情况下你不需要直接使用它。
对于主题作者，该插件可以帮助你提供用户自定义样式的能力。
npm i -D @vuepress/plugin-palette@next
+import { palettePlugin } from '@vuepress/plugin-palette'
+
+export default {
+ plugins: [
+ palettePlugin({
+ // 配置项
+ }),
+ ],
+}
+该插件会提供一个 @vuepress/plugin-palette/palette （调色板文件）和一个 @vuepress/plugin-palette/style （样式文件），用于在你的主题样式中引入。
样式文件用于覆盖默认样式或添加额外样式，因此它一般会在你主题样式的末尾引入。
在你的主题中使用该插件，假设你使用 SASS 作为 CSS 预处理器：
export default {
+ // ...
+ plugins: [palettePlugin({ preset: 'sass' })],
+}
+在你主题需要使用对应变量的地方引入该插件的调色板文件，比如在 Layout.vue 中：
<template>
+ <h1 class="palette-title">你好，调色板！</h1>
+</template>
+
+<style lang="scss">
+/* 从该插件的调色板中引入变量 */
+@import '@vuepress/plugin-palette/palette';
+
+/* 设置变量的默认值 */
+$color: red !default;
+
+/* 在你的样式中使用变量 */
+.palette-title {
+ color: $color;
+}
+</style>
+然后，用户就可以在 .vuepress/styles/palette.scss 中自定义变量：
$color: green;
+在你主题的样式之后引入该插件的样式文件，比如在 clientConfigFile 中：
// 引入你主题本身的样式文件
+import 'path/to/your/theme/style'
+// 引入该插件的样式文件
+import '@vuepress/plugin-palette/style'
+然后，用户就可以在 .vuepress/styles/index.scss 中添加额外样式，并可以覆盖你主题本身的样式：
h1 {
+ font-size: 2.5rem;
+}
+类型： 'css' | 'sass' | 'less' | 'stylus'
默认值： 'css'
详情：
设置其他选项的预设。
如果你没有对该插件进行进阶定制化的需要，建议只设置该配置项并忽略其他选项。
类型： string
默认值：
'.vuepress/styles/palette.css''.vuepress/styles/palette.scss''.vuepress/styles/palette.less''.vuepress/styles/palette.styl'详情：
用户调色板文件的路径，是针对源文件目录的相对路径。
默认值依赖于 preset 配置项。
该文件用于用户定义样式变量，建议保持默认值作为约定的文件路径。
类型： string
默认值：
'styles/palette.css''styles/palette.scss''styles/palette.less''styles/palette.styl'详情：
生成的调色板临时文件的路径，是针对临时文件文件目录的相对路径。
默认值依赖于 preset 配置项。
你应该使用 '@vuepress/plugin-palette/palette' 别名来引入调色板文件，因此在绝大多数情况下你不需要修改该配置项。
类型： string
默认值：
'.vuepress/styles/index.css''.vuepress/styles/index.scss''.vuepress/styles/index.less''.vuepress/styles/index.styl'详情：
用户样式文件的路径，是针对源文件目录的相对路径。
默认值依赖于 preset 配置项。
该文件用于用户覆盖默认样式和添加额外样式，建议保持默认值作为约定的文件路径。
类型： string
默认值：
'styles/index.css''styles/index.scss''styles/index.less''styles/index.styl'详情：
生成的样式临时文件的路径，是针对临时文件文件目录的相对路径。
默认值依赖于 preset 配置项。
你应该使用 '@vuepress/plugin-palette/style' 别名来引入样式文件，因此在绝大多数情况下你不需要修改该配置项。
类型： (filePath: string) => string
默认值：
(filePath) => \`@import '\${filePath}';\\n\`(filePath) => \`@forward 'file:///\${filePath}';\\n\`(filePath) => \`@import '\${filePath}';\\n\`(filePath) => \`@require '\${filePath}';\\n\`详情：
用于生成引入代码的函数。
默认值依赖于 preset 配置项。
该配置项用于生成 tempPaletteFile 和 tempStyleFile ，在绝大多数情况下你不需要修改该配置项。
Provide palette support for your theme.
This plugin is mainly used to develop themes, and has been integrated into the default theme. You won't need to use it directly in most cases.
For theme authors, this plugin will help you to provide styles customization for users.
npm i -D @vuepress/plugin-palette@next
+import { palettePlugin } from '@vuepress/plugin-palette'
+
+export default {
+ plugins: [
+ palettePlugin({
+ // options
+ }),
+ ],
+}
+This plugin will provide a @vuepress/plugin-palette/palette (palette file) and a @vuepress/plugin-palette/style (style file) to be imported in your theme styles.
The style file is used for overriding the default styles or adding extra styles, so it's likely to be imported at the end of your theme styles.
Use this plugin in your theme, assuming you are using SASS:
export default {
+ // ...
+ plugins: [palettePlugin({ preset: 'sass' })],
+}
+Import the plugin's palette file where your theme needs to use the corresponding variables, such as in the Layout.vue file:
<template>
+ <h1 class="palette-title">Hello, Palette!</h1>
+</template>
+
+<style lang="scss">
+/* import variables from the plugin's palette file */
+@import '@vuepress/plugin-palette/palette';
+
+/* set default value for variables */
+$color: red !default;
+
+/* use variables in your styles */
+.palette-title {
+ color: $color;
+}
+</style>
+Then users can customize variables in .vuepress/styles/palette.scss:
$color: green;
+Import the plugin's style file after your theme's styles, for example, in the clientConfigFile:
// import your theme's style file
+import 'path/to/your/theme/style'
+// import the plugin's style file
+import '@vuepress/plugin-palette/style'
+Then users can add extra styles in .vuepress/styles/index.scss and override the default styles of your theme:
h1 {
+ font-size: 2.5rem;
+}
+Type: 'css' | 'sass' | 'less' | 'stylus'
Default: 'css'
Details:
Set preset for other options.
If you don't need advanced customization of the plugin, it's recommended to only set this option and omit other options.
Type: string
Default:
'.vuepress/styles/palette.css''.vuepress/styles/palette.scss''.vuepress/styles/palette.less''.vuepress/styles/palette.styl'Details:
File path of the user palette file, relative to source directory.
The default value depends on the preset option.
The file is where users define style variables, and it's recommended to keep the default file path as a convention.
Type: string
Default:
'styles/palette.css''styles/palette.scss''styles/palette.less''styles/palette.styl'Details:
File path of the generated palette temp file, relative to temp directory.
The default value depends on the preset option.
You should import the palette file via '@vuepress/plugin-palette/palette' alias, so you don't need to change this option in most cases.
Type: string
Default:
'.vuepress/styles/index.css''.vuepress/styles/index.scss''.vuepress/styles/index.less''.vuepress/styles/index.styl'Details:
File path of the user style file, relative to source directory.
The default value depends on the preset option.
The file is where users override default styles or add extra styles, and it's recommended to keep the default file path as a convention.
Type: string
Default:
'styles/index.css''styles/index.scss''styles/index.less''styles/index.styl'Details:
File path of the generated style temp file, relative to temp directory.
The default value depends on the preset option.
You should import the style file via '@vuepress/plugin-palette/style' alias, so you don't need to change this option in most cases.
Type: (filePath: string) => string
Default:
(filePath) => \`@import '\${filePath}';\\n\`(filePath) => \`@forward 'file:///\${filePath}';\\n\`(filePath) => \`@import '\${filePath}';\\n\`(filePath) => \`@require '\${filePath}';\\n\`Details:
Function to generate import code.
The default value depends on the preset option.
This option is used for generating tempPaletteFile and tempStyleFile, and you don't need to change this option in most cases.
此插件会使页面正文内的图片在点击时进入浏览模式浏览。
npm i -D @vuepress/plugin-photo-swipe@next
+import { photoSwipePlugin } from '@vuepress/plugin-photo-swipe'
+
+export default {
+ plugins: [
+ photoSwipePlugin({
+ // 选项
+ }),
+ ],
+}
+在图片预览模式中，你可以:
提示
string | string[]".theme-default-content :not(a) > img:not([no-view])"booleantrue类型：number
默认值：800
详情：
操作页面 DOM 的延时，单位 ms。
提示
如果你使用的主题有切换动画，建议配置此选项为 切换动画时长 + 200。
类型：PhotoSwipePluginLocaleConfig
interface PhotoSwipePluginLocaleData {
+ /**
+ * 关闭按钮标签文字
+ */
+ close: string
+
+ /**
+ * 全屏按钮标签文字
+ */
+ fullscreen: string
+
+ /**
+ * 分享按钮标签文字
+ */
+ share: string
+
+ /**
+ * 缩放按钮标签文字
+ */
+ zoom: string
+
+ /**
+ * 上一张图片按钮标签文字
+ */
+ prev: string
+
+ /**
+ * 下一张图片按钮标签文字
+ */
+ next: string
+
+ /**
+ * 功能按钮配置
+ */
+ buttons: PhotoSwipeDefaultUI.ShareButtonData[]
+}
+
+interface PhotoSwipePluginLocaleConfig {
+ [localePath: string]: PhotoSwipePluginLocaleData
+}
+详情：Photo Swipe 插件的国际化配置。
示例：
import { defineUserConfig } from 'vuepress'
+import { photoSwipePlugin } from '@vuepress/plugin-photo-swipe'
+
+export default defineUserConfig({
+ locales: {
+ '/': {
+ // 这是一个支持的语言
+ lang: 'zh-CN',
+ },
+ '/xx/': {
+ // 这是一个没有收到插件支持的语言
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ photoSwipePlugin({
+ locales: {
+ '/': {
+ // 覆盖分享标签文字
+ share: '分享给伙伴',
+ },
+
+ '/xx/': {
+ // 在这里完整设置 \`mm-NN\` 的多语言配置
+ },
+ },
+ }),
+ ],
+})
+类型： string | false
详情：
当前页面的图片选择器或 false 以在当前页面中禁用 photo-swipe。
import { definePhotoSwipeConfig } from '@vuepress/plugin-photo-swipe/client'
+
+definePhotoSwipeConfig({
+ // 在此设置 photoswipe 选项
+})
+
+export default {}
+你可以通过 API 来调用 photoswipe。
createPhotoSwipe 允许你以编程的方式查看图片链接:
<script setup lang="ts">
+import { onMounted, onUnmounted } from 'vue';
+import { createPhotoSwipe } from "@vuepress/plugin-photo-swipe/client";
+
+let state: PhotoSwipeState | null = null;
+
+const openPhotoSwipe = (index: number) => {
+ state?.open(index - 1);
+};
+
+onMounted(async () => {
+ // 通过图片链接创建一个新的 photoswipe 实例
+ state= await createPhotoSwipe(
+ [
+ 'https://exmaple.com/image1.png'
+ 'https://exmaple.com/image2.png'
+ 'https://exmaple.com/image3.png'
+ ],
+ {
+ // photoswipe 选项
+ }
+ );
+});
+
+onUnmounted(() => {
+ state?.destroy()
+})
+</script>
+
+<template>
+ <button v-for="i in 3" @click="openPhotoSwipe(i)">open photo {{ i }}</button>
+</template>
+registerPhotoSwipe 允许你为给定的图片元素注册 photoswipe:
<script setup lang="ts">
+import { onMounted, onUnmounted } from 'vue'
+import { registerPhotoSwipe } from '@vuepress/plugin-photo-swipe/client'
+
+let destroy: () => void | null = null
+
+onMounted(async () => {
+ await nextTick()
+
+ const images = Array.from(document.querySelectorAll('img'))
+
+ // 通过图片元素创建一个新的 photoswipe 实例
+ state = await registerPhotoSwipe(images, {
+ // photoswipe 选项
+ })
+})
+
+onUnmounted(() => {
+ destroy?.()
+})
+</script>
+你可以通过 CSS 变量来自定义部分样式：
:root {
+ --photo-swipe-bullet: #fff;
+ --photo-swipe-bullet-active: #3eaf7c;
+}
+This plugin will make the pictures in the body of the page enter the preview mode when clicked.
npm i -D @vuepress/plugin-photo-swipe@next
+import { photoSwipePlugin } from '@vuepress/plugin-photo-swipe'
+
+export default {
+ plugins: [
+ photoSwipePlugin({
+ // options
+ }),
+ ],
+}
+In preview mode, you can:
TIP
string | string[]".theme-default-content :not(a) > img:not([no-view])"booleantrueType: number
Default: 800
Details:
The delay of operating dom, in ms.
TIP
If the theme you are using has a switching animation, it is recommended to configure this option to Switch animation duration + 200.
Type: PhotoSwipePluginLocaleConfig
interface PhotoSwipePluginLocaleData {
+ /**
+ * Close button label text
+ */
+ close: string
+
+ /**
+ * Full screen button label text
+ */
+ fullscreen: string
+
+ /**
+ * Share button label text
+ */
+ share: string
+
+ /**
+ * Zoom button label text
+ */
+ zoom: string
+
+ /**
+ * Previous image button label text
+ */
+ prev: string
+
+ /**
+ * Next image button label text
+ */
+ next: string
+
+ /**
+ * Share button config
+ */
+ buttons: PhotoSwipeDefaultUI.ShareButtonData[]
+}
+
+interface PhotoSwipePluginLocaleConfig {
+ [localePath: string]: PhotoSwipePluginLocaleData
+}
+Details: Locales config for photo-swipe plugin.
Example:
import { defineUserConfig } from 'vuepress'
+import { photoSwipePlugin } from '@vuepress/plugin-photo-swipe'
+
+export default defineUserConfig({
+ locales: {
+ '/': {
+ // this is a supported language
+ lang: 'en-US',
+ },
+ '/xx/': {
+ // the plugin does not support this language
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ photoSwipePlugin({
+ locales: {
+ '/': {
+ // Override share label text
+ share: 'Share with friends',
+ },
+
+ '/xx/': {
+ // Complete locale config for \`mm-NN\` language here
+ },
+ },
+ }),
+ ],
+})
+string | falseImage selector for the current page, or false to disable photo-swipe in current page.
import { definePhotoSwipeConfig } from '@vuepress/plugin-photo-swipe/client'
+
+definePhotoSwipeConfig({
+ // set photoswipe options here
+})
+
+export default {}
+You can also call photoswipe with apis.
createPhotoSwipe allows you to programmatically view images links with PhotoSwipe:
<script setup lang="ts">
+import { onMounted, onUnmounted } from 'vue';
+import { createPhotoSwipe } from "@vuepress/plugin-photo-swipe/client";
+
+let state: PhotoSwipeState | null = null;
+
+const openPhotoSwipe = (index: number) => {
+ state?.open(index - 1);
+};
+
+onMounted(async () => {
+ // create a new photoswipe instance with image links
+ state= await createPhotoSwipe(
+ [
+ 'https://exmaple.com/image1.png'
+ 'https://exmaple.com/image2.png'
+ 'https://exmaple.com/image3.png'
+ ],
+ {
+ // photoswipe options
+ }
+ );
+});
+
+onUnmounted(() => {
+ state?.destroy()
+})
+</script>
+
+<template>
+ <button v-for="i in 3" @click="openPhotoSwipe(i)">open photo {{ i }}</button>
+</template>
+registerPhotoSwipe allows you to register photoswipe for the given image elements:
<script setup lang="ts">
+import { onMounted, onUnmounted } from 'vue'
+import { registerPhotoSwipe } from '@vuepress/plugin-photo-swipe/client'
+
+let destroy: () => void | null = null
+
+onMounted(async () => {
+ await nextTick()
+
+ const images = Array.from(document.querySelectorAll('img'))
+
+ // create a new photoswipe instance on image elements
+ state = await registerPhotoSwipe(images, {
+ // photoswipe options
+ })
+})
+
+onUnmounted(() => {
+ destroy?.()
+})
+</script>
+You can customize the style via CSS variables:
:root {
+ --photo-swipe-bullet: #fff;
+ --photo-swipe-bullet-active: #3eaf7c;
+}
+You can configure the plugins that used by default theme with themePlugins.
Default theme is using some plugins by default. You can disable a plugin if you really do not want to use it. Make sure you understand what the plugin is for before disabling it.
import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ themePlugins: {
+ // customize theme plugins here
+ },
+ }),
+}
+ContainerType type is:
tipwarningdangerdetailscodeGroupcodeGroupItem你可以通过 themePlugins 设置默认主题使用的插件。
默认主题使用了一些插件，如果你确实不需要该插件，你可以选择禁用它。在禁用插件之前，请确保你已了解它的用途。
import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ themePlugins: {
+ // 在这里自定义主题插件
+ },
+ }),
+}
+ContainerType 类型为：
tipwarningdangerdetailscodeGroupcodeGroupItemThis plugin has been integrated into the default theme.
Notice that this plugin would only tokenize the code fence without adding styles. When using it with a custom theme, you may need to choose and import Prism.js style theme yourself.
npm i -D @vuepress/plugin-prismjs@next
+import { prismjsPlugin } from '@vuepress/plugin-prismjs'
+
+export default {
+ plugins: [
+ prismjsPlugin({
+ // options
+ }),
+ ],
+}
+该插件已经集成到默认主题中。
需要注意的是，该插件仅会给代码块添加 HTML 标记，而不会添加样式。当你在一个自定义主题中使用它时，可能需要自己选择并引入 Prism.js 样式主题。
npm i -D @vuepress/plugin-prismjs@next
+import { prismjsPlugin } from '@vuepress/plugin-prismjs'
+
+export default {
+ plugins: [
+ prismjsPlugin({
+ // 配置项
+ }),
+ ],
+}
+此插件会为每个页面生成字数统计与预计阅读时间。
npm i -D @vuepress/plugin-reading-time@next
+import { readingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default {
+ plugins: [
+ readingTimePlugin({
+ // 配置项
+ }),
+ ],
+}
+插件会将相关信息注入到页面数据的 readingTime，其中：
readingTime.minutes：为预计阅读时间（分钟）numberreadingTime.words：字数统计，number对于任何页面，你可以从 page.data.readingTime 获取预计阅读时间与字数统计:
page.data.readingTime // { minutes: 3.2, words: 934 }
+你可以在 extendsPage 以及其他生命周期获取它做进一步处理:
export default {
+ // ...
+ extendsPage: (page) => {
+ page.data.readingTime // { minutes: 3.2, words: 934 }
+ },
+
+ onInitialized: (app) => {
+ app.pages.map((page) => {
+ page.data.readingTime // { minutes: 3.2, words: 934 }
+ })
+ },
+}
+你可以从 @vuepress/plugin-reading-time/client 导入 useReadingTimeData 和 useReadingTimeLocale 来获取当前页面的阅读时间数据和语言环境数据：
<script setup lang="ts">
+import {
+ useReadingTimeData,
+ useReadingTimeLocale,
+} from '@vuepress/plugin-reading-time/client'
+
+const readingTimeData = useReadingTimeData() // { minutes: 1.1, words: 100 }
+const readingTimeLocale = useReadingTimeLocale() // { time: "1 分钟", words: "100 字" }
+</script>
+number300类型：ReadingTimePluginLocaleConfig
interface ReadingTimePluginLocaleData {
+ /**
+ * 字数模板，模板中 \`$word\` 会被自动替换为字数
+ */
+ word: string
+
+ /**
+ * 小于一分钟文字
+ */
+ less1Minute: string
+
+ /**
+ * 时间模板
+ */
+ time: string
+}
+
+interface ReadingTimePluginLocaleConfig {
+ [localePath: string]: ReadingTimePluginLocaleData
+}
+必填：否
详情：
阅读时间插件的国际化配置。
你可以从 @vuepress/plugin-reading-time/client 导入并使用这些 API：
即使插件被禁用，这些 API 也不会抛出错误。
interface ReadingTime {
+ /** 分钟为单位的预计阅读时长 */
+ minutes: number
+ /** 内容的字数 */
+ words: number
+}
+
+const useReadingTimeData: () => ComputedRef<ReadingTime | null>
+当插件被禁用时会返回 null。
interface ReadingTimeLocale {
+ /** 当前语言的预计阅读时间 */
+ time: string
+ /** 当前语言的字数文字 */
+ words: string
+}
+
+const useReadingTimeLocale: () => ComputedRef<ReadingTimeLocale>
+由于此插件主要面向插件和主题开发者，所以提供了 "使用 API"：
import { useReadingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default (options) => (app) => {
+ useReadingTimePlugin(app, {
+ // 你的选项
+ })
+
+ return {
+ name: 'vuepress-plugin-xxx', // or vuepress-theme-xxx
+ }
+}
+为什么你应该使用 "使用 API"
当你多次注册一个插件时，vuepress 会给你一个警告，告诉你只有第一个插件会生效。useReadingTimePlugin 会自动检测插件是否已经注册，避免多次注册。
如果你在 extendsPage 生命周期访问阅读时间数据，那么 @vuepress/plugin-reading-time 必须在你的主题或插件之前被调用，否则你会得到未定义的 page.data.readingTime。useReadingTimePlugin 确保了 @vuepress/plugin-reading-time 在你的主题或插件之前被调用。
我们也提供了一个 removeReadingTimePlugin api 来移除插件。你可以使用它来确保你的调用生效或清除插件:
import { useReadingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default (options) => (app) => {
+ // 这会移除任何当前存在的阅读时间插件
+ removeReadingTimePlugin(app)
+
+ // 所以这会生效，即使之前已经注册了一个阅读时间插件
+ useReadingTimePlugin(app, {
+ // 你的选项
+ })
+
+ return {
+ name: 'vuepress-plugin-xxx', // or vuepress-theme-xxx
+ }
+}
+This plugin will generate word count and estimated reading time for each page.
npm i -D @vuepress/plugin-reading-time@next
+import { readingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default {
+ plugins: [
+ readingTimePlugin({
+ // options
+ }),
+ ],
+}
+The plugin will inject reading time information into the readingTime of the page data, where:
readingTime.minutes: estimated reading time (minutes) numberreadingTime.words: word count numberFor any page, you can get estimated reading time and word count from page.data.readingTime:
page.data.readingTime // { minutes: 3.2, words: 934 }
+You can access it for further processing in the extendsPage lifecycle and other lifecycle:
export default {
+ // ...
+ extendsPage: (page) => {
+ page.data.readingTime // { minutes: 3.2, words: 934 }
+ },
+
+ onInitialized: (app) => {
+ app.pages.map((page) => {
+ page.data.readingTime // { minutes: 3.2, words: 934 }
+ })
+ },
+}
+You can import useReadingTimeData and useReadingTimeLocale from @vuepress/plugin-reading-time/client to get the reading time data and locale data of the current page:
<script setup lang="ts">
+import {
+ useReadingTimeData,
+ useReadingTimeLocale,
+} from '@vuepress/plugin-reading-time/client'
+
+const readingTimeData = useReadingTimeData() // { minutes: 1.1, words: 100 }
+const readingTimeLocale = useReadingTimeLocale() // { time: "1 minute", words: "100 words" }
+</script>
+number300Type: ReadingTimePluginLocaleConfig
interface ReadingTimePluginLocaleData {
+ /**
+ * Word template, \`$word\` will be automatically replaced by actual words
+ */
+ word: string
+
+ /**
+ * Text for less than one minute
+ */
+ less1Minute: string
+
+ /**
+ * Time template
+ */
+ time: string
+}
+
+interface ReadingTimePluginLocaleConfig {
+ [localePath: string]: ReadingTimePluginLocaleData
+}
+Required: No
Details:
Locales config for reading-time plugin.
You can import and use these APIs from @vuepress/plugin-reading-time/client:
These APIs won't throw even you disable the plugin.
interface ReadingTime {
+ /** Expect reading time in minute unit */
+ minutes: number
+ /** Words count of content */
+ words: number
+}
+
+const useReadingTimeData: () => ComputedRef<ReadingTime | null>
+null is returned when the plugin is disabled.
interface ReadingTimeLocale {
+ /** Expect reading time text in locale */
+ time: string
+ /** Word count text in locale */
+ words: string
+}
+
+const useReadingTimeLocale: () => ComputedRef<ReadingTimeLocale>
+This plugin is targeting plugin and theme developers mostly, so we provide a "Use API":
import { useReadingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default (options) => (app) => {
+ useReadingTimePlugin(app, {
+ // your options
+ })
+
+ return {
+ name: 'vuepress-plugin-xxx', // or vuepress-theme-xxx
+ }
+}
+Why you should use "Use API"
useReadingTimePlugin automatically detects if the plugin is registered and avoid registering multiple times.extendsPage lifecycle, then @vuepress/plugin-reading-time must be called before your theme or plugin, otherwise you will get undefined for page.data.readingTime. The useReadingTimePlugin ensures that @vuepress/plugin-reading-time is called before your theme or plugin.We also provides a removeReadingTimePlugin api to remove the plugin.You can use this to ensure your call take effect or clear the plugin:
import { useReadingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default (options) => (app) => {
+ // this removes any existing reading time plugin at this time
+ removeReadingTimePlugin(app)
+
+ // so this will take effect even if there is a reading time plugin registered before
+ useReadingTimePlugin(app, {
+ // your options
+ })
+
+ return {
+ name: 'vuepress-plugin-xxx', // or vuepress-theme-xxx
+ }
+}
+This plugin can automatically handle redirects for your site.
npm i -D @vuepress/plugin-redirect@next
+import { redirectPlugin } from '@vuepress/plugin-redirect'
+
+export default {
+ plugins: [
+ redirectPlugin({
+ // options
+ }),
+ ],
+}
+If you change the address of an existing page, you can use the redirectFrom option in Frontmatter to redirect to the address of this page, which ensures that users are redirected to the new address when they visit the old link.
If you need to redirect an existing page to a new page, you can use the redirectTo option in Frontmatter to set the address to redirect to. This way the page will redirect to the new address when accessed.
You can also set config with a redirect map in plugin options, see config for more details.
The plugin can automatically redirect non-multilingual links to the multilingual pages the user needs based on the user's language preference.
To achieve this, you need to leave the default language directory (/) blank and set autoLocale: true in plugin options. The plugin will automatically redirect to the correct page according to the user's language.
I.E.: you need to set the following directory structure:
.
+├── en
+│ ├── ...
+│ ├── page.md
+│ └── README.md
+├── zh
+│ ├── ...
+│ ├── page.md
+│ └── README.md
+└── other_languages
+ ├── ...
+ ├── page.md
+ └── README.md
+And set locales in theme options with:
export default {
+ locales: {
+ '/en/': {
+ lang: 'en-US',
+ // ...
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ // ...
+ },
+ // other languages
+ },
+ // ...
+}
+So when a user accesses / or /page.html, they are automatically redirected to /en/ /en/page.html and /en/ /en/page.html based on current browser language.
Customizing fallback behavior
Sometimes, users may add more than one language to the system settings. By default, when a site supports a preferred language, but the page not exists for the preferred language, the plugin attempts to match the alternate language set by the user.
If you don't need to fall back to the user's alternate language, but directly match the user's preferred language, set localeFallback: false in the plugin options.
Customizing missing behavior
Sometimes, when a user visits a page, the document does not yet contain the language version the user needs (a common case is that the current page has not been localized in the relevant language), so the plugin needs to perform a default action, which you can customize by defaultBehavior in the plugin options:
"defaultLocale": Redirect to default language or first available language page (default behavior)"homepage": redirect to the home page in the current language (only available if the document contains the user's language)"404": Redirect to page 404 in current language (only available if the document contains the user's language)Customizing default locale path
You can customize the default locale path by setting defaultLocale in the plugin options. By default, the plugin uses the first locale key in locales as the default language.
The plugin supports automatically switching the link to the multilingual page that the user needs according to the user's language preference when opening a multilingual document. In order to achieve this, you need to set switchLocale in the plugin options, which can be the following two values:
direct: switch directly to the user language preference page without askingmodal: When the user's language preference is different from the current page language, show a modal asking whether to switch languageBy default, the plugin generates a locale setting by reading locale path and lang from the site's locales option. Sometimes, you may want multiple languages to hit the same path, in which case you should set localeConfig in plugin options.
For example, you might want all English users to match to /en/ and Chinese Traditional users to /zh/, then you can set:
redirect({
+ localeConfig: {
+ '/en/': ['en-US', 'en-UK', 'en'],
+ '/zh/': ['zh-CN', 'zh-TW', 'zh'],
+ },
+})
+Sometimes you may change base or use new domain for your site, so you may want the original site automatically redirects to the new one.
To solve this, the plugin provide vp-redirect cli.
Usage:
+ $ vp-redirect generate [sourceDir]
+
+Options:
+ --hostname <hostname> Hostname to redirect to (E.g.: https://new.example.com/) (default: /)
+ -c, --config <config> Set path to config file
+ -o, --output <output> Set the output directory (default: .vuepress/redirect)
+ --cache <cache> Set the directory of the cache files
+ -t, --temp <temp> Set the directory of the temporary files
+ --clean-cache Clean the cache files before generation
+ --clean-temp Clean the temporary files before generation
+ -h, --help Display this message
+You need to pass in VuePress project source dir and also set the hostname option. The redirect helper cli will initialize your VuePress project to get pages, then generate and output the redirect html files to the output directory.
By default, the plugin will output to .vuepress/redirect directory under source directory. And you should upload it to your original site to provide redirection.
Type: Record<string, string> | ((app: App) => Record<string, string>)
Details: Redirect map.
Example:
When base is set to /base/:
/base/foo.html to /base/bar.html/base/baz.html to https://example.com/qux.html.redirect({
+ config: {
+ '/foo.html': '/bar.html',
+ '/baz.html': 'https://example.com/qux.html',
+ },
+})
+Redirect post folder to posts folder:
redirect({
+ hostname: 'https://example.com',
+ config: (app) =>
+ Object.fromEntries(
+ app.pages
+ .filter(({ path }) => path.startsWith('/posts/'))
+ .map(({ path }) => [path.replace(/^\\/posts\\//, '/post/'), path]),
+ ),
+})
+booleanfalseType: "direct" | "modal" | false
Default: false
Details:
Whether switch to a new locale based on user preference.
"direct": redirect to the new locale directly without asking"modal": show a modal to let user choose whether to switch to the new localeType: Record<string, string | string[]>
Details: Locale language config
booleantrue"defaultLocale" | "homepage" | "404""defaultLocale"stringstring | string[]stringYou can customize the style of the redirect popup via CSS variables:
:root {
+ --redirect-z-index: 1499;
+ --redirect-bg-color: #fff;
+ --redirect-bg-color-light: #f3f4f5;
+ --redirect-bg-color-lighter: #eeeeee;
+ --redirect-text-color: #2c3e50;
+ --redirect-primary-color: #3eaf7c;
+ --redirect-primary-hover-color: #4abf8a;
+ --redirect-primary-text-color: #fff;
+}
+此插件提供页面与整站重定向功能。
npm i -D @vuepress/plugin-redirect@next
+import { redirectPlugin } from '@vuepress/plugin-redirect'
+
+export default {
+ plugins: [
+ redirectPlugin({
+ // 配置项
+ }),
+ ],
+}
+如果你改动了已有页面的地址，你可以在 Frontmatter 中使用 redirectFrom 选项设置重定向到此页面的地址，这样可以保证用户在访问旧链接时重定向到新的地址。
如果你需要将已有的页面重定向到新的页面，可以在 Frontmatter 中使用 redirectTo 选项设置需要重定向到的地址。这样该页面会在访问时重定向到新的地址。
你还可以通过插件选项中的 config 设置一个重定向映射，详见 config。
插件可以根据用户的语言首选项，自动将无多语言链接重定向到用户需要的多语言页面。为了实现这一点，你需要留空默认的语言目录 (/)，并在插件选项中设置 autoLocale: true。插件会自动根据用户语言跳转到对应的语言页面。
也就是你需要设置以下目录结构:
.
+├── en
+│ ├── ...
+│ ├── page.md
+│ └── README.md
+├── zh
+│ ├── ...
+│ ├── page.md
+│ └── README.md
+└── other_languages
+ ├── ...
+ ├── page.md
+ └── README.md
+并将主题选项的 locales 设置为:
export default {
+ locales: {
+ '/en/': {
+ lang: 'en-US',
+ // ...
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ // ...
+ },
+ // other languages
+ },
+ // ...
+}
+这样当用户访问 / 或 /page.html 时，他们会自动根据当前浏览器语言重定向到 /en/ /en/page.html 与 /zh/ /zh/page.html。
自定义回退行为
有些时候，用户可能会在系统设置中添加多个语言。默认情况下，在站点支持首选语言，但首选语言不存在相应页面时，插件会尝试匹配用户设置的备用语言。
如果不需要回退到用户备用语言，而直接匹配用户首选语言，请在插件选项中设置 localeFallback: false。
自定义缺失行为
有些时候，当用户访问一个页面时，文档尚未包含用户需要的语言版本 (一个普遍的情况是当前页面尚未完成相关语言的本地化)，这样插件需要做出默认行为，你可以通过插件选项中的 defaultBehavior 定制它:
"defaultLocale": 重定向到默认语言或首个可用语言页面 (默认行为)"homepage": 重定向到当前语言的主页 (仅在文档包含用户语言时可用)"404": 重定向到当前语言的 404 页 (仅在文档包含用户语言时可用)自定义默认路径
你可以通过设置插件选项中的 defaultLocale 来自定义默认路径。默认情况下，插件会使用 locales 中的第一个键名作为默认路径。
插件支持在多语言文档中，自动根据用户语言首选项，将链接切换到用户需要的多语言页面。为了实现这一点，你需要在插件选项中设置 switchLocale，它可以是以下两个值:
direct: 直接切换到用户语言首选项页面，而不询问modal: 在用户语言首选项与当前页面语言不同时，弹出一个对话框询问用户是否切换语言默认情况下，插件会从站点的多语言配置 locales 选项中，读取 语言路径 和 lang 生成多语言配置。有些时候，你可能希望多个语言命中同一个路径，这种情况下，你应该设置插件的 localeConfig 选项。
比如，你可能希望所有英文用户都匹配到 /en/，并将繁体中文用户匹配到 /zh/ 中，那么你可以设置:
redirect({
+ localeConfig: {
+ '/en/': ['en-US', 'en-UK', 'en'],
+ '/zh/': ['zh-CN', 'zh-TW', 'zh'],
+ },
+})
+有时你可能会更改 base 或为你的站点使用新域名，因此你可能希望原始站点自动重定向到新站点。
为了解决这个问题，插件提供了 vp-redirect 脚手架。
使用:
+ $ vp-redirect generate [源文件夹]
+
+Options:
+ --hostname <hostname> 重定向到的域名 (例如: https://new.example.com/) (默认: /)
+ -c, --config <config> 设置配置文件路径
+ -o, --output <output> 设置输出目录 (默认: .vuepress/redirect)
+ --cache <cache> 设置缓存文件的目录
+ -t, --temp <temp> 设置临时文件的目录
+ --clean-cache 生成前清理缓存文件
+ --clean-temp 生成前清理临时文件
+ -h, --help 显示此消息
+你需要传入 VuePress 项目源目录并设置 hostname 选项。重定向助手脚手架将初始化你的 VuePress 项目以获取页面，然后在输出目录生成重定向 html 文件。
默认情况下，插件将输出到源文件夹下的 .vuepress/redirect 目录。你应该将其上传到你的原始站点以提供重定向。
类型：Record<string, string> | ((app: App) => Record<string, string>)
详情
页面重定向映射。
可直接传入对象或传入参数为 App 的函数返回值一个对象。
每个键名必须是一个绝对路径，代表重定向的源页面地址。
每个键值是重定向的目标地址，可以是绝对路径或完整路径。
示例：
当 base 为 /base/时：
/base/foo.html 重定向到 /base/bar.html/base/baz.html 重定向到 https://example.com/qux.html。redirect({
+ config: {
+ '/foo.html': '/bar.html',
+ '/baz.html': 'https://example.com/qux.html',
+ },
+})
+将 post 文件夹的路径重定向到 posts 文件夹
redirect({
+ hostname: 'https://example.com',
+ config: (app) =>
+ Object.fromEntries(
+ app.pages
+ .filter(({ path }) => path.startsWith('/posts/'))
+ .map(({ path }) => [path.replace(/^\\/posts\\//, '/post/'), path]),
+ ),
+})
+booleanfalse类型："direct" | "modal" | false
默认值: false
详情：
是否根据用户偏好切换到新的语言环境。
"direct": 直接重定向到新的语言环境而不询问"modal": 显示一个模式让用户选择是否切换到新的语言环境Record<string, string | string[]>booleantrue"defaultLocale" | "homepage" | "404""defaultLocale"stringstring | string[]string你可以通过 CSS 变量来自定义重定向弹窗的样式：
:root {
+ --redirect-z-index: 1499;
+ --redirect-bg-color: #fff;
+ --redirect-bg-color-light: #f3f4f5;
+ --redirect-bg-color-lighter: #eeeeee;
+ --redirect-text-color: #2c3e50;
+ --redirect-primary-color: #3eaf7c;
+ --redirect-primary-hover-color: #4abf8a;
+ --redirect-primary-text-color: #fff;
+}
+Register Vue components from component files or directory automatically.
npm i -D @vuepress/plugin-register-components@next
+import { registerComponentsPlugin } from '@vuepress/plugin-register-components'
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ // options
+ }),
+ ],
+}
+Type: Record<string, string>
Default: {}
Details:
An object that defines name of components and their corresponding file path.
The key will be used as the component name, and the value is an absolute path of the component file.
If the component name from this option conflicts with componentsDir option, this option will have a higher priority.
Example:
import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ components: {
+ FooBar: path.resolve(__dirname, './components/FooBar.vue'),
+ },
+ }),
+ ],
+}
+Type: string | null
Default: null
Details:
Absolute path to the components directory.
Files in this directory which are matched with componentsPatterns will be registered as Vue components automatically.
Example:
import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ componentsDir: path.resolve(__dirname, './components'),
+ }),
+ ],
+}
+Components directory:
components
+├─ FooBar.vue
+└─ Baz.vue
+Components will be registered like this:
import { defineAsyncComponent } from 'vue'
+
+app.component(
+ 'FooBar',
+ defineAsyncComponent(() => import('/path/to/components/FooBar.vue')),
+)
+
+app.component(
+ 'Baz',
+ defineAsyncComponent(() => import('/path/to/components/Baz.vue')),
+)
+Type: (filename: string) => string
Default: (filename) => path.trimExt(filename.replace(/\\/|\\\\/g, '-'))
Details:
A function to get component name from the filename.
It will only take effect on the files in the componentsDir which are matched with the componentsPatterns.
Notice that the filename is a filepath relative to componentsDir.
根据组件文件或目录自动注册 Vue 组件。
npm i -D @vuepress/plugin-register-components@next
+import { registerComponentsPlugin } from '@vuepress/plugin-register-components'
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ // 配置项
+ }),
+ ],
+}
+类型： Record<string, string>
默认值： {}
详情：
一个定义了组件名称和其对应文件路径的对象。
键会被用作组件名称，值是组件文件的绝对路径。
如果该配置项中的组件名称和 componentsDir 配置项发生冲突，那么该配置项会有更高的优先级。
示例：
import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ components: {
+ FooBar: path.resolve(__dirname, './components/FooBar.vue'),
+ },
+ }),
+ ],
+}
+类型： string | null
默认值： null
详情：
组件目录的绝对路径。
该目录下匹配 componentsPatterns 的文件会被自动注册为 Vue 组件。
示例：
import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ componentsDir: path.resolve(__dirname, './components'),
+ }),
+ ],
+}
+组件目录：
components
+├─ FooBar.vue
+└─ Baz.vue
+组件会像这样被注册：
import { defineAsyncComponent } from 'vue'
+
+app.component(
+ 'FooBar',
+ defineAsyncComponent(() => import('/path/to/components/FooBar.vue')),
+)
+
+app.component(
+ 'Baz',
+ defineAsyncComponent(() => import('/path/to/components/Baz.vue')),
+)
+类型： (filename: string) => string
默认值： (filename) => path.trimExt(filename.replace(/\\/|\\\\/g, '-'))
详情：
用于从文件名获取对应组件名称的函数。
它只会对 componentsDir 目录下匹配了 componentsPatterns 的文件生效。
注意，这里的 filename 是相对于 componentsPatterns 目录的文件路径。
npm i -D @vuepress/plugin-remove-pwa@next
+import { removePwaPlugin } from '@vuepress/plugin-remove-pwa'
+
+export default {
+ plugins: [
+ removePwaPlugin({
+ // options
+ }),
+ ],
+}
+string'workbox'string'service-worker.js'npm i -D @vuepress/plugin-remove-pwa@next
+import { removePwaPlugin } from '@vuepress/plugin-remove-pwa'
+
+export default {
+ plugins: [
+ removePwaPlugin({
+ // options
+ }),
+ ],
+}
+string'workbox'string'service-worker.js'此插件会在配置的语言上设置 rtl 方向。
npm i -D @vuepress/plugin-rtl@next
+import { rtlPlugin } from '@vuepress/plugin-rtl'
+
+export default {
+ plugins: [
+ rtlPlugin({
+ // 配置项
+ locales: ['/ar/'],
+ }),
+ ],
+}
+string[]['/']类型：SelectorOptions
interface SelectorOptions {
+ [element: string]: {
+ [attrs: string]: string
+ }
+}
+默认值：{ 'html': { dir: 'rtl' } }
详情：
开启 RTL 的选择器。
默认设置意味着在 RTL 多语言中，html 元素的 dir 属性将被设置为 rtl。
This plugin will set direction to rtl on configured locales.
npm i -D @vuepress/plugin-rtl@next
+import { rtlPlugin } from '@vuepress/plugin-rtl'
+
+export default {
+ plugins: [
+ rtlPlugin({
+ // options
+ locales: ['/ar/'],
+ }),
+ ],
+}
+string[]['/']Type: SelectorOptions
interface SelectorOptions {
+ [element: string]: {
+ [attrs: string]: string
+ }
+}
+Default: { 'html': { dir: 'rtl' } }
Details:
Selector to enable rtl.
The default settings mean that the dir attribute of the html element will be set to rtl in rtl locales.
为你的文档网站提供本地搜索能力。
提示
当你正确配置该插件后，默认主题会把搜索框添加到导航栏。
该插件不一定能在其他主题中直接使用，因此你应参考主题本身的文档来获取更多信息。
npm i -D @vuepress/plugin-search@next
+import { searchPlugin } from '@vuepress/plugin-search'
+
+export default {
+ plugins: [
+ searchPlugin({
+ // 配置项
+ }),
+ ],
+}
+该插件会根据你的页面，在本地生成搜索索引，然后在用户访问站点时加载搜索索引文件。换句话说，这是一个轻量级的内置搜索能力，不会进行任何外部请求。
`,7),u=l(`类型： Record<string, { placeholder: string }>
详情：
搜索框在不同 locales 下的文字。
如果没有指定该配置项，它会降级使用默认文字。
示例：
export default {
+ plugins: [
+ searchPlugin({
+ locales: {
+ '/': {
+ placeholder: 'Search',
+ },
+ '/zh/': {
+ placeholder: '搜索',
+ },
+ },
+ }),
+ ],
+}
+(string | HotKeyOptions)[]export interface HotKeyOptions {
+ /**
+ * Value of \`event.key\` to trigger the hot key
+ */
+ key: string;
+ /**
+ * Whether to press \`event.altKey\` at the same time
+ *
+ * @default false
+ */
+ alt?: boolean;
+ /**
+ * Whether to press \`event.ctrlKey\` at the same time
+ *
+ * @default false
+ */
+ ctrl?: boolean;
+ /**
+ * Whether to press \`event.shiftKey\` at the same time
+ *
+ * @default false
+ */
+ shift?: boolean;
+}
+类型： number
默认值： 5
详情：
指定搜索结果的最大条数。
类型： (page: Page) => boolean
默认值： () => true
详情：
一个函数，用于判断一个页面是否应该被包含在搜索索引中。
true 来包含该页面。false 来排除该页面。示例：
export default {
+ plugins: [
+ searchPlugin({
+ // 排除首页
+ isSearchable: (page) => page.path !== '/',
+ }),
+ ],
+}
+类型： (page: Page) => string[]
默认值： () => []
详情：
一个函数，用于在页面的搜索索引中添加额外字段。
默认情况下，该插件会将页面标题和小标题作为搜索索引。该配置项可以帮助你添加更多的可搜索字段。
示例：
export default {
+ plugins: [
+ searchPlugin({
+ // 允许搜索 Frontmatter 中的 \`tags\`
+ getExtraFields: (page) => page.frontmatter.tags ?? [],
+ }),
+ ],
+}
+你可以通过 CSS 变量来自定义搜索框的样式：
:root {
+ --search-bg-color: #ffffff;
+ --search-accent-color: #3eaf7c;
+ --search-text-color: #2c3e50;
+ --search-border-color: #eaecef;
+ --search-item-text-color: #5d81a5;
+ --search-item-focus-bg-color: #f3f4f5;
+ --search-input-width: 8rem;
+ --search-result-width: 20rem;
+}
+详情：
该插件会全局注册一个 <SearchBox /> 组件，你可以不传入任何 Props 来使用它。
将该组件放置在你想要显示搜索框的地方。例如，默认主题将这个组件放在了导航栏的末尾。
提示
该组件主要用于主题开发。在大多数情况下你不需要直接使用该组件。
Provide local search to your documentation site.
TIP
Default theme will add search box to the navbar once you configure this plugin correctly.
This plugin may not be used directly in other themes, so you'd better refer to the documentation of your theme for more details.
npm i -D @vuepress/plugin-search@next
+import { searchPlugin } from '@vuepress/plugin-search'
+
+export default {
+ plugins: [
+ searchPlugin({
+ // options
+ }),
+ ],
+}
+This plugin will generate search index from your pages locally, and load the search index file when users enter your site. In other words, this is a lightweight built-in search which does not require any external requests.
`,7),u=n(`Type: Record<string, { placeholder: string }>
Details:
The text of the search box in different locales.
If this option is not specified, it will fallback to default text.
Example:
export default {
+ plugins: [
+ searchPlugin({
+ locales: {
+ '/': {
+ placeholder: 'Search',
+ },
+ '/zh/': {
+ placeholder: '搜索',
+ },
+ },
+ }),
+ ],
+}
+(string | HotKeyOptions)[]export interface HotKeyOptions {
+ /**
+ * Value of \`event.key\` to trigger the hot key
+ */
+ key: string;
+ /**
+ * Whether to press \`event.altKey\` at the same time
+ *
+ * @default false
+ */
+ alt?: boolean;
+ /**
+ * Whether to press \`event.ctrlKey\` at the same time
+ *
+ * @default false
+ */
+ ctrl?: boolean;
+ /**
+ * Whether to press \`event.shiftKey\` at the same time
+ *
+ * @default false
+ */
+ shift?: boolean;
+}
+Type: number
Default: 5
Details:
Specify the maximum number of search results.
Type: (page: Page) => boolean
Default: () => true
Details:
A function to determine whether a page should be included in the search index.
true to include the page.false to exclude the page.Example:
export default {
+ plugins: [
+ searchPlugin({
+ // exclude the homepage
+ isSearchable: (page) => page.path !== '/',
+ }),
+ ],
+}
+Type: (page: Page) => string[]
Default: () => []
Details:
A function to add extra fields to the search index of a page.
By default, this plugin will use page title and headers as the search index. This option could help you to add more searchable fields.
Example:
export default {
+ plugins: [
+ searchPlugin({
+ // allow searching the \`tags\` frontmatter
+ getExtraFields: (page) => page.frontmatter.tags ?? [],
+ }),
+ ],
+}
+You can customize the style of the search box via CSS variables:
:root {
+ --search-bg-color: #ffffff;
+ --search-accent-color: #3eaf7c;
+ --search-text-color: #2c3e50;
+ --search-border-color: #eaecef;
+ --search-item-text-color: #5d81a5;
+ --search-item-focus-bg-color: #f3f4f5;
+ --search-input-width: 8rem;
+ --search-result-width: 20rem;
+}
+Details:
This plugin will register a <SearchBox /> component globally, and you can use it without any props.
Put this component to where you want to place the search box. For example, default theme puts this component to the end of the navbar.
TIP
This component is mainly used for theme development. You don't need to use it directly in most cases.
The following functions are available on both Node.js and Client.
Encode/decode and zip/unzip data.
This is useful in markdown plugins when you want to encode string content and pass it to the component through props.
You may simply achieve this with encodeURIComponent and decodeURIComponent, but it can be very large if the content contains lots of special characters.
So we provide encodeData and decodeData to zip and encode content.
export const encodeData: (
+ data: string,
+ level: DeflateOptions['level'] = 6,
+) => string
+
+export const decodeData: (compressed: string) => string
+const content = \`
+{
+ "type": "bar",
+ "data": {
+ "labels": ["Red", "Blue", "Yellow", "Green", "Purple", "Orange"],
+ "datasets": [
+ {
+ "label": "# of Votes",
+ "data": [12, 19, 3, 5, 2, 3],
+ "backgroundColor": [
+ "rgba(255, 99, 132, 0.2)",
+ "rgba(54, 162, 235, 0.2)",
+ "rgba(255, 206, 86, 0.2)",
+ "rgba(75, 192, 192, 0.2)",
+ "rgba(153, 102, 255, 0.2)",
+ "rgba(255, 159, 64, 0.2)"
+ ],
+ "borderColor": [
+ "rgba(255, 99, 132, 1)",
+ "rgba(54, 162, 235, 1)",
+ "rgba(255, 206, 86, 1)",
+ "rgba(75, 192, 192, 1)",
+ "rgba(153, 102, 255, 1)",
+ "rgba(255, 159, 64, 1)"
+ ],
+ "borderWidth": 1
+ }
+ ]
+ },
+ "options": {
+ "scales": {
+ "y": {
+ "beginAtZero": true
+ }
+ }
+ }
+}
+\`
+
+const prop = encodeData(content) // "eJyNUsFOwzAMve8rrHABKZqWlg5WxAE4cARxAMHEIV1NmQhNlaaCCe3fcdKtW0sLWGpjxy/v+UV512mlcIyfhTa2hHP4GgHYVYExsEQaxqlMpZWxbwAomaAqY5izO0wZB3apKnTrIyqlP1x2bRBzl9xWplC+eWNkniF7dmw1X4nWsfgaNtwNP2kfgH6Be22x9CPUUQ8yFwEHMeMQcog4UBFuiF0kcvGWGV3l6ZVW2uw0XDCTJfIwiOjYjAhESIcn4+BoT2MLio6pP6V+EBJ6AOSZgsmUwyl9A6ATwoiZn3lYTkTkRkycnuP8TU9ENPqUxuuA9i9BmxTNPy9A/G2/F9I23wtpW++FdIwPKzW2W5Afph+WqX2NQWz313XicT7XhV3qnB5f/ejKhVTYVACrXUqUmC3zC/uERsdgTYUdVr/Qb302+gZxe7S/"
+
+decodeData(prop) // will be the original content
+
+// if you use \`encodeURIComponent\`, it will be much longer
+encodeURIComponent(content) // '%0A%7B%0A%20%20%22type%22%3A%20%22bar%22%2C%0A%20%20%22data%22%3A%20%7B%0A%20%20%20%20%22labels%22%3A%20%5B%22Red%22%2C%20%22Blue%22%2C%20%22Yellow%22%2C%20%22Green%22%2C%20%22Purple%22%2C%20%22Orange%22%5D%2C%0A%20%20%20%20%22datasets%22%3A%20%5B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%22label%22%3A%20%22%23%20of%20Votes%22%2C%0A%20%20%20%20%20%20%20%20%22data%22%3A%20%5B12%2C%2019%2C%203%2C%205%2C%202%2C%203%5D%2C%0A%20%20%20%20%20%20%20%20%22backgroundColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%200.2)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%201)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderWidth%22%3A%201%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%0A%20%20%7D%2C%0A%20%20%22options%22%3A%20%7B%0A%20%20%20%20%22scales%22%3A%20%7B%0A%20%20%20%20%20%20%22y%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22beginAtZero%22%3A%20true%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A'
+isDef(x): Check if x is defined.isBoolean(x): Check if x is a boolean.isString(x): Check if x is a string.isNumber(x): Check if x is a number.isPlainObject(x): Check if x is a plain object.isArray(x): Check if x is an array.isFunction(x): Check if x is a function.isRegExp(x): Check if x is a regular expression.startsWith(a, b): Check if string a starts with string b.endsWith(a, b): Check if string a ends with string b.Return false if a is not a string.
keys(x): Return an array of keys of object x.
values(x): Return an array of values of object x.
entries(x): Convert object x to an array of key-value pairs.
fromEntries(x): Convert an array of key-value pairs x to an object.
deepAssign(x, y, ...): A deep version of Object.assign.
// or @vuepress/helper/client
+import { deepAssign } from '@vuepress/helper'
+
+const defaultOptions = {
+ optionA: {
+ optionA1: 'defaultOptionA1',
+ optionA2: 'defaultOptionA2',
+ optionA3: 'defaultOptionA3',
+ },
+ optionB: true,
+ optionC: 'optionC',
+}
+
+const userOptions = {
+ optionA: {
+ optionA1: 'optionA1',
+ optionA2: 'optionA2',
+ },
+ optionB: false,
+}
+
+deepAssign(defaultOptions, userOptions)
+// {
+// optionA: {
+// optionA1: "optionA1",
+// optionA2: "optionA2",
+// optionA3: "defaultOptionA3",
+// },
+// optionB: false,
+// optionC: "optionC",
+// }
+getDate(x): Convert input x to a date. It can support Date, timestamp, and date string. The support degree of date string depends on the Date.parse support degree of the environment. Return null when it cannot be converted to a date.
getDate('2021-01-01') // a Date object represents 2021-01-01
+getDate(1609459200000) // a Date object represents 2021-01-01
+getDate('2021-01-01T00:00:00.000Z') // a Date object represents 2021-01-01
+getDate('2021/01/01') // a Date object represents 2021-01-01 (might be null in some browsers)
+getDate('invalid date') // null
+getDate(undefined) // null
+getDate(-32) // null
+dateSorter: Sort the values that can be converted to dates from new to old, and the values that cannot be converted to dates will be at the end.
const arr = [
+ '2020-01-01',
+ 1609459200000,
+ '2022-01-01T00:00:00.000Z',
+ '2023/01/01',
+ 'invalid date',
+ undefined,
+ -32,
+]
+
+arr.sort(dateSorter)
+// [
+// '2023/01/01',
+// '2022-01-01T00:00:00.000Z',
+// 1609459200000,
+// '2020-01-01',
+// 'invalid date',
+// undefined,
+// -32,
+// ]
+isLinkHttp(x): Check if x is a valid HTTP URL.isLinkWithProtocol(x): Check if x is a valid URL with protocol.isLinkExternal(x): Check if x is a valid external URL.isLinkAbsolute(x): Check if x is a valid absolute URL.ensureEndingSlash(x): Ensure x ends with a slash.ensureLeadingSlash(x): Ensure x starts with a slash.removeEndingSlash(x): Ensure x does not end with a slash.removeLeadingSlash(x): Ensure x does not start with a slash.以下函数在 Node.js 和客户端上均可用。
此方法在 MarkdownIt 插件中很有用。有些时候你可能需要在 Markdown 插件中生成组件，并将复杂的数据写入到组件属性中，一个通常做法是使用 JSON.stringify + encodeURIComponent，并在客户端 decodeURIComponent + JSON.parse。但如果内容包含很多特殊字符，转换结果会很长。
所以我们提供 encodeData 和 decodeData 来压缩和编码内容。
export const encodeData: (
+ data: string,
+ level: DeflateOptions['level'] = 6,
+) => string
+
+export const decodeData: (compressed: string) => string
+const content = \`
+{
+ "type": "bar",
+ "data": {
+ "labels": ["Red", "Blue", "Yellow", "Green", "Purple", "Orange"],
+ "datasets": [
+ {
+ "label": "# of Votes",
+ "data": [12, 19, 3, 5, 2, 3],
+ "backgroundColor": [
+ "rgba(255, 99, 132, 0.2)",
+ "rgba(54, 162, 235, 0.2)",
+ "rgba(255, 206, 86, 0.2)",
+ "rgba(75, 192, 192, 0.2)",
+ "rgba(153, 102, 255, 0.2)",
+ "rgba(255, 159, 64, 0.2)"
+ ],
+ "borderColor": [
+ "rgba(255, 99, 132, 1)",
+ "rgba(54, 162, 235, 1)",
+ "rgba(255, 206, 86, 1)",
+ "rgba(75, 192, 192, 1)",
+ "rgba(153, 102, 255, 1)",
+ "rgba(255, 159, 64, 1)"
+ ],
+ "borderWidth": 1
+ }
+ ]
+ },
+ "options": {
+ "scales": {
+ "y": {
+ "beginAtZero": true
+ }
+ }
+ }
+}
+\`
+
+const prop = encodeData(content) // "eJyNUsFOwzAMve8rrHABKZqWlg5WxAE4cARxAMHEIV1NmQhNlaaCCe3fcdKtW0sLWGpjxy/v+UV512mlcIyfhTa2hHP4GgHYVYExsEQaxqlMpZWxbwAomaAqY5izO0wZB3apKnTrIyqlP1x2bRBzl9xWplC+eWNkniF7dmw1X4nWsfgaNtwNP2kfgH6Be22x9CPUUQ8yFwEHMeMQcog4UBFuiF0kcvGWGV3l6ZVW2uw0XDCTJfIwiOjYjAhESIcn4+BoT2MLio6pP6V+EBJ6AOSZgsmUwyl9A6ATwoiZn3lYTkTkRkycnuP8TU9ENPqUxuuA9i9BmxTNPy9A/G2/F9I23wtpW++FdIwPKzW2W5Afph+WqX2NQWz313XicT7XhV3qnB5f/ejKhVTYVACrXUqUmC3zC/uERsdgTYUdVr/Qb302+gZxe7S/"
+
+decodeData(prop) // will be the original content
+
+// if you use \`encodeURIComponent\`, it will be much longer
+encodeURIComponent(content) // '%0A%7B%0A%20%20%22type%22%3A%20%22bar%22%2C%0A%20%20%22data%22%3A%20%7B%0A%20%20%20%20%22labels%22%3A%20%5B%22Red%22%2C%20%22Blue%22%2C%20%22Yellow%22%2C%20%22Green%22%2C%20%22Purple%22%2C%20%22Orange%22%5D%2C%0A%20%20%20%20%22datasets%22%3A%20%5B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%22label%22%3A%20%22%23%20of%20Votes%22%2C%0A%20%20%20%20%20%20%20%20%22data%22%3A%20%5B12%2C%2019%2C%203%2C%205%2C%202%2C%203%5D%2C%0A%20%20%20%20%20%20%20%20%22backgroundColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%200.2)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%201)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderWidth%22%3A%201%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%0A%20%20%7D%2C%0A%20%20%22options%22%3A%20%7B%0A%20%20%20%20%22scales%22%3A%20%7B%0A%20%20%20%20%20%20%22y%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22beginAtZero%22%3A%20true%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A'
+isDef(x): 判断 x 是否定义。isBoolean(x): 判断 x 是否为布尔值。isString(x): 判断 x 是否为字符串。isNumber(x): 判断 x 是否为数字。isPlainObject(x): 判断值是否为纯对象。isArray(x): 判断 x 是否为数组isFunction(x): 判断 x 是否为函数。isRegExp(x): 判断 x 是否为正则表达式startsWith(a, b): 判断字符串 a 是否以指定字符串 b 开头endsWith(a, b): 判断字符串 a 是否以指定字符串 b 结尾当 a 不是字符串时返回 false
keys(x): 以数组形式返回对象 x 的键
values(x): 以数组形式返回对象 x 的值
entries(x): 将对象 x 转换为键值对数组。
fromEntries(x): 将键值对数组 x 转换为对象。
deepAssign(x, y, ...): Object.assign 的深度版本。
// or @vuepress/helper/client
+import { deepAssign } from '@vuepress/helper'
+
+const defaultOptions = {
+ optionA: {
+ optionA1: 'defaultOptionA1',
+ optionA2: 'defaultOptionA2',
+ optionA3: 'defaultOptionA3',
+ },
+ optionB: true,
+ optionC: 'optionC',
+}
+
+const userOptions = {
+ optionA: {
+ optionA1: 'optionA1',
+ optionA2: 'optionA2',
+ },
+ optionB: false,
+}
+
+deepAssign(defaultOptions, userOptions)
+// {
+// optionA: {
+// optionA1: "optionA1",
+// optionA2: "optionA2",
+// optionA3: "defaultOptionA3",
+// },
+// optionB: false,
+// optionC: "optionC",
+// }
+getDate(x): 将输入 x 转换为日期，可以支持 Date，时间戳，日期字符串。日期字符串的支持度以环境的 Date.parse 支持度为准。当不能转换为日期时返回 null
getDate('2021-01-01') // a Date object represents 2021-01-01
+getDate(1609459200000) // a Date object represents 2021-01-01
+getDate('2021-01-01T00:00:00.000Z') // a Date object represents 2021-01-01
+getDate('2021/01/01') // a Date object represents 2021-01-01 (might be null in some browsers)
+getDate('invalid date') // null
+getDate(undefined) // null
+getDate(-32) // null
+dateSorter: 将可转换为日期的值从新到旧排序，不能转换为日期的值会在最后。
const arr = [
+ '2020-01-01',
+ 1609459200000,
+ '2022-01-01T00:00:00.000Z',
+ '2023/01/01',
+ 'invalid date',
+ undefined,
+ -32,
+]
+
+arr.sort(dateSorter)
+// [
+// '2023/01/01',
+// '2022-01-01T00:00:00.000Z',
+// 1609459200000,
+// '2020-01-01',
+// 'invalid date',
+// undefined,
+// -32,
+// ]
+isLinkHttp(x): x 是否是有效的 HTTP URL。isLinkWithProtocol(x): x 是否是有效的带有协议的 URL。isLinkExternal(x): x 是否是有效的外部 URL。isLinkAbsolute(x): x 是否是有效的绝对 URL。ensureEndingSlash(x): 确保 x 以斜杠结尾。ensureLeadingSlash(x): 确保 x 以斜杠开头。removeEndingSlash(x): 确保 x 不以斜杠结尾。removeLeadingSlash(x): 确保 x 不以斜杠开头。npm i -D @vuepress/plugin-shiki@next
+import { shikiPlugin } from '@vuepress/plugin-shiki'
+
+export default {
+ plugins: [
+ shikiPlugin({
+ // 配置项
+ langs: ['ts', 'json', 'vue', 'md', 'bash', 'diff'],
+ }),
+ ],
+}
+类型： ShikiTheme
默认值： 'nord'
详情：
Shiki 的主题。
该配置项会被传递到 Shiki 的 codeToHtml() 方法中。
npm i -D @vuepress/plugin-shiki@next
+import { shikiPlugin } from '@vuepress/plugin-shiki'
+
+export default {
+ plugins: [
+ shikiPlugin({
+ // options
+ langs: ['ts', 'json', 'vue', 'md', 'bash', 'diff'],
+ }),
+ ],
+}
+Type: ShikiTheme
Default: 'nord'
Details:
Theme of Shiki.
This option will be forwarded to codeToHtml() method of Shiki.
Users can customize style variables via a palette file, and add extra styles via a style file.
The path of the palette file is .vuepress/styles/palette.scss.
You can make use of it to override predefined SASS variables of the default theme.
// responsive breakpoints
+$MQNarrow: 959px !default;
+$MQMobile: 719px !default;
+$MQMobileNarrow: 419px !default;
+The path of the style file is .vuepress/styles/index.scss.
You can add extra styles here, or override the default styles:
:root {
+ scroll-behavior: smooth;
+}
+You can also make use of it to override predefined CSS variables of the default theme.
:root {
+ // brand colors
+ --c-brand: #3eaf7c;
+ --c-brand-light: #4abf8a;
+
+ // background colors
+ --c-bg: #ffffff;
+ --c-bg-light: #f3f4f5;
+ --c-bg-lighter: #eeeeee;
+ --c-bg-dark: #ebebec;
+ --c-bg-darker: #e6e6e6;
+ --c-bg-navbar: var(--c-bg);
+ --c-bg-sidebar: var(--c-bg);
+ --c-bg-arrow: #cccccc;
+
+ // text colors
+ --c-text: #2c3e50;
+ --c-text-accent: var(--c-brand);
+ --c-text-light: #3a5169;
+ --c-text-lighter: #4e6e8e;
+ --c-text-lightest: #6a8bad;
+ --c-text-quote: #999999;
+
+ // border colors
+ --c-border: #eaecef;
+ --c-border-dark: #dfe2e5;
+
+ // custom container colors
+ --c-tip: #42b983;
+ --c-tip-bg: var(--c-bg-light);
+ --c-tip-title: var(--c-text);
+ --c-tip-text: var(--c-text);
+ --c-tip-text-accent: var(--c-text-accent);
+ --c-warning: #ffc310;
+ --c-warning-bg: #fffae3;
+ --c-warning-bg-light: #fff3ba;
+ --c-warning-bg-lighter: #fff0b0;
+ --c-warning-border-dark: #f7dc91;
+ --c-warning-details-bg: #fff5ca;
+ --c-warning-title: #f1b300;
+ --c-warning-text: #746000;
+ --c-warning-text-accent: #edb100;
+ --c-warning-text-light: #c1971c;
+ --c-warning-text-quote: #ccab49;
+ --c-danger: #f11e37;
+ --c-danger-bg: #ffe0e0;
+ --c-danger-bg-light: #ffcfde;
+ --c-danger-bg-lighter: #ffc9c9;
+ --c-danger-border-dark: #f1abab;
+ --c-danger-details-bg: #ffd4d4;
+ --c-danger-title: #ed1e2c;
+ --c-danger-text: #660000;
+ --c-danger-text-accent: #bd1a1a;
+ --c-danger-text-light: #b5474d;
+ --c-danger-text-quote: #c15b5b;
+ --c-details-bg: #eeeeee;
+
+ // badge component colors
+ --c-badge-tip: var(--c-tip);
+ --c-badge-warning: #ecc808;
+ --c-badge-warning-text: var(--c-bg);
+ --c-badge-danger: #dc2626;
+ --c-badge-danger-text: var(--c-bg);
+
+ // code group colors
+ --c-code-group-tab-title: rgba(255, 255, 255, 0.9);
+ --c-code-group-tab-bg: var(--code-bg-color);
+ --c-code-group-tab-outline: var(var(--c-code-group-tab-title));
+ --c-code-group-tab-active-border: var(--c-brand);
+
+ // transition vars
+ --t-color: 0.3s ease;
+ --t-transform: 0.3s ease;
+
+ // code blocks vars
+ --code-bg-color: #282c34;
+ --code-hl-bg-color: rgba(0, 0, 0, 0.66);
+ --code-ln-color: #9e9e9e;
+ --code-ln-wrapper-width: 3.5rem;
+
+ // font vars
+ --font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen,
+ Ubuntu, Cantarell, 'Fira Sans', 'Droid Sans', 'Helvetica Neue', sans-serif;
+ --font-family-code: Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono', monospace;
+
+ // layout vars
+ --navbar-height: 3.6rem;
+ --navbar-padding-v: 0.7rem;
+ --navbar-padding-h: 1.5rem;
+ --sidebar-width: 20rem;
+ --sidebar-width-mobile: calc(var(--sidebar-width) * 0.82);
+ --content-width: 740px;
+ --homepage-width: 960px;
+}
+
+// plugin-back-to-top
+.vp-back-to-top-button {
+ --back-to-top-color: var(--c-brand);
+ --back-to-top-color-hover: var(--c-brand-light);
+ --back-to-top-bg-color: var(--c-bg);
+}
+
+// plugin-catalog
+.vp-catalog-wrapper {
+ --catalog-bg-color: var(--c-bg);
+ --catalog-bg-secondary-color: var(--c-bg-dark);
+ --catalog-border-color: var(--c-border);
+ --catalog-active-color: var(--c-brand);
+ --catalog-hover-color: var(--c-brand-light);
+}
+
+// plugin-comment
+.waline-wrapper {
+ --waline-bg-color: var(--c-bg);
+ --waline-bg-color-light: var(--c-bg-light);
+ --waline-text-color: var(--c-color);
+ --waline-border: 1px solid var(--c-border);
+ --waline-border-color: var(--c-border);
+ --waline-theme-color: var(--c-brand);
+ --waline-active-color: var(--c-brand-light);
+}
+
+// plugin-docsearch
+.DocSearch {
+ --docsearch-primary-color: var(--c-brand);
+ --docsearch-text-color: var(--c-text);
+ --docsearch-highlight-color: var(--c-brand);
+ --docsearch-muted-color: var(--c-text-quote);
+ --docsearch-container-background: rgba(9, 10, 17, 0.8);
+ --docsearch-modal-background: var(--c-bg-light);
+ --docsearch-searchbox-background: var(--c-bg-lighter);
+ --docsearch-searchbox-focus-background: var(--c-bg);
+ --docsearch-searchbox-shadow: inset 0 0 0 2px var(--c-brand);
+ --docsearch-hit-color: var(--c-text-light);
+ --docsearch-hit-active-color: var(--c-bg);
+ --docsearch-hit-background: var(--c-bg);
+ --docsearch-hit-shadow: 0 1px 3px 0 var(--c-border-dark);
+ --docsearch-footer-background: var(--c-bg);
+}
+
+// plugin-external-link-icon
+.external-link-icon {
+ --external-link-icon-color: var(--c-text-quote);
+}
+
+// plugin-medium-zoom
+.medium-zoom-overlay {
+ --medium-zoom-bg-color: var(--c-bg);
+}
+
+// plugin-nprogress
+#nprogress {
+ --nprogress-color: var(--c-brand);
+}
+
+// plugin-photo-swipe
+body {
+ --photo-swipe-bullet: var(--c-bg);
+ --photo-swipe-bullet-active: var(--c-brand);
+}
+
+// plugin-pwa-popup
+body {
+ --pwa-text-color: var(--c-text);
+ --pwa-bg-color: var(--c-bg);
+ --pwa-border-color: var(--c-brand);
+ --pwa-btn-text-color: var(--c-bg);
+ --pwa-btn-bg-color: var(--c-brand);
+ --pwa-btn-hover-bg-color: var(--c-brand-light);
+}
+
+// plugin-redirect
+.language-modal-mask {
+ --redirect-bg-color: var(--c-bg);
+ --redirect-bg-color-light: var(--c-bg-light);
+ --redirect-bg-color-lighter: var(--c-bg-lighter);
+ --redirect-text-color: var(--c-text);
+ --redirect-primary-color: var(--c-brand);
+ --redirect-primary-hover-color: var(--c-brand-light);
+ --redirect-primary-text-color: var(--c-bg);
+}
+
+// plugin-search
+.search-box {
+ --search-bg-color: var(--c-bg);
+ --search-accent-color: var(--c-brand);
+ --search-text-color: var(--c-text);
+ --search-border-color: var(--c-border);
+
+ --search-item-text-color: var(--c-text-lighter);
+ --search-item-focus-bg-color: var(--c-bg-light);
+}
+html.dark {
+ // brand colors
+ --c-brand: #3aa675;
+ --c-brand-light: #349469;
+
+ // background colors
+ --c-bg: #22272e;
+ --c-bg-light: #2b313a;
+ --c-bg-lighter: #262c34;
+ --c-bg-dark: #343b44;
+ --c-bg-darker: #37404c;
+
+ // text colors
+ --c-text: #adbac7;
+ --c-text-light: #96a7b7;
+ --c-text-lighter: #8b9eb0;
+ --c-text-lightest: #8094a8;
+
+ // border colors
+ --c-border: #3e4c5a;
+ --c-border-dark: #34404c;
+
+ // custom container colors
+ --c-tip: #318a62;
+ --c-warning: #e0ad15;
+ --c-warning-bg: #2d2f2d;
+ --c-warning-bg-light: #423e2a;
+ --c-warning-bg-lighter: #44442f;
+ --c-warning-border-dark: #957c35;
+ --c-warning-details-bg: #39392d;
+ --c-warning-title: #fdca31;
+ --c-warning-text: #d8d96d;
+ --c-warning-text-accent: #ffbf00;
+ --c-warning-text-light: #ddb84b;
+ --c-warning-text-quote: #ccab49;
+ --c-danger: #fc1e38;
+ --c-danger-bg: #39232c;
+ --c-danger-bg-light: #4b2b35;
+ --c-danger-bg-lighter: #553040;
+ --c-danger-border-dark: #a25151;
+ --c-danger-details-bg: #482936;
+ --c-danger-title: #fc2d3b;
+ --c-danger-text: #ea9ca0;
+ --c-danger-text-accent: #fd3636;
+ --c-danger-text-light: #d9777c;
+ --c-danger-text-quote: #d56b6b;
+ --c-details-bg: #323843;
+
+ // badge component colors
+ --c-badge-warning: var(--c-warning);
+ --c-badge-warning-text: #3c2e05;
+ --c-badge-danger: var(--c-danger);
+ --c-badge-danger-text: #401416;
+
+ // code blocks vars
+ --code-hl-bg-color: #363b46;
+}
+
+// plugin-docsearch
+html.dark .DocSearch {
+ --docsearch-logo-color: var(--c-text);
+ --docsearch-modal-shadow: inset 1px 1px 0 0 #2c2e40, 0 3px 8px 0 #000309;
+ --docsearch-key-shadow: inset 0 -2px 0 0 #282d55, inset 0 0 1px 1px #51577d,
+ 0 2px 2px 0 rgba(3, 4, 9, 0.3);
+ --docsearch-key-gradient: linear-gradient(-225deg, #444950, #1c1e21);
+ --docsearch-footer-shadow: inset 0 1px 0 0 rgba(73, 76, 106, 0.5),
+ 0 -4px 8px 0 rgba(0, 0, 0, 0.2);
+}
+
+// plugin-pwa
+html.dark body {
+ --pwa-shadow-color: rgb(0 0 0 / 30%);
+ --pwa-content-color: #ccc;
+ --pwa-content-light-color: #999;
+}
+用户可以通过 palette 文件 来自定义样式变量，还可以通过 style 文件 来添加额外的样式。
Palette 文件的路径是 .vuepress/styles/palette.scss 。
你可以利用它来覆盖默认主题的预定义 SASS 变量。
// responsive breakpoints
+$MQNarrow: 959px !default;
+$MQMobile: 719px !default;
+$MQMobileNarrow: 419px !default;
+Style 文件的路径是 .vuepress/styles/index.scss 。
你可以在这里添加额外的样式，或者覆盖默认样式：
:root {
+ scroll-behavior: smooth;
+}
+你也可以利用它来覆盖默认主题的预定义 CSS 变量。
:root {
+ // brand colors
+ --c-brand: #3eaf7c;
+ --c-brand-light: #4abf8a;
+
+ // background colors
+ --c-bg: #ffffff;
+ --c-bg-light: #f3f4f5;
+ --c-bg-lighter: #eeeeee;
+ --c-bg-dark: #ebebec;
+ --c-bg-darker: #e6e6e6;
+ --c-bg-navbar: var(--c-bg);
+ --c-bg-sidebar: var(--c-bg);
+ --c-bg-arrow: #cccccc;
+
+ // text colors
+ --c-text: #2c3e50;
+ --c-text-accent: var(--c-brand);
+ --c-text-light: #3a5169;
+ --c-text-lighter: #4e6e8e;
+ --c-text-lightest: #6a8bad;
+ --c-text-quote: #999999;
+
+ // border colors
+ --c-border: #eaecef;
+ --c-border-dark: #dfe2e5;
+
+ // custom container colors
+ --c-tip: #42b983;
+ --c-tip-bg: var(--c-bg-light);
+ --c-tip-title: var(--c-text);
+ --c-tip-text: var(--c-text);
+ --c-tip-text-accent: var(--c-text-accent);
+ --c-warning: #ffc310;
+ --c-warning-bg: #fffae3;
+ --c-warning-bg-light: #fff3ba;
+ --c-warning-bg-lighter: #fff0b0;
+ --c-warning-border-dark: #f7dc91;
+ --c-warning-details-bg: #fff5ca;
+ --c-warning-title: #f1b300;
+ --c-warning-text: #746000;
+ --c-warning-text-accent: #edb100;
+ --c-warning-text-light: #c1971c;
+ --c-warning-text-quote: #ccab49;
+ --c-danger: #f11e37;
+ --c-danger-bg: #ffe0e0;
+ --c-danger-bg-light: #ffcfde;
+ --c-danger-bg-lighter: #ffc9c9;
+ --c-danger-border-dark: #f1abab;
+ --c-danger-details-bg: #ffd4d4;
+ --c-danger-title: #ed1e2c;
+ --c-danger-text: #660000;
+ --c-danger-text-accent: #bd1a1a;
+ --c-danger-text-light: #b5474d;
+ --c-danger-text-quote: #c15b5b;
+ --c-details-bg: #eeeeee;
+
+ // badge component colors
+ --c-badge-tip: var(--c-tip);
+ --c-badge-warning: #ecc808;
+ --c-badge-warning-text: var(--c-bg);
+ --c-badge-danger: #dc2626;
+ --c-badge-danger-text: var(--c-bg);
+
+ // code group colors
+ --c-code-group-tab-title: rgba(255, 255, 255, 0.9);
+ --c-code-group-tab-bg: var(--code-bg-color);
+ --c-code-group-tab-outline: var(var(--c-code-group-tab-title));
+ --c-code-group-tab-active-border: var(--c-brand);
+
+ // transition vars
+ --t-color: 0.3s ease;
+ --t-transform: 0.3s ease;
+
+ // code blocks vars
+ --code-bg-color: #282c34;
+ --code-hl-bg-color: rgba(0, 0, 0, 0.66);
+ --code-ln-color: #9e9e9e;
+ --code-ln-wrapper-width: 3.5rem;
+
+ // font vars
+ --font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen,
+ Ubuntu, Cantarell, 'Fira Sans', 'Droid Sans', 'Helvetica Neue', sans-serif;
+ --font-family-code: Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono', monospace;
+
+ // layout vars
+ --navbar-height: 3.6rem;
+ --navbar-padding-v: 0.7rem;
+ --navbar-padding-h: 1.5rem;
+ --sidebar-width: 20rem;
+ --sidebar-width-mobile: calc(var(--sidebar-width) * 0.82);
+ --content-width: 740px;
+ --homepage-width: 960px;
+}
+
+// plugin-back-to-top
+.vp-back-to-top-button {
+ --back-to-top-color: var(--c-brand);
+ --back-to-top-color-hover: var(--c-brand-light);
+ --back-to-top-bg-color: var(--c-bg);
+}
+
+// plugin-catalog
+.vp-catalog-wrapper {
+ --catalog-bg-color: var(--c-bg);
+ --catalog-bg-secondary-color: var(--c-bg-dark);
+ --catalog-border-color: var(--c-border);
+ --catalog-active-color: var(--c-brand);
+ --catalog-hover-color: var(--c-brand-light);
+}
+
+// plugin-comment
+.waline-wrapper {
+ --waline-bg-color: var(--c-bg);
+ --waline-bg-color-light: var(--c-bg-light);
+ --waline-text-color: var(--c-color);
+ --waline-border: 1px solid var(--c-border);
+ --waline-border-color: var(--c-border);
+ --waline-theme-color: var(--c-brand);
+ --waline-active-color: var(--c-brand-light);
+}
+
+// plugin-docsearch
+.DocSearch {
+ --docsearch-primary-color: var(--c-brand);
+ --docsearch-text-color: var(--c-text);
+ --docsearch-highlight-color: var(--c-brand);
+ --docsearch-muted-color: var(--c-text-quote);
+ --docsearch-container-background: rgba(9, 10, 17, 0.8);
+ --docsearch-modal-background: var(--c-bg-light);
+ --docsearch-searchbox-background: var(--c-bg-lighter);
+ --docsearch-searchbox-focus-background: var(--c-bg);
+ --docsearch-searchbox-shadow: inset 0 0 0 2px var(--c-brand);
+ --docsearch-hit-color: var(--c-text-light);
+ --docsearch-hit-active-color: var(--c-bg);
+ --docsearch-hit-background: var(--c-bg);
+ --docsearch-hit-shadow: 0 1px 3px 0 var(--c-border-dark);
+ --docsearch-footer-background: var(--c-bg);
+}
+
+// plugin-external-link-icon
+.external-link-icon {
+ --external-link-icon-color: var(--c-text-quote);
+}
+
+// plugin-medium-zoom
+.medium-zoom-overlay {
+ --medium-zoom-bg-color: var(--c-bg);
+}
+
+// plugin-nprogress
+#nprogress {
+ --nprogress-color: var(--c-brand);
+}
+
+// plugin-photo-swipe
+body {
+ --photo-swipe-bullet: var(--c-bg);
+ --photo-swipe-bullet-active: var(--c-brand);
+}
+
+// plugin-pwa-popup
+body {
+ --pwa-text-color: var(--c-text);
+ --pwa-bg-color: var(--c-bg);
+ --pwa-border-color: var(--c-brand);
+ --pwa-btn-text-color: var(--c-bg);
+ --pwa-btn-bg-color: var(--c-brand);
+ --pwa-btn-hover-bg-color: var(--c-brand-light);
+}
+
+// plugin-redirect
+.language-modal-mask {
+ --redirect-bg-color: var(--c-bg);
+ --redirect-bg-color-light: var(--c-bg-light);
+ --redirect-bg-color-lighter: var(--c-bg-lighter);
+ --redirect-text-color: var(--c-text);
+ --redirect-primary-color: var(--c-brand);
+ --redirect-primary-hover-color: var(--c-brand-light);
+ --redirect-primary-text-color: var(--c-bg);
+}
+
+// plugin-search
+.search-box {
+ --search-bg-color: var(--c-bg);
+ --search-accent-color: var(--c-brand);
+ --search-text-color: var(--c-text);
+ --search-border-color: var(--c-border);
+
+ --search-item-text-color: var(--c-text-lighter);
+ --search-item-focus-bg-color: var(--c-bg-light);
+}
+html.dark {
+ // brand colors
+ --c-brand: #3aa675;
+ --c-brand-light: #349469;
+
+ // background colors
+ --c-bg: #22272e;
+ --c-bg-light: #2b313a;
+ --c-bg-lighter: #262c34;
+ --c-bg-dark: #343b44;
+ --c-bg-darker: #37404c;
+
+ // text colors
+ --c-text: #adbac7;
+ --c-text-light: #96a7b7;
+ --c-text-lighter: #8b9eb0;
+ --c-text-lightest: #8094a8;
+
+ // border colors
+ --c-border: #3e4c5a;
+ --c-border-dark: #34404c;
+
+ // custom container colors
+ --c-tip: #318a62;
+ --c-warning: #e0ad15;
+ --c-warning-bg: #2d2f2d;
+ --c-warning-bg-light: #423e2a;
+ --c-warning-bg-lighter: #44442f;
+ --c-warning-border-dark: #957c35;
+ --c-warning-details-bg: #39392d;
+ --c-warning-title: #fdca31;
+ --c-warning-text: #d8d96d;
+ --c-warning-text-accent: #ffbf00;
+ --c-warning-text-light: #ddb84b;
+ --c-warning-text-quote: #ccab49;
+ --c-danger: #fc1e38;
+ --c-danger-bg: #39232c;
+ --c-danger-bg-light: #4b2b35;
+ --c-danger-bg-lighter: #553040;
+ --c-danger-border-dark: #a25151;
+ --c-danger-details-bg: #482936;
+ --c-danger-title: #fc2d3b;
+ --c-danger-text: #ea9ca0;
+ --c-danger-text-accent: #fd3636;
+ --c-danger-text-light: #d9777c;
+ --c-danger-text-quote: #d56b6b;
+ --c-details-bg: #323843;
+
+ // badge component colors
+ --c-badge-warning: var(--c-warning);
+ --c-badge-warning-text: #3c2e05;
+ --c-badge-danger: var(--c-danger);
+ --c-badge-danger-text: #401416;
+
+ // code blocks vars
+ --code-hl-bg-color: #363b46;
+}
+
+// plugin-docsearch
+html.dark .DocSearch {
+ --docsearch-logo-color: var(--c-text);
+ --docsearch-modal-shadow: inset 1px 1px 0 0 #2c2e40, 0 3px 8px 0 #000309;
+ --docsearch-key-shadow: inset 0 -2px 0 0 #282d55, inset 0 0 1px 1px #51577d,
+ 0 2px 2px 0 rgba(3, 4, 9, 0.3);
+ --docsearch-key-gradient: linear-gradient(-225deg, #444950, #1c1e21);
+ --docsearch-footer-shadow: inset 0 1px 0 0 rgba(73, 76, 106, 0.5),
+ 0 -4px 8px 0 rgba(0, 0, 0, 0.2);
+}
+
+// plugin-pwa
+html.dark body {
+ --pwa-shadow-color: rgb(0 0 0 / 30%);
+ --pwa-content-color: #ccc;
+ --pwa-content-light-color: #999;
+}
+This plugin is mainly used to develop themes, and has been integrated into the default theme. You won't need to use it directly in most cases.
For theme authors, this plugin will help you to use the same i18n mechanism as VuePress and the default theme. But if you don't want to provide i18n support, or you want to implement in your own way, you don't need this plugin.
npm i -D @vuepress/plugin-theme-data@next
+import { themeDataPlugin } from '@vuepress/plugin-theme-data'
+
+export default {
+ plugins: [
+ themeDataPlugin({
+ // options
+ }),
+ ],
+}
+Type: ThemeData
Default: {}
Details:
The theme data object that you want to use in client side.
You can provide theme data in Node side via this option, and use it in client side via useThemeData and useThemeLocaleData.
Example:
export default {
+ plugins: [
+ themeDataPlugin({
+ themeData: {
+ foo: 'foo',
+ locales: {
+ '/zh/': {
+ foo: 'zh-foo',
+ },
+ },
+ },
+ }),
+ ],
+}
+WARNING
The theme data object will be processed by JSON.stringify() before forwarding to client side, so you should ensure that you are providing a JSON-friendly object.
Details:
Returns the theme data ref object.
The value is provided by themeData option.
Example:
import { useThemeData } from '@vuepress/plugin-theme-data/client'
+import type { ThemeData } from '@vuepress/plugin-theme-data/client'
+
+type MyThemeData = ThemeData<{
+ foo: string
+}>
+
+export default {
+ setup() {
+ const themeData = useThemeData<MyThemeData>()
+ console.log(themeData.value)
+ },
+}
+Details:
Returns the theme data ref object in current locale.
The properties of current locale has been merged into the root-level properties.
Example:
import { useThemeLocaleData } from '@vuepress/plugin-theme-data/client'
+import type { ThemeData } from '@vuepress/plugin-theme-data/client'
+
+type MyThemeData = ThemeData<{
+ foo: string
+}>
+
+export default {
+ setup() {
+ const themeLocaleData = useThemeLocaleData<MyThemeData>()
+ console.log(themeLocaleData.value)
+ },
+}
+该插件主要用于开发主题，并且已经集成到默认主题中。大部分情况下你不需要直接使用它。
对于主题作者，该插件可以提供与 VuePress 及默认主题相同的多语言支持机制。但是如果你的主题不需要提供多语言支持，或者你想用你自己的方式来实现多语言支持，那么你不需要使用该插件。
npm i -D @vuepress/plugin-theme-data@next
+import { themeDataPlugin } from '@vuepress/plugin-theme-data'
+
+export default {
+ plugins: [
+ themeDataPlugin({
+ // 配置项
+ }),
+ ],
+}
+类型： ThemeData
默认值： {}
详情：
你希望在 Client 端中使用的主题数据对象。
你可以通过该配置项，在 Node 端提供主题数据，然后在客户端通过 useThemeData 和 useThemeLocaleData 来使用主题数据。
示例：
export default {
+ plugins: [
+ themeDataPlugin({
+ themeData: {
+ foo: 'foo',
+ locales: {
+ '/zh/': {
+ foo: 'zh-foo',
+ },
+ },
+ },
+ }),
+ ],
+}
+注意
主题数据对象在传递到客户端之前，会使用 JSON.stringify() 进行处理，因此你需要保证你提供的是一个可以被 JSON 序列化的对象。
详情：
返回主题数据的 Ref 对象。
数据是通过 themeData 配置项提供的。
示例：
import { useThemeData } from '@vuepress/plugin-theme-data/client'
+import type { ThemeData } from '@vuepress/plugin-theme-data/client'
+
+type MyThemeData = ThemeData<{
+ foo: string
+}>
+
+export default {
+ setup() {
+ const themeData = useThemeData<MyThemeData>()
+ console.log(themeData.value)
+ },
+}
+详情：
返回当前 locale 下主题数据的 Ref 对象。
当前 locale 中的字段已被合并到顶层字段中。
示例：
import { useThemeLocaleData } from '@vuepress/plugin-theme-data/client'
+import type { ThemeData } from '@vuepress/plugin-theme-data/client'
+
+type MyThemeData = ThemeData<{
+ foo: string
+}>
+
+export default {
+ setup() {
+ const themeLocaleData = useThemeLocaleData<MyThemeData>()
+ console.log(themeLocaleData.value)
+ },
+}
+This plugin will provide a table-of-contents (TOC) component.
npm i -D @vuepress/plugin-toc@next
+import { tocPlugin } from '@vuepress/plugin-toc'
+
+export default {
+ plugins: [
+ tocPlugin({
+ // options
+ }),
+ ],
+}
+<!-- markdown toc syntax -->
+
+[[toc]]
+
+<!-- vue toc component -->
+<Toc />
+Both of them can be pre-rendered correctly in build mode. However, there are some differences between them.
The markdown syntax [[toc]] could only be used in markdown files. It is parsed by markdown-it, and the generated TOC is static content.
The component <Toc/> could be used in both markdown files and vue files. It is loaded by vue, and the generated TOC is a vue component.
Therefore, this plugin is more useful for theme developers.
Type: string
Default: 'Toc'
Details:
Specify the name of the TOC component.
Type: Partial<TocPropsOptions>
Default: {}
Details:
Override the default values of the component options prop.
The TOC component also accepts props for customization.
<template>
+ <Toc :headers="headers" :options="options" />
+</template>
+PageHeader[]interface PageHeader {
+ level: number
+ title: string
+ slug: string
+ children: PageHeader[]
+}
+Details:
Specify the headers array to render.
If this prop is not specified, the headers of current page will be used.
Partial<TocPropsOptions>interface TocPropsOptions {
+ containerTag: string
+ containerClass: string
+ listClass: string
+ itemClass: string
+ linkTag: 'a' | 'RouterLink' | 'RouteLink'
+ linkClass: string
+ linkActiveClass: string
+ linkChildrenActiveClass: string
+}
+Default:
Following default values can be overridden by defaultPropsOptions.
const defaultOptions = {
+ containerTag: 'nav',
+ containerClass: 'vuepress-toc',
+ listClass: 'vuepress-toc-list',
+ itemClass: 'vuepress-toc-item',
+ linkTag: 'RouteLink',
+ linkClass: 'vuepress-toc-link',
+ linkActiveClass: 'active',
+ linkChildrenActiveClass: 'active',
+}
+Details:
Customize the TOC component.
If the containerTag is set to an empty string '', the <nav> container will be removed totally.
Example:
The rendered TOC component with default options looks like:
<template>
+ <!-- container -->
+ <nav class="vuepress-toc">
+ <!-- list -->
+ <ul class="vuepress-toc-list">
+ <!-- item -->
+ <li class="vuepress-toc-item">
+ <!-- link -->
+ <RouteLink class="vuepress-toc-link" to="#foo">Foo</RouteLink>
+ </li>
+ <!-- item with children -->
+ <li class="vuepress-toc-item">
+ <!-- link (children active) -->
+ <RouteLink class="vuepress-toc-link active" to="#bar">Bar</RouteLink>
+ <!-- list (children) -->
+ <ul class="vuepress-toc-list">
+ <!-- item -->
+ <li class="vuepress-toc-item">
+ <!-- link (active) -->
+ <RouteLink class="vuepress-toc-link active" to="#bar-child">
+ Bar Child
+ </RouteLink>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </nav>
+</template>
+该插件会提供一个目录 (table-of-contents, TOC) 组件。
npm i -D @vuepress/plugin-toc@next
+import { tocPlugin } from '@vuepress/plugin-toc'
+
+export default {
+ plugins: [
+ tocPlugin({
+ // 配置项
+ }),
+ ],
+}
+<!-- Markdown 目录语法 -->
+
+[[toc]]
+
+<!-- Vue 目录组件 -->
+<Toc />
+在 Build 模式中，它们都可以被正确地预渲染。然而，它们之间存在一些区别。
Markdown 语法 [[toc]] 仅能在 Markdown 文件中使用。它是由 markdown-it 解析的，生成的目录是静态内容。
组件 <Toc/> 既可以用在 Markdown 文件中，也可以用在 Vue 文件中。它是由 Vue 加载的，生成的目录是一个 Vue 组件。
因此，该插件对于主题开发者来说更为有用。
类型： string
默认值： 'Toc'
详情：
指定目录组件的名称。
类型： Partial<TocPropsOptions>
默认值： {}
详情：
覆盖组件 options Prop 的默认值。
目录组件可以通过 Props 来进行自定义。
<template>
+ <Toc :headers="headers" :options="options" />
+</template>
+PageHeader[]interface PageHeader {
+ level: number
+ title: string
+ slug: string
+ children: PageHeader[]
+}
+详情：
指定要渲染的标题数组。
如果该 Prop 没有被设置，默认会使用当前页面的标题。
Partial<TocPropsOptions>interface TocPropsOptions {
+ containerTag: string
+ containerClass: string
+ listClass: string
+ itemClass: string
+ linkTag: 'a' | 'RouterLink' | 'RouteLink'
+ linkClass: string
+ linkActiveClass: string
+ linkChildrenActiveClass: string
+}
+默认值：
下列默认值可以用过 defaultPropsOptions 来覆盖：
const defaultOptions = {
+ containerTag: 'nav',
+ containerClass: 'vuepress-toc',
+ listClass: 'vuepress-toc-list',
+ itemClass: 'vuepress-toc-item',
+ linkTag: 'RouteLink',
+ linkClass: 'vuepress-toc-link',
+ linkActiveClass: 'active',
+ linkChildrenActiveClass: 'active',
+}
+详情：
自定义目录组件。
如果 containerTag 设置为空字符串 '' ，那么最外层的 <nav> Container 会被完全移除。
示例：
使用默认 options 的目录组件的渲染结果类似以下结构：
<template>
+ <!-- container -->
+ <nav class="vuepress-toc">
+ <!-- list -->
+ <ul class="vuepress-toc-list">
+ <!-- item -->
+ <li class="vuepress-toc-item">
+ <!-- link -->
+ <RouteLink class="vuepress-toc-link" to="#foo">Foo</RouteLink>
+ </li>
+ <!-- item with children -->
+ <li class="vuepress-toc-item">
+ <!-- link (children active) -->
+ <RouteLink class="vuepress-toc-link active" to="#bar">Bar</RouteLink>
+ <!-- list (children) -->
+ <ul class="vuepress-toc-list">
+ <!-- item -->
+ <li class="vuepress-toc-item">
+ <!-- link (active) -->
+ <RouteLink class="vuepress-toc-link active" to="#bar-child">
+ Bar Child
+ </RouteLink>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </nav>
+</template>
+Type: string
Details:
+Hostname to be deployed, e.g.: https://example.com
Type: { [path: string]: Partial<DefaultThemeLocaleData> }
Default: {}
Details:
+Specify locales for i18n support.
+All the options inside the Locale Config section can be used in locales.
+This option will only take effect in default theme, so don't confuse with locales in Site Config.
Also see:
+Type: string
Details:
+Hostname to be deployed, e.g.: https://example.com
Type: { [path: string]: Partial<DefaultThemeLocaleData> }
Default: {}
Details:
+Specify locales for i18n support.
+All the options inside the Locale Config section can be used in locales.
+This option will only take effect in default theme, so don't confuse with locales in Site Config.
Also see:
+Config of this section can be used as normal config, and can also be used in the locales option.
+Type: 'auto' | 'light' | 'dark'
Default: 'auto'
Details:
+Default color mode.
+If set to 'auto', the initial color mode will be automatically set according to prefers-color-scheme.
Also see:
+ +Type: boolean
Default: true
Details:
+Enable color mode switching or not.
+If set to true, a button to switch color mode will be displayed in the navbar.
Also see:
+ +Type: string
Default: /
Details:
+Specify the path of the homepage.
+This will be used for:
+Type: false | (NavbarItem | NavbarGroup | string)[]
Default: []
Details:
+Configuration of navbar.
+Set to false to disable navbar.
To configure the navbar items, you can set it to a navbar array, each item of which could be a NavbarItem object, a NavbarGroup object, or a string:
NavbarItem object should have a text field and a link field, could have an optional activeMatch field.NavbarGroup object should have a text field and a children field. The children field should be a navbar array, too.NavbarItem object, using the page title as text, and the page route path as link.Example 1:
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // NavbarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ },
+ // NavbarGroup
+ {
+ text: 'Group',
+ children: ['/group/foo.md', '/group/bar.md'],
+ },
+ // string - page file path
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // nested group - max depth is 2
+ {
+ text: 'Group',
+ children: [
+ {
+ text: 'SubGroup',
+ children: ['/group/sub/foo.md', '/group/sub/bar.md'],
+ },
+ ],
+ },
+ // control when should the item be active
+ {
+ text: 'Group 2',
+ children: [
+ {
+ text: 'Always active',
+ link: '/',
+ // this item will always be active
+ activeMatch: '/',
+ },
+ {
+ text: 'Active on /foo/',
+ link: '/not-foo/',
+ // this item will be active when current route path starts with /foo/
+ // regular expression is supported
+ activeMatch: '^/foo/',
+ },
+ ],
+ },
+ ],
+ }),
+}
+Type: null | string
Details:
+Specify the url of logo image.
+The logo image will be displayed at the left end of the navbar.
+Set to null to disable logo.
Example:
+export default {
+ theme: defaultTheme({
+ // public file path
+ logo: '/hero.png',
+ // url
+ logo: 'https://vuejs.org/images/logo.png',
+ }),
+}
+Type: null | string
Details:
+Specify the url of logo image to be used in dark mode.
+You can make use of this option if you want to use different logo config in dark mode.
+Set to null to disable logo in dark mode. Omit this option to use logo in dark mode.
Also see:
+ +Type: null | string
Details:
+Specify the alt text of the logo image.
+If not specified, defaults to be the same as the site title.
+Type: string
Details:
+Specify the repository url of your project.
+This will be used as the link of the repository link, which will be displayed as the last item of the navbar.
+export default {
+ theme: defaultTheme({
+ // If you set it in the form of `organization/repository`
+ // we will take it as a GitHub repo
+ repo: 'vuejs/vuepress',
+ // You can also set it to a URL directly
+ repo: 'https://gitlab.com/foo/bar',
+ }),
+}
+Type: false | 'auto' | SidebarConfigArray | SidebarConfigObject
Default: 'auto'
Details:
+Configuration of sidebar.
+You can override this global option via sidebar frontmatter in your pages.
+Set to false to disable sidebar.
If you set it to 'auto', the sidebar will be automatically generated from the page headers.
To configure the sidebar items manually, you can set this option to a sidebar array, each item of which could be a SidebarItem object or a string:
SidebarItem object should have a text field, could have an optional link field, an optional children field and an optional collapsible field. The children field should be a sidebar array. The collapsible field controls whether the item is collapsible.SidebarItem object, whose text is the page title, link is the page route path, and children is automatically generated from the page headers.If you want to set different sidebar for different sub paths, you can set this option to a sidebar object:
+'heading' to automatically generate the sidebar from the page headers for just the corresponding path.Example 1:
+export default {
+ theme: defaultTheme({
+ // sidebar array
+ // all pages will use the same sidebar
+ sidebar: [
+ // SidebarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ children: [
+ // SidebarItem
+ {
+ text: 'github',
+ link: 'https://github.com',
+ children: [],
+ },
+ // string - page file path
+ '/foo/bar.md',
+ ],
+ },
+ // string - page file path
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // sidebar object
+ // pages under different sub paths will use different sidebar
+ sidebar: {
+ '/guide/': [
+ {
+ text: 'Guide',
+ children: ['/guide/introduction.md', '/guide/getting-started.md'],
+ },
+ ],
+ '/reference/': 'heading',
+ },
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // collapsible sidebar
+ sidebar: {
+ '/reference/': [
+ {
+ text: 'VuePress Reference',
+ collapsible: true,
+ children: ['/reference/cli.md', '/reference/config.md'],
+ },
+ {
+ text: 'Bundlers Reference',
+ collapsible: true,
+ children: [
+ '/reference/bundler/vite.md',
+ '/reference/bundler/webpack.md',
+ ],
+ },
+ ],
+ },
+ }),
+}
+Type: number
Default: 2
Details:
+Set the maximum depth of the sidebar children which are automatically generated from the page headers.
+0 to disable all levels of headers.1 to include <h2> headers.2 to include <h2> and <h3> headers.The max value depends on which levels of headers you have extracted via markdown.headers.level.
+The default value of markdown.headers.level is [2, 3], so the default max value of sidebarDepth is 2.
You can override this global option via sidebarDepth frontmatter in your pages.
+Type: boolean
Default: true
Details:
+Enable the edit this page link or not.
+You can override this global option via editLink frontmatter in your pages.
+Type: string
Details:
+Specify the pattern of the edit this page link.
+This will be used for generating the edit this page link.
+If you don't set this option, the pattern will be inferred from the docsRepo option. But if your documentation repository is not hosted on a common platform, for example, GitHub, GitLab, Bitbucket, Gitee, etc., you have to set this option explicitly to make the edit this page link work.
+Usage:
+| Pattern | Description | +|
+Default theme's Layout provides some slots:
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottomDefault theme's Layout provides some slots:
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottomWith the help of them, you can add or replace content easily. Here comes an example to introduce how to extend default theme with layout slots.
+Firstly, create a client config file .vuepress/client.ts:
import { defineClientConfig } from 'vuepress/client'
+import Layout from './layouts/Layout.vue'
+
+export default defineClientConfig({
+ layouts: {
+ Layout,
+ },
+})
+Next, create the .vuepress/layouts/Layout.vue, and make use of the slots that provided by the Layout of default theme:
<script setup>
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+</script>
+
+<template>
+ <ParentLayout>
+ <template #page-bottom>
+ <div class="my-footer">This is my custom page footer</div>
+ </template>
+ </ParentLayout>
+</template>
+
+<style lang="css">
+.my-footer {
+ text-align: center;
+}
+</style>
+Then the default Layout layout has been overridden by your own local layout, which will add a custom footer to every normal pages in default theme (excluding homepage):
The layout slots are useful, but sometimes you might find it's not flexible enough. Default theme also provides the ability to replace a single component.
+Default theme has registered alias for every non-global components with a @theme prefix. For example, the alias of HomeFooter.vue is @theme/HomeFooter.vue.
Then, if you want to replace the HomeFooter.vue component, just override the alias in your config file .vuepress/config.ts:
import { defaultTheme } from '@vuepress/theme-default'
+import { getDirname, path } from 'vuepress/utils'
+import { defineUserConfig } from 'vuepress'
+
+const __dirname = getDirname(import.meta.url)
+
+export default defineUserConfig({
+ theme: defaultTheme(),
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+})
+Instead of extending the default theme directly in .vuepress/config.ts and .vuepress/client.ts, you can also develop your own theme extending the default theme:
import { defaultTheme, type DefaultThemeOptions } from '@vuepress/theme-default'
+import type { Theme } from 'vuepress/core'
+import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export const childTheme = (options: DefaultThemeOptions): Theme => {
+ return {
+ name: 'vuepress-theme-child',
+ extends: defaultTheme(options),
+
+ // override layouts in child theme's client config file
+ // notice that you would build ts to js before publishing to npm,
+ // so this should be the path to the js file
+ clientConfigFile: path.resolve(__dirname, './client.js'),
+
+ // override component alias
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+ }
+}
+If your site is served in a different language besides English, you should set these options per locale to provide translations.
+Type: string
Details:
+Specify the repository label of your project.
+This will be used as the text of the repository link, which will be displayed as the last item of the navbar.
+If you don't set this option explicitly, it will be automatically inferred from the repo option.
+If your site is served in a different language besides English, you should set these options per locale to provide translations.
+Type: string
Details:
+Specify the repository label of your project.
+This will be used as the text of the repository link, which will be displayed as the last item of the navbar.
+If you don't set this option explicitly, it will be automatically inferred from the repo option.
+Type: string
Details:
+Specify the text of the select language menu.
+The select language menu will appear next to the repository button in the navbar when you set multiple locales in your site config.
+Type: string
Details:
+Specify the aria-label attribute of the select language menu.
This is mainly for a11y purpose.
+Type: string
Details:
+Specify the name of the language of a locale.
+This option will only take effect inside the locales of your theme config. It will be used as the language name of the locale, which will be displayed in the select language menu.
+Example:
+export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+ theme: defaultTheme({
+ locales: {
+ '/': {
+ selectLanguageName: 'English',
+ },
+ '/zh/': {
+ selectLanguageName: '简体中文',
+ },
+ },
+ }),
+}
+Type: null | string
Details:
+aria-label value for main navigation in navbar.
Type: null | string
Details:
+aria-label value for next/previous page navigation.
Type: string
Default: 'Edit this page'
Details:
+Specify the text of the edit this page link.
+Type: string
Default: 'Last Updated'
Details:
+Specify the text of the last updated timestamp label.
+Type: string
Default: 'Contributors'
Details:
+Specify the text of the contributors list label.
+Type: string
Default: 'TIP'
Details:
+Specify the default title of the tip custom containers.
+Type: string
Default: 'WARNING'
Details:
+Specify the default title of the warning custom containers.
+Type: string
Default: 'DANGER'
Details:
+Specify the default title of the danger custom containers.
+Type: string[]
Default: ['Not Found']
Details:
+Specify the messages of the 404 page.
+The message will be randomly picked from the array when users enter the 404 page.
+Type: string
Default: 'Back to home'
Details:
+Specify the text of the back to home link in the 404 page.
+Type: string
Default: 'open in new window'
Details:
+Specify the sr-only text of the ExternalLinkIcon.
This is mainly for a11y purpose.
+Also see:
+ +Type: string
Default: 'toggle color mode'
Details:
+Title text for the color mode toggle button.
+This is mainly for a11y purpose.
+Also see:
+ +Type: string
Default: 'toggle sidebar'
Details:
+Title text for sidebar toggle button.
+This is mainly for a11y purpose.
+Type: string
Default: 'Prev'
Details:
+Text for the previous page navigation button.
+Type: string
Default: 'Next'
Details:
+Text for the next page navigation button.
+themePlugins.
+Default theme is using some plugins by default. You can disable a plugin if you really do not want to use it. Make sure you understand what the plugin is for before disabling it.
+import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ themePlugins: {
+ // customize theme plugins here
+ },
+ }),
+}
+themePlugins.
+Default theme is using some plugins by default. You can disable a plugin if you really do not want to use it. Make sure you understand what the plugin is for before disabling it.
+import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ themePlugins: {
+ // customize theme plugins here
+ },
+ }),
+}
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-active-header-links or not.
+Type: BackToTopPluginOptions | boolean
Default: true
Details:
+Enable @vuepress/plugin-back-to-top or not.
+Object value is supported as plugin options.
+Type: Record<ContainerType, boolean>
Details:
+Enable custom containers that powered by @vuepress/plugin-container or not.
+ContainerType type is:
tipwarningdangerdetailscodeGroupcodeGroupItemAlso see:
+ +Type: CopyCodePluginOptions | boolean
Default: true
Details:
+Enable @vuepress/plugin-copy-code or not.
+Object value is supported as plugin options.
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-external-link-icon or not.
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-git or not.
+Type: LinksCheckPluginOptions | boolean
Default: true
Details:
+Enable @vuepress/plugin-links-check or not.
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-medium-zoom or not.
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-nprogress or not.
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-prismjs or not.
+Type: SeoPluginOptions | boolean
Default: true
Details:
+Enable @vuepress/plugin-seo or not.
+Object value is supported as plugin options.
+Type: SitemapPluginOptions | boolean
Default: true
Details:
+Enable @vuepress/plugin-sitemap or not.
+Object value is supported as plugin options.
+Type: (page: Page) => Record<string, unknown>
Required: No
+Reference:
+ +Details:
+Function getting article info.
+Article info will be injected in route meta so that they will be available later in client composables.
+Type: (page: Page) => boolean
Default: (page) => Boolean(page.filePathRelative) && !page.frontmatter.home
Reference:
+ +Details:
+Page filter, determine whether a page should be included.
+By default, all the pages generated from Markdown files but not homepage will be included as articles.
+BlogCategoryOptions[]BlogTypeOptions[](name: string) => string(name) => name.replace(/ _/g, '-').replace(/[:?*|\\/<>]/g, "").toLowerCase()booleantruestringType: (page: Page) => Record<string, unknown>
Required: No
+Reference:
+ +Details:
+Function getting article info.
+Article info will be injected in route meta so that they will be available later in client composables.
+Type: (page: Page) => boolean
Default: (page) => Boolean(page.filePathRelative) && !page.frontmatter.home
Reference:
+ +Details:
+Page filter, determine whether a page should be included.
+By default, all the pages generated from Markdown files but not homepage will be included as articles.
+BlogCategoryOptions[]BlogTypeOptions[](name: string) => string(name) => name.replace(/ _/g, '-').replace(/[:?*|\\/<>]/g, "").toLowerCase()booleantruestring<!-- more -->Type: number
Default: 300
Reference:
+ +Details:
+Length of excerpt when auto generating.
+TIP
+Excerpt length will be the minimal possible length reaching this value.
+You can set it to 0 to disable auto excerpt generation.
Type: (page: Page) => boolean
Default: filter option
Reference:
+ +Details:
+Page filter, determine whether the plugin should generate excerpt for it.
+TIP
+You should use this to skip pages that you don't need to generate excerpt for. E.g.: If users set excerpt or description in frontmatter, you may want to use them directly.
Type: (tagName: string) => boolean
Default: () => false
Reference:
+ +Details:
+Tags which is considered as custom elements.
+This is used to determine whether a tag is a custom element since all unknown tags are removed in excerpt.
+Type: string
Default: "_blog"
Details:
+Key used when injecting info to route meta.
+TIP
+Setting to an empty key will inject to route meta directly instead of a field.
+Type: boolean
Default: Whether using --debug flag
Details:
+Whether enable hotReload in devServer.
+To theme developers
+It's disabled by default because it does have performance impact in sites with a lot of categories and types. And it can slow down hotReload speed when editing Markdown.
+If users are adding or organizing your categories or tags, you may tell them to enable this, for the rest it's better to keep it disabled.
+Also, you can try to detect number of pages in users project and decide whether to enable it.
+Blog category config should be an array, while each item is controlling a "category" rule.
+interface BlogCategoryOptions {
+ /**
+ * Unique category name
+ */
+ key: string
+
+ /**
+ * Function getting category from page
+ */
+ getter: (page: Page) => string[]
+
+ /**
+ * A custom function to sort the pages
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * Path pattern of page to be registered
+ *
+ * @description `:key` will be replaced by the "slugify" result of the original key
+ *
+ * @default `/:key/`
+ */
+ path?: string
+
+ /**
+ * Page layout name
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Frontmatter
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+
+ /**
+ * Item page path pattern or custom function to be registered
+ *
+ * @description When filling in a string, `:key` and `:name` will be replaced by the "slugify" result of the original key and name
+ *
+ * @default `/:key/:name/`
+ */
+ itemPath?: string | ((name: string) => string)
+
+ /**
+ * Item page layout name
+ *
+ * @default 'Layout'
+ */
+ itemLayout?: string
+
+ /**
+ * Items Frontmatter
+ */
+ itemFrontmatter?: (name: string, localePath: string) => Record<string, string>
+}
+Blog type config should be an array, while each item is controlling a "type" rule.
+interface BlogTypeOptions {
+ /**
+ * Unique type name
+ */
+ key: string
+
+ /**
+ * A filter function to determine whether a page should be the type
+ */
+ filter: (page: Page) => boolean
+
+ /**
+ * A custom function to sort the pages
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * Page path to be registered
+ *
+ * @default '/:key/'
+ */
+ path?: string
+
+ /**
+ * Layout name
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Frontmatter
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+}
+You can import the following API from @vuepress/plugin-blog/client.
Blog category
+const useBlogCategory: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogCategoryData<T>>
+Argument key should be the category unique key.
If no key is passed, the plugin will try to use the key in current path.
+Blog category
+const useBlogType: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogTypeData<T>>
+Argument key should be the type unique key.
If no key is passed, the plugin will try to use the key in current path.
+Returning values are:
+interface Article<T extends Record<string, unknown> = Record<string, unknown>> {
+ /** Article path */
+ path: string
+ /** Article info */
+ info: T
+}
+
+interface BlogCategoryData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** Category path */
+ path: string
+
+ /**
+ * Only available when current route matches an item path
+ */
+ currentItems?: Article<T>[]
+
+ /** Category map */
+ map: {
+ /** Unique key under current category */
+ [key: string]: {
+ /** Category path of the key */
+ path: string
+ /** Category items of the key */
+ items: Article<T>[]
+ }
+ }
+}
+
+interface BlogTypeData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** Type path */
+ path: string
+
+ /** Items under current type */
+ items: Article<T>[]
+}
+@vuepress/plugin-blog, you can easily bring blog feature into your theme.
+The plugin filters all pages using filter option to drop pages you don't want.
By default, all pages generating from Markdown files but not homepage are considered as articles.
+You can fully customize pages to collect through option filter, which accepts a function (page: Page) => boolean.
You should set getInfo option with a function accepting Page as argument and returning an object containing the info you want.
The plugin will collect all the info you want and write them to routeMeta field of each page, so you will be able to get this information through Composition API later.
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ filter: ({ filePathRelative, frontmatter }) => {
+ // drop those pages which is NOT generated from file
+ if (!filePathRelative) return false
+
+ // drop those pages in `archives` directory
+ if (filePathRelative.startsWith('archives/')) return false
+
+ // drop those pages which do not use default layout
+ if (frontmatter.home || frontmatter.layout) return false
+
+ return true
+ },
+
+ getInfo: ({ frontmatter, git = {}, data = {} }) => {
+ // getting page info
+ const info: Record<string, any> = {
+ author: frontmatter.author || '',
+ categories: frontmatter.categories || [],
+ date: frontmatter.date || git.createdTime || null,
+ tags: frontmatter.tags || [],
+ excerpt: data.excerpt || '',
+ }
+
+ return info
+ },
+ }),
+ // other plugins ...
+ ],
+}
+Basically, you would want 2 types of collection in your blog:
+Category:
+"Category" means grouping articles with their labels.
+For example, each article may have their "categories" and "tags".
+Type:
+"Type" means identifying articles with conditions.
+For example, you may want to describe some of your articles as diary.
+After understanding description of these 2 types, you can set category and type options, each accepts an array, and each element represents a configuration.
Let's start with 2 examples here.
+Imagine you are setting tags for each articles with tag field in page frontmatter. You want a tag mapping page in /tag/ with TagMap layout, and group each tag list with tagName in /tag/tagName with TagList layout, you probably need a configuration like this:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // other options ...
+ category: [
+ {
+ key: 'tag',
+ getter: ({ frontmatter }) => frontmatter.tag || [],
+ path: '/tag/',
+ layout: 'TagMap',
+ frontmatter: () => ({ title: 'Tag page' }),
+ itemPath: '/tag/:name/',
+ itemLayout: 'TagList',
+ itemFrontmatter: (name) => ({ title: `Tag ${name}` }),
+ },
+ ],
+ }),
+ // other plugins ...
+ ],
+}
+Also, you may want to star some of your articles, and display them to visitors. When you are setting star: true in frontmatter to mark them, you probably need a configuration like this to display them in /star/ path with StarList layout:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // other options ...
+ type: [
+ {
+ key: 'star',
+ filter: ({ frontmatter }) => frontmatter.star,
+ path: '/star/',
+ layout: 'StarList',
+ frontmatter: () => ({ title: 'Star page' }),
+ },
+ ],
+ }),
+ // other plugins ...
+ ],
+}
+See, setting these 2 types is easy. For full options, please see Category Config and Type Config.
+When generating each page, the plugin will set following information under frontmatter.blog:
interface BlogFrontmatterOptions {
+ /** Current type of the page */
+ type: 'category' | 'type'
+ /** Unique key under current category or tag */
+ key: string
+ /**
+ * Current category name
+ *
+ * @description Only available in category item page
+ */
+ name?: string
+}
+So you can invoke useBlogCategory() and useBlogType() directly, and the result will be the category or type bind to current route.
Also, you can pass key you want as argument, then you will get information bind to that key.
So with node side settings above, you can get information about "tag" and "star" in client side:
+TagMap layout:
<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+
+<template>
+ <div>
+ <h1>Tag page</h1>
+ <ul>
+ <li v-for="({ items, path }, name) in categoryMap.map">
+ <RouteLink :key="name" :to="path" class="category">
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </li>
+ </ul>
+ </div>
+</template>
+TagList layout:
<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+
+<template>
+ <div>
+ <h1>Tag page</h1>
+ <div class="category-wrapper">
+ <RouteLink
+ v-for="({ items, path }, name) in categoryMap.map"
+ :key="name"
+ :to="path"
+ class="category"
+ >
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </div>
+ <div class="article-wrapper" v-if="categoryMap.currentItems">
+ <div v-if="!categoryMap.currentItems.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in categoryMap.currentItems"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline
+ ? `${new Date(info.date).toLocaleDateString()}: `
+ : '') + info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author"
+ >Author: {{ info.author }}</span
+ >
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag"
+ >Tag: {{ info.tag.join(', ') }}</span
+ >
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+ </div>
+</template>
+StarList layout:
<script setup lang="ts">
+import { useBlogType } from '@vuepress/plugin-blog/client'
+import { RouteLink } from 'vuepress/client'
+
+import ArticleList from '../components/ArticleList.vue'
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+
+const stars = useBlogType('star')
+</script>
+
+<template>
+ <div class="article-wrapper" v-if="stars.items">
+ <div v-if="!stars.items.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in stars.items"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline ? `${new Date(info.date).toLocaleDateString()}: ` : '') +
+ info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author">Author: {{ info.author }}</span>
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag">Tag: {{ info.tag.join(', ') }}</span>
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+</template>
+For return types, please see Composition API Return Types.
+This plugin adds native i18n support, so your settings will be automatically applied to each language.
+For example, if user has the following locales' config, and you are setting the "star" example above:
+export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+}
+Then /zh/star/ and /star/ will both be available, and only articles under the correct locale will appear.
This plugin provides a built-in excerpt generator, which can be enabled by setting excerpt option to true.
Excerpt introduction
+An excerpt is an HTML fragment that is used to display a short description of an article in the blog list, so the excerpt has the following restrictions:
+isCustomElement option..vuepress/public or full URL to ensure they can be accessed in other places.The excerpt generator will try to find a valid excerpt separator from markdown contents, if it finds one, it will use content before the separator. The separator is default `
+]]>@vuepress/plugin-blog, you can easily bring blog feature into your theme.
+The plugin filters all pages using filter option to drop pages you don't want.
By default, all pages generating from Markdown files but not homepage are considered as articles.
+You can fully customize pages to collect through option filter, which accepts a function (page: Page) => boolean.
You should set getInfo option with a function accepting Page as argument and returning an object containing the info you want.
The plugin will collect all the info you want and write them to routeMeta field of each page, so you will be able to get this information through Composition API later.
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ filter: ({ filePathRelative, frontmatter }) => {
+ // drop those pages which is NOT generated from file
+ if (!filePathRelative) return false
+
+ // drop those pages in `archives` directory
+ if (filePathRelative.startsWith('archives/')) return false
+
+ // drop those pages which do not use default layout
+ if (frontmatter.home || frontmatter.layout) return false
+
+ return true
+ },
+
+ getInfo: ({ frontmatter, git = {}, data = {} }) => {
+ // getting page info
+ const info: Record<string, any> = {
+ author: frontmatter.author || '',
+ categories: frontmatter.categories || [],
+ date: frontmatter.date || git.createdTime || null,
+ tags: frontmatter.tags || [],
+ excerpt: data.excerpt || '',
+ }
+
+ return info
+ },
+ }),
+ // other plugins ...
+ ],
+}
+Basically, you would want 2 types of collection in your blog:
+Category:
+"Category" means grouping articles with their labels.
+For example, each article may have their "categories" and "tags".
+Type:
+"Type" means identifying articles with conditions.
+For example, you may want to describe some of your articles as diary.
+After understanding description of these 2 types, you can set category and type options, each accepts an array, and each element represents a configuration.
Let's start with 2 examples here.
+Imagine you are setting tags for each articles with tag field in page frontmatter. You want a tag mapping page in /tag/ with TagMap layout, and group each tag list with tagName in /tag/tagName with TagList layout, you probably need a configuration like this:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // other options ...
+ category: [
+ {
+ key: 'tag',
+ getter: ({ frontmatter }) => frontmatter.tag || [],
+ path: '/tag/',
+ layout: 'TagMap',
+ frontmatter: () => ({ title: 'Tag page' }),
+ itemPath: '/tag/:name/',
+ itemLayout: 'TagList',
+ itemFrontmatter: (name) => ({ title: `Tag ${name}` }),
+ },
+ ],
+ }),
+ // other plugins ...
+ ],
+}
+Also, you may want to star some of your articles, and display them to visitors. When you are setting star: true in frontmatter to mark them, you probably need a configuration like this to display them in /star/ path with StarList layout:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // other options ...
+ type: [
+ {
+ key: 'star',
+ filter: ({ frontmatter }) => frontmatter.star,
+ path: '/star/',
+ layout: 'StarList',
+ frontmatter: () => ({ title: 'Star page' }),
+ },
+ ],
+ }),
+ // other plugins ...
+ ],
+}
+See, setting these 2 types is easy. For full options, please see Category Config and Type Config.
+When generating each page, the plugin will set following information under frontmatter.blog:
interface BlogFrontmatterOptions {
+ /** Current type of the page */
+ type: 'category' | 'type'
+ /** Unique key under current category or tag */
+ key: string
+ /**
+ * Current category name
+ *
+ * @description Only available in category item page
+ */
+ name?: string
+}
+So you can invoke useBlogCategory() and useBlogType() directly, and the result will be the category or type bind to current route.
Also, you can pass key you want as argument, then you will get information bind to that key.
So with node side settings above, you can get information about "tag" and "star" in client side:
+TagMap layout:
<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+
+<template>
+ <div>
+ <h1>Tag page</h1>
+ <ul>
+ <li v-for="({ items, path }, name) in categoryMap.map">
+ <RouteLink :key="name" :to="path" class="category">
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </li>
+ </ul>
+ </div>
+</template>
+TagList layout:
<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+
+<template>
+ <div>
+ <h1>Tag page</h1>
+ <div class="category-wrapper">
+ <RouteLink
+ v-for="({ items, path }, name) in categoryMap.map"
+ :key="name"
+ :to="path"
+ class="category"
+ >
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </div>
+ <div class="article-wrapper" v-if="categoryMap.currentItems">
+ <div v-if="!categoryMap.currentItems.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in categoryMap.currentItems"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline
+ ? `${new Date(info.date).toLocaleDateString()}: `
+ : '') + info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author"
+ >Author: {{ info.author }}</span
+ >
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag"
+ >Tag: {{ info.tag.join(', ') }}</span
+ >
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+ </div>
+</template>
+StarList layout:
<script setup lang="ts">
+import { useBlogType } from '@vuepress/plugin-blog/client'
+import { RouteLink } from 'vuepress/client'
+
+import ArticleList from '../components/ArticleList.vue'
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+
+const stars = useBlogType('star')
+</script>
+
+<template>
+ <div class="article-wrapper" v-if="stars.items">
+ <div v-if="!stars.items.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in stars.items"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline ? `${new Date(info.date).toLocaleDateString()}: ` : '') +
+ info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author">Author: {{ info.author }}</span>
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag">Tag: {{ info.tag.join(', ') }}</span>
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+</template>
+For return types, please see Composition API Return Types.
+This plugin adds native i18n support, so your settings will be automatically applied to each language.
+For example, if user has the following locales' config, and you are setting the "star" example above:
+export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+}
+Then /zh/star/ and /star/ will both be available, and only articles under the correct locale will appear.
This plugin provides a built-in excerpt generator, which can be enabled by setting excerpt option to true.
Excerpt introduction
+An excerpt is an HTML fragment that is used to display a short description of an article in the blog list, so the excerpt has the following restrictions:
+isCustomElement option..vuepress/public or full URL to ensure they can be accessed in other places.The excerpt generator will try to find a valid excerpt separator from markdown contents, if it finds one, it will use content before the separator. The separator is default <!-- more -->, and you can customize it by setting excerptSeparator option.
If it cannot find a valid separator, it will parse content from the beginning of markdown file, and stop till its length reaches a preset value. The value is default 300, and you can customize it by setting excerptLength option.
To choose which page should generate excerpt, you can use excerptFilter option.
Example
+Normally you may want to use frontmatter.description if users set them, so you can let filter function return false if frontmatter.description is not empty.
You can both set options with plugin options on Node side and set options in client config file on Browser side.
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+// .vuepress/config.ts
+export default {
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo
+
+ // other options here
+ // ...
+ }),
+ ],
+}
+You can both set options with plugin options on Node side and set options in client config file on Browser side.
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+// .vuepress/config.ts
+export default {
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo
+
+ // other options here
+ // ...
+ }),
+ ],
+}
+import { defineClientConfig } from 'vuepress/client'
+import {
+ defineArtalkConfig,
+ // defineGiscusConfig,
+ // defineTwikooConfig,
+ // defineWalineConfig,
+} from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+But here are some limitations you should remember:
+provider, locales and other resource related option must be set in plugin options.
To ensure tree-shaking works, we must optimize entries at node so that bundler can understand which resource should be included in the final bundle.
+These options will be marked with
+Options which can not be serialized to JSON must be set in client config.
+Options that receives function values can not be set in plugin options, as plugins are running under Node.js environment, so we can not pass these values and their contexts to browser.
+These options will be marked with
+This plugin globally registers a component <CommentService />.
alias and layout slots to insert the component. We recommended you to insert the comment component (<CommentService />) after the <PageNav /> component, and the current page is a demo with default theme.By default, <CommentService /> component is enabled globally, and you can use comment option in both plugin options and page frontmatter to control it.
comment: false in page frontmatter.comment to false in the plugin options. Then you can set comment: true in page frontmatter to enable it locally.You can set commentID option in page frontmatter to customize comment ID, which is used to identify comment storage item to use for a page. By default it will be the path of the page, which means if you are deploying the site to multiple places, page with same content across sites will share the same comment data.
Currently, you can choose from Giscus, Waline, Artalk and Twikoo.
+Recommended comment services
+"Artalk" | "Giscus" | "Twikoo" | "Waline" | "None""None"booleantruestringSiteConfig.titleChannel title
+stringoptions.hostname and context.base)stringSiteConfig.titleChannel title
+stringoptions.hostname and context.base)Channel address
+stringSiteConfig.descriptionChannel description
+Type: string
Default:
+siteConfig.locales['/'].lang"en-US"The language of the channel
+Type: string
Default:
+author.name in channel options, and fall back to Copyright by $authorRecommended to set manually: Yes
+Channel copyright information
+string (must be a valid Date ISOString)Publish date of the Channel
+string (must be a valid Date ISOString)Last update time of channel content
+numberThe effective time of the content. It's the time to keep the cache after request without making new requests.
+stringA picture presenting the channel. A square picture with a size not smaller than 512×512 is recommended.
+stringAn icon representing a channel, a square picture, with not less than 128×128 in size, and transparent background color is recommended.
+FeedAuthorThe author of the channel.
+interface FeedAuthor {
+ /** Author name */
+ name: string
+ /** Author's email */
+ email?: string
+ /** Author's site */
+ url?: string
+ /**
+ * Author's avatar address
+ *
+ * Square, preferably not less than 128×128 with transparent background
+ */
+ avatar?: string
+}
+stringLink to Websub. Websub requires a server backend, which is inconsistent with VuePress, so ignore it if there is no special need.
+WebSub
+For details, see Websub.
+stringThe domain name of the deployment site.
+booleanfalseWhether to output Atom syntax files.
+booleanfalsestringThe domain name of the deployment site.
+booleanfalseWhether to output Atom syntax files.
+booleanfalseWhether output JSON syntax files.
+booleanfalseWhether to output RSS syntax files.
+stringA large image/icon of the feed, probably used as banner.
+stringA small icon of the feed, probably used as favicon.
+number100Set the maximum number of items in the feed. After all pages are sorted, the first count items will be intercepted.
If your site has a lot of articles, you may consider this option to reduce feed file size.
+(RegExp | string)[] | (tagName: string) => booleanCustom element or component which should be preserved in feed.
+By default, all unknown tags will be removed.
+Type: (page: Page)=> boolean
Default:
+;({ frontmatter, filePathRelative }: Page): boolean =>
+ !(
+ frontmatter.home ||
+ !filePathRelative ||
+ frontmatter.article === false ||
+ frontmatter.feed === false
+ )
+A custom filter function, used to filter feed items.
+Type: (pageA: Page, pageB: Page)=> number
Default:
+// dateSorter is from @vuepress/helper
+;(pageA: Page, pageB: Page): number =>
+ dateSorter(
+ pageA.data.git?.createdTime
+ ? new Date(pageA.data.git?.createdTime)
+ : pageA.frontmatter.date,
+ pageB.data.git?.createdTime
+ ? new Date(pageB.data.git?.createdTime)
+ : pageB.frontmatter.date,
+ )
+Custom sorter function for feed items.
+The default sorting behavior is by file adding time coming from git (needs @vuepress/plugin-git).
TIP
+You should enable @vuepress/plugin-git to get the newest created pages as feed items. Otherwise, the feed items will be sorted by the default order of pages in VuePress.
channel option is used to config Feed Channels.
For available options, please see Config → Channel
+booleanfalseWhether enabled in devServer.
+TIP
+For performance reasons, we do not provide hot reload. Reboot your devServer to sync your changes.
+string"http://localhost:${port}"Hostname to use in devServer
+string"atom.xml"Atom syntax output filename, relative to dest folder.
+string@vuepress/plugin-feed/templates/atom.xslAtom xsl template file content.
+string"atom.xsl"Atom xsl filename, relative to dest folder.
+string"feed.json"JSON syntax output filename, relative to dest folder.
+string"rss.xml"RSS syntax output filename, relative to dest folder.
+string@vuepress/plugin-feed/templates/rss.xslRSS xsl template file content.
+string"rss.xsl"RSS syntax xsl filename, relative to dest folder.
+Feed generation controller, see Feed Getter.
+The plugin has a built-in getter, only set this if you want full control of feed generation.
+Record<string, BaseFeedOptions>You can use it to specific options for each locale.
+Any options above are supported except hostname.
By default, all articles are added to the feed stream. Set feed: false in frontmatter to remove a page from feed.
stringBy default, all articles are added to the feed stream. Set feed: false in frontmatter to remove a page from feed.
stringAutomatically generated by VuePress, defaults to the h1 content of the page
+stringDescription of the page
+DateDate when the page was published
+booleanWhether the page is an article
+++If this is set to
+false, the page will not be included in the final feed.
stringPage copyright information
+stringImage used as page cover , should be full link or absolute link.
+stringThe title of the feed item
+stringDescription of the feed item
+stringThe content of the feed item
+FeedAuthor[] | FeedAuthorThe author of the feed item
+interface FeedAuthor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+FeedContributor[] | FeedContributorContributors to feed item
+interface FeedContributor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+stringThe identifier of feed item, used to identify the feed item.
+You should ensure every feed has a unique guid.
+getter in the plugin options.
+(page: Page) => stringItem title getter
+(page: Page) => stringgetter in the plugin options.
+(page: Page) => stringItem title getter
+(page: Page) => stringItem link getter
+(page: Page) => string | undefinedItem description getter
+TIP
+Due to Atom support HTML in summary, so you can return HTML content here if possible, but the content must start with mark html:.
(page: Page) => stringItem content getter
+(page: Page) => FeedAuthor[]Item author getter.
+The getter should return an empty array when author information is missing.
+interface FeedAuthor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => FeedCategory[] | undefinedItem category getter.
+interface FeedCategory {
+ /**
+ * Category Name
+ */
+ name: string
+
+ /**
+ * A string that identifies a categorization taxonomy
+ *
+ * @description rss format only
+ */
+ domain?: string
+
+ /**
+ * the categorization scheme via a URI
+ *
+ * @description atom format only
+ */
+ scheme?: string
+}
+(page: Page) => FeedEnclosure | undefinedItem enclosure getter.
+interface FeedEnclosure {
+ /**
+ * Enclosure link
+ */
+ url: string
+
+ /**
+ * what its type is
+ *
+ * @description should be a standard MIME Type, rss format only
+ */
+ Type: string
+
+ /**
+ * Size in bytes
+ *
+ * @description rss format only
+ */
+ length?: number
+}
+(page: Page) => Date | undefinedItem release date getter
+(page: Page) => DateItem last update date getter
+(page: Page) => stringItem Image Getter
+Ensure it's returning a full URL
+(page: Page) => FeedContributor[]Item Contributor Getter
+The getter should return an empty array when contributor information is missing.
+interface FeedContributor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => string | undefinedItem copyright getter
+]]>The plugin can generate feed files in the following three formats for you:
+Please set atom, json or rss to true in the plugin options according to the formats you want to generate.
The plugin can generate feed files in the following three formats for you:
+Please set atom, json or rss to true in the plugin options according to the formats you want to generate.
To correctly generate feed links, you need to set hostname in the plugin options,
When you open the feed file in browser, we magically convert atom and rss feed xml to human readable html via xsl template. Check atom and rss feed of this site as an example!
+If you want to preview your feed in devServer, set devServer: true in plugin options. You may also need to set devHostname if you are not using the default http://localhost:{port}.
You can customize the feed channel information by setting the channel option.
We recommend the following settings:
+channel.pubDatechannel.ttl (unit: minutes)channel.copyrightchannel.author.For detailed options and their default values, see Channel Config
+By default, all articles are added to the feed stream.
+You can set feed and other options in page frontmatter to control contents of feed item. See Frontmatter Config for how they are converted.
You can take full control of feed items generation by configuring the getter in the plugin options. For detailed options and their default values, see Configuration → Feed Getter.
The plugin generates separate feeds for each language.
+You can provide different settings for different languages via locales in the plugin options.
booleanfalseType: AppManifest
Details:
+You can fill with an object which will be parsed to manifest.webmanifest.
+TIP
+Some options have their fallback if you don't set them.
+siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.description || siteConfig.locales['/'].description || "A site built with vuepress"siteConfig.locales['/'].lang || "en-US"context.basecontext.base"standalone""#46bd87""#ffffff""portrait-primary"falseReference:
+ +booleanfalseType: AppManifest
Details:
+You can fill with an object which will be parsed to manifest.webmanifest.
+TIP
+Some options have their fallback if you don't set them.
+siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.description || siteConfig.locales['/'].description || "A site built with vuepress"siteConfig.locales['/'].lang || "en-US"context.basecontext.base"standalone""#46bd87""#ffffff""portrait-primary"falseReference:
+ +Type: string
Details:
+Link of favicon.ico.
+WARNING
+We recommend you to set favicon for your site.
+Type: string
Default: "#46bd87"
Details:
+Theme Color of the pwa.
+Type: boolean
Default: false
Details:
+Whether cache HTML files besides home page and 404 page.
+Type: boolean
Default: false
Details:
+Whether cache pictures
+Type: number
Default: 2048
Details:
+Max size allowed to be cached, with KB unit
+WARNING
+This option has the highest priority, and any files exceeding this value will be excluded.
+So if you generate very large HTML or JS files, please consider increasing this value, otherwise your PWA may not work normally in offline mode.
+Type: number
Default: 1024
Details: +Max picture size allowed to be cached, with KB unit
+The value must not be greater than maxSize option
+Type: "disabled" | "available" | "hint" | "force"
Default: "available"
Details: +Control logic when new content is found.
+"disabled": Do nothing even when new service worker is available. After new service work succeeds installing and starts waiting, it will control page and provide new content in next visit.
"available": Only display update popup when the new service worker is available
"hint": Display a hint to let user choose to refresh immediately
This is helpful when you want users to see new docs immediately.
+TIP
+If users choose to refresh, the current service worker will be unregister, and request will start coming to web. Later the new service worker will start installing and control current page after installed.
+"force": unregister current service worker immediately then refresh to get new content
DANGER
+Although this ensures users are viewing the latest content, it may affect viewing experiences.
+TIP
+How docs are updated is controlled by a previous version, so the current option only effect next update from this version.
+Special settings for better supporting Safari, ignoring these options are safe.
+string"black" | "white""black"stringSpecial settings for Microsoft tiles, ignoring these options are safe.
+stringstringthemeColorstring"PwaFoundPopup"string"PwaReadyPopup"booleanfalseDetails:
+Options passed to workbox-build, for details, see Workbox documentation
Type: PwaPluginLocaleConfig
interface PwaPluginLocaleData {
+ /**
+ * Install button text
+ */
+ install: string
+
+ /**
+ * iOS install hint text
+ */
+ iOSInstall: string
+
+ /**
+ * Cancel button text
+ */
+ cancel: string
+
+ /**
+ * Close button text
+ */
+ close: string
+
+ /**
+ * Previous image text
+ */
+ prevImage: string
+
+ /**
+ * Next image text
+ */
+ nextImage: string
+
+ /**
+ * Install explain text
+ */
+ explain: string
+
+ /**
+ * Description label text
+ */
+ desc: string
+
+ /**
+ * Feature label text
+ */
+ feature: string
+
+ /**
+ * Update hint text
+ */
+ hint: string
+
+ /**
+ * Update available text
+ */
+ update: string
+}
+
+interface PwaPluginLocaleConfig {
+ [localePath: string]: PwaPluginLocaleData
+}
+Details: +Locales config for pwa plugin.
+Details:
+Returns the event emitter of this plugin.
+You can add listener function to events that provided by register-service-worker.
+Example:
+import { usePwaEvent } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+ event.on('ready', (registration) => {
+ console.log('Service worker is active.')
+ })
+ },
+}
+Details:
+Force update the page when an update is found.
+Example:
+import { forceUpdate } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ forceUpdate()
+ })
+ },
+}
+Details:
+Register service worker manually.
+Parameters:
+| Parameter | Type | Description | +|
+]]>Make your VuePress site a Progressive Web Application (PWA)[1].
+This plugin uses workbox-build to generate service worker file, and uses register-service-worker to register service worker.
]]>Make your VuePress site a Progressive Web Application (PWA)[1].
+This plugin uses workbox-build to generate service worker file, and uses register-service-worker to register service worker.
+WARNING
+If you enabled this plugin once and you want to disable it, you might need `@vuepress/plugin-remove-pwa to remove the existing service worker.
+A PWA uses a Service Worker [2] (SW for short) to cache and proxy site content.
+To make your website fully compliant with PWA, a Web app manifests [3] file is needed, and your pwa should satisfy the installability [4] specification.
+You can set manifest option to customize the manifest file, or provide a manifest.webmanifest or manifest.json in public folder. The former has higher priority.
The plugin will automatically generate manifest.webmanifest for you and add manifest link declaration in each page, while you should still at least set a valid icon through manifest.icons or other icon related options in the PWA plugin.
WARNING
+The installability [4:1] specification requires at least one valid icon to be declared in the manifest.
+So if you do not configure manifest.icons, visitors can only enjoy the offline accessibility brought by the Service Worker cache, while cannot install your site as a PWA.
Besides the plugin does not process anything in the manifest by default, but outputs them as-is. This means that if you plan to deploy to a subdirectory, you should append the URL prefix to manifest Urls yourself. If everything you need is all under base directory, you can set appendBase: true in plugin options to let the plugin append base to any links in manifest.
To better control what the Service Worker can pre-cache, the plugin provides related options for cache control.
+By default, the plugin will pre-cache all js css files, and only homepage and 404 html are cached. The plugin will also cache font files (woff, woff2, eot, ttf, otf) and SVG icons.
If your site has only a few important images, and want them displayed in offline mode, you can cache site images by setting cacheImage: true .
We recognize images by file extension. Any files ending with .png, .jpg, .jpeg, .gif, .bmp, .webp will be regarded as images.
If you have small sites, and would like to make document fully offline available, you can set cacheHTML to true to cache all HTML files.
Why only home and 404 page been cached by default?
+Though VuePress generates HTML files through SSG[5] for all pages, these files are mainly used for SEO[6] and allow you to directly configure the backend without SPA[7] Visit any link.
+VuePress is essentially an SPA. This means that you only need to cache the home page and enter from the home page to access all pages normally. Therefore, not caching other HTML by default can effectively reduce the cache size (40% smaller in size) and speed up the SW update speed.
+But this also has the disadvantage. If the user enters the site directly from a non-home page, the HTML file for the first page still needs to be loaded from the internet. Also, in offline environment, users can only enter through the homepage and then navigate to the corresponding page by themselves. If they directly access a link, an inaccessible prompt will appear.
+To prevent large files from being included in the pre-cache list, any files > 2 MB or images > 1 MB will be omitted. You can customize these limits with maxSize and maxImageSize options (in KB unit).
We provide the update option to control how users receive updates.
The default value of the update option is "available", which means that when new content available, the new SW will be installed and its resources will be fetched silently in the background. A pop-up window appears once the new SW is ready, and users can choose whether to refresh immediately to view new content. This means users are reading old content before a new SW is ready.
If your project is still in building stage, and you want to alert the user that he may be reading outdated content, you can set this to "hint". This allows users to be notified that new content has been published within seconds after visiting docs. But the negative effect of this is that if the user chooses to update before the new SW is ready, he will need to get all the resources of the page from the internet before the new SW installs and controls the page.
If your docs are stable, or you're hosting a blog and don't care much about users receiving the latest version right away, you can set this to "disabled", which means that the new SW will be installed completely silently in the background and start waiting, when all pages controlled by old SW are all closed, the new SW will start to take control and provide users with new content during next visit. This setting can prevent users from being disturbed during the visit.
To speed up user access under weak or no network conditions through SW, but also want users to always access new content, you can set this option to "force". This means any old SW will be removed as soon as a new SW is detected, and all pages are refreshed to ensure the user is browsing the latest content. The biggest disadvantage is that all users will experience unexpected sudden refresh within seconds after reentering an updated site.
When new content is detected (new SW detected), a update found popup appears; and when the new content is ready, an update ready popup appears.
+If you are not satisfied with the default popup content, you can use your own component. Import PwaFoundPopup or PwaReadyPopup from @vuepress/plugin-pwa/client and use its slot to customize the popup content, then pass the component path to foundComponent or readyComponent option:
<script setup lang="ts">
+import { PwaFoundPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaFoundPopup v-slot="{ found, refresh }">
+ <div v-if="found">
+ New content is found.
+ <button @click="refresh">Refresh</button>
+ </div>
+ </PwaFoundPopup>
+</template>
+<script setup lang="ts">
+import { PwaReadyPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaReadyPopup v-slot="{ isReady, reload }">
+ <div v-if="isReady">
+ New content is ready.
+ <button @click="reload">Apply</button>
+ </div>
+ </PwaReadyPopup>
+</template>
+The plugin also provides other PWA-related options, such as Microsoft tile icon and color settings, Apple icon and so on. If you are an advanced user, you can also set generateSwConfig to configure workbox-build. Check Plugin options for more details.
For more details, please see:
+ +PWA introduction
+PWA, full name Progressive Web app. PWA standard is stipulated by W3C.
+It allows sites to install the site as an App on supported platform through a browser that supports this feature.
+See https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps for details. ↩︎
+Service Worker Introduction
+The Service Worker will get and cache all the files registered in it during the registration process.
+After the registration complete, the Service Worker is activated, and starts to proxy and control all your requests.
+Whenever you want to initiate an access request through the browser, the Service Worker will check whether it exists in its own cache list, if it exists, it will directly return the cached result, otherwise it will call its own fetch method to get it. You can use a custom fetch method to fully control the result of the request for resources in the web page, such as providing a fallback web page when offline.
+Every time the user reopens the site, the Service Worker will request to the link when it was registered. If a new version of Service Worker is detected, it will update itself and start caching the list of resources registered in the new Service Worker . After the content update is successfully obtained, the Service Worker will trigger the update event. The user can be notified through this event, for example, a pop-up window will be displayed in the lower right corner, prompting the user that new content is available and allowing the user to trigger an update.
Manifest File
+The manifest file uses the JSON format and is responsible for declaring various information of the PWA, such as name, description, icon, and shortcut actions.
+In order for your site to be registered as a PWA, you need to meet the basic specifications of the manifest to make the browser consider the site as an installable PWA and allow users to install it.
+TIP
+For Manifest standards and specifications, please see MDN Web app manifests and W3C Manifest.
+Installable
+To let the site be registered as a PWA, the site needs to successfully register a valid service worker by itself, and declare a valid manifest file with its link in meta tag.
+The manifest file should contain at least name (or short_name) icons start_url.
On safari, the maximum cache size of the service worker is 50 MB. ↩︎ ↩︎
+SSG: Static Site Generation, ↩︎
+SEO: Search Engine Optimization. ↩︎
+SPA: Single Page Application, most of them only have the homepage, and use history mode to handle routing instead of actually navigating between pages. ↩︎
+Type: string
Required: Yes
+Details:
+Deploy hostname.
+Type: Author
type AuthorName = string
+
+interface AuthorInfo {
+ /**
+ * Author name
+ */
+ name: string
+
+ /**
+ * Author website
+ */
+ url?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+}
+
+type Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]
+Required: No
+Details:
+Default author.
+Type: string
Required: Yes
+Details:
+Deploy hostname.
+Type: Author
type AuthorName = string
+
+interface AuthorInfo {
+ /**
+ * Author name
+ */
+ name: string
+
+ /**
+ * Author website
+ */
+ url?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+}
+
+type Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]
+Required: No
+Details:
+Default author.
+Type: boolean
Default: true
Details:
+Whether generate description automatically
+Type: string | ((page: Page) => string | null)
Details:
+Canonical link
+Type: string
Details:
+Fallback Image link when no image are found
+Type: string
Details:
+The age rating of the content, the format is [int]+, such as "13+".
Type: string
Details:
+Fill in your twitter username.
+Type: (page: Page) => boolean
Details:
+Use this option to judge whether the page is an article.
+Type:
+function ogp(
+ /** OGP info inferred by plugin */
+ ogp: SeoContent,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+Required: No
+Details:
+Custom OPG Generator.
+You can use this options to edit OGP tags.
+Type:
+function jsonLd(
+ /** JSON-LD Object inferred by plugin */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+Required: No
+Details:
+Custom JSON-LD Generator.
+You can use this options to edit JSON-LD properties.
+Type:
+function customHead(
+ /** Head tag config */
+ head: HeadConfig[],
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+Required: No
+Details:
+You can use this options to edit tags injected to <head>.
The plugin works out of the box. Without any config, it will extract information from the page content as much as possible to complete the necessary tags required by OGP and JSON-LD.
+By default, the plugin will read the site config and page frontmatter to automatically generate tags as much as possible. Such as site name, page title, page type, writing date, last update date, and article tags are all automatically generated.
+The following are the <meta> tags and their values that will be injected into <head> by default:
The following are the <meta> tags and their value injected into <head> by default to satisfy OGP:
| Meta Name | Value | +| :
+]]>Type: string
Required: Yes
+Details:
+The domain name where the current site is deployed, the plugin needs this option to work.
+Type: string[]
Details:
+Extra link to be included.
+If you have some links not including in VuePress Router (normally in public directory or generated by other tools directly), you may need this option.
+Example: ['/about.html', '/api/']
Type: string
Required: Yes
+Details:
+The domain name where the current site is deployed, the plugin needs this option to work.
+Type: string[]
Details:
+Extra link to be included.
+If you have some links not including in VuePress Router (normally in public directory or generated by other tools directly), you may need this option.
+Example: ['/about.html', '/api/']
Type: string[]
Default: ['/404.html']
Details:
+Urls excluding from sitemap, starting with absolute path.
+By default, all the urls generated by VuePress (excluding 404 page) will be added into sitemap.
+Type: boolean
Default: false
Details:
+Whether enabled in devServer.
+TIP
+For performance reasons, we do not provide hot reload. Reboot your devServer to sync your changes.
+Type: string
Default: "http://localhost:${port}"
Details:
+Hostname to use in devServer
+Type: string
Default value: "sitemap.xml"
Details:
+The output filename, relative to output directory.
+Type: string
Default value: "sitemap.xsl"
Details:
+Output xsl filename, relative to dest folder.
+Type: string
Default value: "@vuepress/plugin-sitemap/templates/sitemap.xsl"
Details:
+XSL content used as template.
+Type: "always" | "hourly" | "daily" | "weekly" |"monthly" | "yearly" | "never"
Default value: "daily"
Details:
+Page default update frequency, will be overridden by sitemap.changefreq in Frontmatter.
+Type: number
Default: 0.5
Details:
+Page priority, from 0 to 1.
Type: (page: Page, app: App) => string
Details:
+Last modify time getter. By default, the plugin will use the timestamp generated by git plugin.
+Type: SitemapFrontmatterOptions | false
Details:
+false means exclude the page from sitemap.
Type: "always" | "hourly" | "daily" | "weekly" | "monthly" | "yearly" | "never"
Default: "daily"
Details:
+Page default update frequency. This will override changefreq in Plugin Options.
+Type: SitemapFrontmatterOptions | false
Details:
+false means exclude the page from sitemap.
Type: "always" | "hourly" | "daily" | "weekly" | "monthly" | "yearly" | "never"
Default: "daily"
Details:
+Page default update frequency. This will override changefreq in Plugin Options.
+Type: number
Default: 0.5
Details:
+Page priority, range from 0 to 1.
hostname option of the plugin. If you want to preview in devServer, set devServer options.
+The plugin will automatically generate the last update time of the page based on the Git timestamp of the page, and will also declare the alternative links of the page in other languages according to the locales' config.
]]>hostname option of the plugin. If you want to preview in devServer, set devServer options.
+The plugin will automatically generate the last update time of the page based on the Git timestamp of the page, and will also declare the alternative links of the page in other languages according to the locales' config.
+By default, all site links except 404 page will be added to the Sitemap.
+To add other pages to the Sitemap outside the VuePress project page, please turn them into an array and pass to the extraUrls plugin option.
If you don't want certain pages to appear in the sitemap, you can turn their paths into an array and pass to the excludePaths plugin option, or set sitemap to false in the frontmatter of the corresponding page.
You can also control the output link through the sitemapFilename option of the plugin, the link is relative to output directory. By default, the plugin will use sitemap.xml.
The default update cycle of the page is daily (every day). To modify the entire page cycle, please set changefreq in the plugin options. You can also set sitemap.changefreq in the frontmatter of the page. Note that page has a higher priority.
The legal frequencies are:
+"always""hourly""daily""weekly""monthly""yearly""never"You can set priority in the plugin to provide a default value. At the same time you can set the priority for each page through sitemap.priority in frontmatter. Acceptable values are floating point numbers from 0 to 1.
You can use option modifyTimeGetter to return a time in ISO string format, which is generated by the Git plugin by default.
The following is an example based on the last modification time of a file.
+// Based on file last modified time
+({
+ modifyTimeGetter: (page, app) =>
+ fs.statSync(app.dir.source(page.filePathRelative)).mtime.toISOString();
+})
+Sitemaps provide SEO (Search Engine Optimization):
+A sitemap enhances SEO by making all pages findable.
+Most search engines only follow a limited number of links within a page, so when the site is very large, a sitemap becomes essential to make everything on the site accessible to search engines and visitors.
+Sitemaps is a protocol for site administrators to publish pages that can be crawled on a site to search engine spiders. The content of sitemap files must follow the definition in XML format. Each URL can contain the update period and last update time, the priority of the URL across the site. This allows search engines to crawl site content better and more efficiently.
+Together with robots.txt
+Sitemap is basically used by search engines, when using this plugin, you'd better ensure that you have a valid robots.txt in the .vuepress/public directory to allow search engines spiders to visit your site. The simplest robots.txt is as follows (allow all search engines to access all paths)
User-agent: *
+
+Allow: /
+Check whether a component is registered globally.
+TIP
+setup scope, you need to pass the app instance as the second parameter.Check whether a component is registered globally.
+TIP
+setup scope, you need to pass the app instance as the second parameter.export const hasGlobalComponent: (name: string, app?: App) => boolean
+// if you globally register `<my-component>`
+hasGlobalComponent('MyComponent') // true
+hasGlobalComponent('my-component') // true
+
+hasGlobalComponent('MyComponent2') // false
+Get current locale config from locales settings.
+export const useLocaleConfig: <T extends LocaleData>(
+ localesConfig: RequiredLocaleConfig<T>,
+) => ComputedRef<T>
+const localesCOnfig = {
+ '/': 'Title',
+ '/zh/': '标题',
+}
+
+const locale = useLocaleConfig(localesConfig)
+
+// under `/page`
+locale.value // 'Title'
+
+// under `/zh/page`
+locale.value // '标题'
+Encode/decode and zip/unzip data.
+This is useful in markdown plugins when you want to encode string content and pass it to the component through props.
+You may simply achieve this with encodeURIComponent and decodeURIComponent, but it can be very large if the content contains lots of special characters.
Encode/decode and zip/unzip data.
+This is useful in markdown plugins when you want to encode string content and pass it to the component through props.
+You may simply achieve this with encodeURIComponent and decodeURIComponent, but it can be very large if the content contains lots of special characters.
So we provide encodeData and decodeData to zip and encode content.
export const encodeData: (
+ data: string,
+ level: DeflateOptions['level'] = 6,
+) => string
+
+export const decodeData: (compressed: string) => string
+const content = `
+{
+ "type": "bar",
+ "data": {
+ "labels": ["Red", "Blue", "Yellow", "Green", "Purple", "Orange"],
+ "datasets": [
+ {
+ "label": "# of Votes",
+ "data": [12, 19, 3, 5, 2, 3],
+ "backgroundColor": [
+ "rgba(255, 99, 132, 0.2)",
+ "rgba(54, 162, 235, 0.2)",
+ "rgba(255, 206, 86, 0.2)",
+ "rgba(75, 192, 192, 0.2)",
+ "rgba(153, 102, 255, 0.2)",
+ "rgba(255, 159, 64, 0.2)"
+ ],
+ "borderColor": [
+ "rgba(255, 99, 132, 1)",
+ "rgba(54, 162, 235, 1)",
+ "rgba(255, 206, 86, 1)",
+ "rgba(75, 192, 192, 1)",
+ "rgba(153, 102, 255, 1)",
+ "rgba(255, 159, 64, 1)"
+ ],
+ "borderWidth": 1
+ }
+ ]
+ },
+ "options": {
+ "scales": {
+ "y": {
+ "beginAtZero": true
+ }
+ }
+ }
+}
+`
+
+const prop = encodeData(content) // "eJyNUsFOwzAMve8rrHABKZqWlg5WxAE4cARxAMHEIV1NmQhNlaaCCe3fcdKtW0sLWGpjxy/v+UV512mlcIyfhTa2hHP4GgHYVYExsEQaxqlMpZWxbwAomaAqY5izO0wZB3apKnTrIyqlP1x2bRBzl9xWplC+eWNkniF7dmw1X4nWsfgaNtwNP2kfgH6Be22x9CPUUQ8yFwEHMeMQcog4UBFuiF0kcvGWGV3l6ZVW2uw0XDCTJfIwiOjYjAhESIcn4+BoT2MLio6pP6V+EBJ6AOSZgsmUwyl9A6ATwoiZn3lYTkTkRkycnuP8TU9ENPqUxuuA9i9BmxTNPy9A/G2/F9I23wtpW++FdIwPKzW2W5Afph+WqX2NQWz313XicT7XhV3qnB5f/ejKhVTYVACrXUqUmC3zC/uERsdgTYUdVr/Qb302+gZxe7S/"
+
+decodeData(prop) // will be the original content
+
+// if you use `encodeURIComponent`, it will be much longer
+encodeURIComponent(content) // '%0A%7B%0A%20%20%22type%22%3A%20%22bar%22%2C%0A%20%20%22data%22%3A%20%7B%0A%20%20%20%20%22labels%22%3A%20%5B%22Red%22%2C%20%22Blue%22%2C%20%22Yellow%22%2C%20%22Green%22%2C%20%22Purple%22%2C%20%22Orange%22%5D%2C%0A%20%20%20%20%22datasets%22%3A%20%5B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%22label%22%3A%20%22%23%20of%20Votes%22%2C%0A%20%20%20%20%20%20%20%20%22data%22%3A%20%5B12%2C%2019%2C%203%2C%205%2C%202%2C%203%5D%2C%0A%20%20%20%20%20%20%20%20%22backgroundColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%200.2)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%201)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderWidth%22%3A%201%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%0A%20%20%7D%2C%0A%20%20%22options%22%3A%20%7B%0A%20%20%20%20%22scales%22%3A%20%7B%0A%20%20%20%20%20%20%22y%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22beginAtZero%22%3A%20true%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A'
+isDef(x): Check if x is defined.isBoolean(x): Check if x is a boolean.isString(x): Check if x is a string.isNumber(x): Check if x is a number.isPlainObject(x): Check if x is a plain object.isArray(x): Check if x is an array.isFunction(x): Check if x is a function.isRegExp(x): Check if x is a regular expression.startsWith(a, b): Check if string a starts with string b.endsWith(a, b): Check if string a ends with string b.Return false if a is not a string.
keys(x): Return an array of keys of object x.
values(x): Return an array of values of object x.
entries(x): Convert object x to an array of key-value pairs.
fromEntries(x): Convert an array of key-value pairs x to an object.
deepAssign(x, y, ...): A deep version of Object.assign.
// or @vuepress/helper/client
+import { deepAssign } from '@vuepress/helper'
+
+const defaultOptions = {
+ optionA: {
+ optionA1: 'defaultOptionA1',
+ optionA2: 'defaultOptionA2',
+ optionA3: 'defaultOptionA3',
+ },
+ optionB: true,
+ optionC: 'optionC',
+}
+
+const userOptions = {
+ optionA: {
+ optionA1: 'optionA1',
+ optionA2: 'optionA2',
+ },
+ optionB: false,
+}
+
+deepAssign(defaultOptions, userOptions)
+// {
+// optionA: {
+// optionA1: "optionA1",
+// optionA2: "optionA2",
+// optionA3: "defaultOptionA3",
+// },
+// optionB: false,
+// optionC: "optionC",
+// }
+getDate(x): Convert input x to a date. It can support Date, timestamp, and date string. The support degree of date string depends on the Date.parse support degree of the environment. Return null when it cannot be converted to a date.
getDate('2021-01-01') // a Date object represents 2021-01-01
+getDate(1609459200000) // a Date object represents 2021-01-01
+getDate('2021-01-01T00:00:00.000Z') // a Date object represents 2021-01-01
+getDate('2021/01/01') // a Date object represents 2021-01-01 (might be null in some browsers)
+getDate('invalid date') // null
+getDate(undefined) // null
+getDate(-32) // null
+dateSorter: Sort the values that can be converted to dates from new to old, and the values that cannot be converted to dates will be at the end.
const arr = [
+ '2020-01-01',
+ 1609459200000,
+ '2022-01-01T00:00:00.000Z',
+ '2023/01/01',
+ 'invalid date',
+ undefined,
+ -32,
+]
+
+arr.sort(dateSorter)
+// [
+// '2023/01/01',
+// '2022-01-01T00:00:00.000Z',
+// 1609459200000,
+// '2020-01-01',
+// 'invalid date',
+// undefined,
+// -32,
+// ]
+isLinkHttp(x): Check if x is a valid HTTP URL.isLinkWithProtocol(x): Check if x is a valid URL with protocol.isLinkExternal(x): Check if x is a valid external URL.isLinkAbsolute(x): Check if x is a valid absolute URL.ensureEndingSlash(x): Ensure x ends with a slash.ensureLeadingSlash(x): Ensure x starts with a slash.removeEndingSlash(x): Ensure x does not end with a slash.removeLeadingSlash(x): Ensure x does not start with a slash.Come to your blog, or anywhere, place the Artalk comment box, so that the page has rich social functions.
+]]>Come to your blog, or anywhere, place the Artalk comment box, so that the page has rich social functions.
+ +npm i -D artalk
+See the Artalk documentation.
+Please set provider: "Artalk" and pass your server link to server in the plugin options.
For other configuration items, see Artalk Config.
+TIP
+The plugin retains the el option and inserts Artalk itself on the page. At the same time, the plugin will automatically set the pageTitle, pageKey and site options for you according to the VuePress information.
To let Artalk apply the correct theme, you need to pass a boolean value to <CommentService /> through darkmode prop, representing whether the dark mode is currently enabled.
See Artalk Configuration for details.
+The el pageTitle, pageKey and site options are reserved for plugins, they will be inferred from VuePress config.
Two function options imgUploader and avatarURLBuilder can only be set on client side.
See Artalk Configuration for details.
+The el pageTitle, pageKey and site options are reserved for plugins, they will be inferred from VuePress config.
Two function options imgUploader and avatarURLBuilder can only be set on client side.
You can directly configure serializable options in the plugin options:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineArtalkConfig function to customize Artalk:
import { defineClientConfig } from 'vuepress/client'
+import { defineArtalkConfig } from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // Artalk config
+})
+
+export default defineClientConfig({
+ // ...
+})
+Create a public repository and open discussion panel as a place to store comments.
+Install the Giscus App to have permission to access the corresponding repository.
+After completing the above steps, please go to the Giscus page to get your settings.
+You just need to fill in the repository and Discussion categories, then scroll to the "Enable giscus" section at the bottom of the page and obtain four attributes: data-repo, data-repo-id, data-category and data-category-id.
Please set provider: "Giscus" and pass data-repo, data-repo-id, data-category and data-category-id as plugin options as repo, repoId, category categoryId.
For other options, see Giscus Config.
+By default, the theme of Giscus is light or dark (based on darkmode status).
Darkmode
+To let Giscus apply the correct theme, you need to pass a boolean value to <CommentService /> via darkmode property, indicating whether darkmode is currently enabled.
If you want to customize theme in lightmode and darkmode, you can set lightTheme and darkTheme option with a built-in theme keyword or a custom CSS link starting with https://.
stringstringstringstringstringstringstring"pathname"booleantruebooleantruebooleantrue"top" | "bottom""top"Type: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+Default: "light"
Details:
+Giscus theme used in lightmode
+Should be a built-in theme keyword or a css link starting with https://.
Type: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+Default: "dark"
Details:
+Giscus theme used in darkmode
+Should be a built-in theme keyword or a css link starting with https://.
You can directly configure serializable options in the plugin options:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Giscus',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineGiscusConfig function to customize Giscus:
import { defineClientConfig } from 'vuepress/client'
+import { defineGiscusConfig } from 'vuepress-plugin-comment2/client'
+
+defineGiscusConfig({
+ // Giscus config
+})
+
+export default defineClientConfig({
+ // ...
+})
+npm i -D twikoo
+Apply for MongoDB account
+Create a free MongoDB database, the recommended region is AWS / N. Virginia (us-east-1)
Click CONNECT on the Clusters page, follow the steps to allow connections from all IP addresses (Why?), create Database user, and record the database connection string, please change the <password> in the connection string to the database password
Sign up for a Vercel account
+Click the button below to deploy Twikoo to Vercel in one click
+Go to Settings - Environment Variables, add the environment variable MONGODB_URI, the value is the database connection string in step 3
Go to Overview, click the link under Domains, if the environment configuration is correct, you can see the prompt "Twikoo cloud function is running normally"
+Vercel Domains (with https:// prefix, e.g. https://xxx.vercel.app) is your environment ID
Please set provider: "Twikoo" and set envId in the plugin options.
For other configuration items, see Twikoo Config.
+]]>stringYou can directly configure serializable options in the plugin options:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Twikoo',
+ // other options
+ // ...
+ }),
+ ],
+})
+stringYou can directly configure serializable options in the plugin options:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Twikoo',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineTwikooConfig function to customize Twikoo:
import { defineClientConfig } from 'vuepress/client'
+import { defineTwikooConfig } from 'vuepress-plugin-comment2/client'
+
+defineTwikooConfig({
+ // Twikoo config
+})
+
+export default defineClientConfig({
+ // ...
+})
+npm i -D @waline/client
+Click Create app button to create a new app and enter a name you like:
+ +Enter the app, then select Settings > App Keys at the left bottom corner. You will see APP ID, APP Key and Master Key of your app. We will use them later
Click the dark button above, it will redirect you to vercel to deploy with waline template.
+TIP
+If you haven't logged in, we recommend you to sign in with GitHub.
+Input your Vercel project name then click Create.
Repo which named you input before will be created and initialized automatically base on waline example template by Vercel.
+
After one minute or two, vercel should finish the deployment. Click Go to Dashboard button to redirect to your application dashboard.
Click Settings menu on the top, and Environment Variables button on the side to go to environment variables setting page. Then set LEAN_ID, LEAN_KEY and LEAN_MASTER_KEY. The variables' value should be the ones you got in the previous step. APP ID is the value of LEAN_ID, and APP Key to LEAN_KEY, Master Key to LEAN_MASTER_KEY.
To let your environment variables setting active, you need redeploy your application. Click Deployments menu on the top and find the latest deployment at the top of list, click Redeploy button in the right dropdown menu.
If everything is ok, vercel will redirect to Overview page to start redeployment. Wait a moment the STATUS will change to Ready. Now you can click Visit to visit the site. This link is your server address.
Click Settings - Domains to go to domain setting page.
Input domain you want to assign and click Add button.
Add a new CNAME record in your domain service server.
| Type | Name | Value | +|
+stringType: (string | WalineEmojiInfo)[] | false
type WalineEmojiPresets = `http://${string}` | `https://${string}`
+
+interface WalineEmojiInfo {
+ /**
+ * Emoji name show on tab
+ */
+ name: string
+ /**
+ * Current folder link
+ */
+ folder?: string
+ /**
+ * Common prefix of Emoji icons
+ */
+ prefix?: string
+ /**
+ * Type of Emoji icons, will be regarded as file extension
+ */
+ type?: string
+ /**
+ * Emoji icon show on tab
+ */
+ icon: string
+ /**
+ * Emoji image list
+ */
+ items: string[]
+}
+Default: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
Reference:
+ +Details: Emoji settings.
+stringType: (string | WalineEmojiInfo)[] | false
type WalineEmojiPresets = `http://${string}` | `https://${string}`
+
+interface WalineEmojiInfo {
+ /**
+ * Emoji name show on tab
+ */
+ name: string
+ /**
+ * Current folder link
+ */
+ folder?: string
+ /**
+ * Common prefix of Emoji icons
+ */
+ prefix?: string
+ /**
+ * Type of Emoji icons, will be regarded as file extension
+ */
+ type?: string
+ /**
+ * Emoji icon show on tab
+ */
+ icon: string
+ /**
+ * Emoji image list
+ */
+ items: string[]
+}
+Default: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
Reference:
+ +Details: Emoji settings.
+Type: string | boolean
Default: false
Reference:
+Details:
+Darkmode support
+'auto' will display darkmode due to device settings.Type: WalineCommentSorting
Default: 'latest'
Details:
+Comment list sorting methods.
+Optional values: 'latest', 'oldest', 'hottest'
Type: string[]
Default: ['nick','mail','link']
Details:
+Reviewer attributes.
+Optional values: 'nick', 'mail', 'link'
Type: string[]
Default: []
Details:
+Set required fields, optional values:
+[]['nick']['nick','mail']Type: string
Default value: 'enable'
Details:
+Login mode status, optional values:
+'enable': enable login (default)'disable': Login is disabled, users should fill in information to comment'force': Forced login, users must login to commentType: number | [number, number]
Default: 0
Details:
+Comment words limit. When a single number is filled in, it 's the maximum number of comment words. No limit when set to 0.
Type: number
Default: 10
Details:
+Number of comments per page.
+Type: WalineImageUploader | false
type WalineImageUploader = (image: File) => Promise<string>
+Reference:
+ +Details:
+Custom image upload method. The default behavior is to embed images Base 64 encoded, you can set this to false to disable image uploading.
The function should receive an image object and return a Promise that provides the image address.
+Type: WalineHighlighter | false
type WalineHighlighter = (code: string, lang: string) => string
+Reference:
+ +Details:
+Code highlighting, use hanabi by default. The function passes in original content of code block and language of the code block. You should return a string directly.
You can pass in a code highlighter of your own, or set to false to disable code highlighting.
Type: WalineTexRenderer | false
type WalineTexRenderer = (blockMode: boolean, tex: string) => string
+Reference:
+ +Details:
+Customize TeX rendering, the default behavior is to prompt that the preview mode does not support TeX. The function provides two parameters, the first parameter indicates whether it should be rendered in block level, and the second parameter is the string of the TeX content, and return a HTML string as render result.
+You can import TeX renderer to provide preview feature. We recommend you to use Katex or MathJax, or you can set to false to disable parsing TeX.
Type: WalineSearchOptions | false
interface WalineSearchImageData extends Record<string, unknown> {
+ /**
+ * Image link
+ */
+ src: string
+
+ /**
+ * Image title
+ *
+ * @description Used for alt attribute of image
+ */
+ title?: string
+
+ /**
+ * Image preview link
+ *
+ * @description For better loading performance, we will use this thumbnail first in the list
+ *
+ * @default src
+ */
+ preview?: string
+}
+
+type WalineSearchResult = WalineSearchImageData[]
+
+interface WalineSearchOptions {
+ /**
+ * Search action
+ */
+ search: (word: string) => Promise<WalineSearchResult>
+
+ /**
+ * Default result when opening list
+ *
+ * @default () => search('')
+ */
+ default?: () => Promise<WalineSearchResult>
+
+ /**
+ * Fetch more action
+ *
+ * @description It will be triggered when the list scrolls to the bottom. If your search service supports paging, you should set this to achieve infinite scrolling
+ *
+ * @default (word) => search(word)
+ */
+ more?: (word: string, currentCount: number) => Promise<WalineSearchResult>
+}
+Details: Customize search features, you can disable search function by setting it to false.
Type: string
Details:
+reCAPTCHA V3 is a captcha service provided by Google. You can add reCAPTCHA V3 site key with recaptchaV3Key to enable it.
You should also set environment variable RECAPTCHA_V3_SECRET for server.
Type: boolean | string[]
Default: false
Details:
+Add emoji interaction function to the article, set it to true to provide the default emoji, you can also customize the emoji image by setting the emoji url array, and supports a maximum of 8 emojis.
booleantrueType: WalineLocales
interface WalineLocales {
+ [localePath: string]: WalineLocale
+}
+Reference:
+ +Details: +Waline locales.
+You can directly configure serializable options in the plugin options:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Waline',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineWalineConfig function to customize Waline:
import { defineClientConfig } from 'vuepress/client'
+import { defineWalineConfig } from 'vuepress-plugin-comment2/client'
+
+defineWalineConfig({
+ // Waline config
+})
+
+export default defineClientConfig({
+ // ...
+})
+All functions should be called in extendsBundlerOptions lifecycle hook.
TIP
+We are omitting that in examples. The actual code should be like this:
+// import functions you need
+import { addCustomElement } from '@vuepress/helper'
+
+export const yourPlugin = {
+ // ...
+ extendsBundlerOptions: (bundlerOptions, app) => {
+ // add them here
+ addCustomElement(bundlerOptions, app, 'my-custom-element')
+ },
+}
+All functions should be called in extendsBundlerOptions lifecycle hook.
TIP
+We are omitting that in examples. The actual code should be like this:
+// import functions you need
+import { addCustomElement } from '@vuepress/helper'
+
+export const yourPlugin = {
+ // ...
+ extendsBundlerOptions: (bundlerOptions, app) => {
+ // add them here
+ addCustomElement(bundlerOptions, app, 'my-custom-element')
+ },
+}
+Get current bundler name.
+export const getBundlerName: (app: App) => string
+// @vuepress/bundler-vite
+getBundleName(app) === 'vite' // true
+// @vuepress/bundler-webpack
+getBundleName(app) === 'webpack' // true
+Add a custom element declaration to the current bundler.
+/**
+ * Add tags as customElement
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param customElements tags recognized as custom element
+ */
+export const addCustomElement = (
+ bundlerOptions: unknown,
+ app: App,
+ customElement: string[] | string | RegExp
+) => void;
+import { addCustomElement } from '@vuepress/helper'
+
+addCustomElement(bundlerConfig, app, 'my-custom-element')
+addCustomElement(bundlerOptions, app, [
+ 'custom-element1',
+ 'custom-element2',
+ // all tags start with `math-`
+ /^math-/,
+])
+Provides contents for specific path in dev server.
+export interface DevServerOptions {
+ /**
+ * Path to be responded
+ */
+ path: string;
+ /**
+ * Respond function
+ */
+ response: (request?: IncomingMessage) => Promise<string | Buffer>;
+
+ /**
+ * error msg
+ */
+ errMsg?: string;
+}
+
+/**
+ * Handle specific path when running VuePress Dev Server
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param path Path to be responded
+ * @param response respond function
+ * @param errMsg error msg
+ */
+export const customizeDevServer: (
+ bundlerOptions: unknown,
+ app: App,
+ {
+ errMsg:"The server encountered an error",
+ response: responseHandler,
+ path,
+ }: CustomServerOptions
+) => void;
+import { useCustomDevServer } from '@vuepress/helper'
+
+// handle `/api/` path
+useCustomDevServer(bundlerOptions, app, {
+ path: '/api/',
+ response: async () => getData(),
+ errMsg: 'Unexpected api error',
+})
+addViteOptimizeDepsInclude
+Add modules to Vite optimizeDeps.include list
TIP
+If a package meets one of the following conditions, you should consider adding it here.
+import()addViteOptimizeDepsExclude
+Add modules to Vite optimizeDeps.exclude list
If a package and its dependencies are all pure ESM packages, you should consider adding it here.
+addViteSsrExternal
+Add modules to Vite ssr.external list
If a package is a pure ESM package and does not use aliases or define variables, you should consider adding it here.
+addViteSsrNoExternal
+Add modules to Vite ssr.noExternal list
If an alias or define is used within a package, you must add it here.
+/**
+ * Add modules to Vite `optimizeDeps.include` list
+ */
+export const addViteOptimizeDepsInclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `optimizeDeps.exclude` list
+ */
+export const addViteOptimizeDepsExclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.external` list
+ */
+export const addViteSsrExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.noExternal` list
+ */
+export const addViteSsrNoExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+import {
+ addViteOptimizeDepsInclude,
+ addViteOptimizeDepsExclude,
+ addViteSsrExternal,
+ addViteSsrNoExternal,
+} from '@vuepress/helper'
+
+addViteOptimizeDepsInclude(bundlerOptions, app, ['vue', 'vue-router'])
+addViteOptimizeDepsExclude(bundlerOptions, app, 'packageA')
+addViteSsrNoExternal(bundlerOptions, app, ['vue', 'vue-router'])
+addViteSsrExternal(bundlerOptions, app, 'packageA')
+addViteConfig
+A function for you to add vite config
+export const addViteConfig: (
+ bundlerOptions: unknown,
+ app: App,
+ config: Record<string, unknown>,
+) => void
+import { addViteConfig } from '@vuepress/helper'
+
+addViteConfig(bundlerOptions, app, {
+ build: {
+ charset: 'utf8',
+ },
+})
+mergeViteConfig
+A function for you to merge vite config.
+WARNING
+Your users may choose to use other bundler so it's pretty bad to declare vite as deps!
+export const mergeViteConfig: (
+ defaults: Record<string, any>,
+ overrides: Record<string, any>,
+) => Record<string, any>
+import { mergeViteConfig } from '@vuepress/helper'
+
+config.viteOptions = mergeViteConfig(config.viteOptions, {
+ build: {
+ charset: 'utf8',
+ },
+})
+chainWebpack
+Chain webpack config.
+export const chainWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ chainWebpack: (
+ config: WebpackChainConfig,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { chainWebpack } from '@vuepress/helper'
+
+chainWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+configWebpack
+Config Webpack
+export const configWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ configureWebpack: (
+ config: WebpackConfiguration,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { configWebpack } from '@vuepress/helper'
+
+configWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+Get the excerpt of the page.
+export interface PageExcerptOptions {
+ /**
+ * Excerpt separator
+ *
+ * @default "Get the excerpt of the page.
+export interface PageExcerptOptions {
+ /**
+ * Excerpt separator
+ *
+ * @default "<!-- more -->"
+ */
+ separator?: string
+
+ /**
+ * Length of excerpt
+ *
+ * @description Excerpt length will be the minimal possible length reaching this value
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * Tags which is considered as custom elements
+ *
+ * @description This is used to determine whether a tag is a custom element since all unknown tags are removed in excerpt.
+ */
+ isCustomElement?: (tagName: string) => boolean
+
+ /**
+ * Whether keep page title (first h1) in excerpt
+ *
+ * @default false
+ */
+ keepPageTitle?: boolean
+
+ /**
+ * Whether preserve tags like line numbers and highlight lines for code blocks
+ *
+ * @default false
+ */
+ keepFenceDom?: boolean
+}
+
+export const getPageExcerpt: (
+ app: App,
+ page: Page,
+ options?: PageExcerptOptions,
+) => string
+Get plain text of the page.
+export interface PageTextOptions {
+ /**
+ * Whether convert text to single line content
+ *
+ * @default false
+ */
+ singleLine?: boolean
+
+ /**
+ * Length of text
+ *
+ * @description Text length will be the minimal possible length reaching this value
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * Tags to be removed
+ *
+ * @description Table and code blocks are removed by default.
+ *
+ * @default ['table', 'pre']
+ */
+ removedTags?: string[]
+}
+
+export const getPageText: (
+ app: App,
+ page: Page,
+ options?: PageTextOptions,
+) => string
+| Last update time: | +
+ |
+
| Author: | +
+ |
+
| Contributor: | +
+ |
+
| Categories: | +
+ |
+
| Copyright: | +
+ |
+
Type: string
Details:
\nHostname to be deployed, e.g.: https://example.com
Type: { [path: string]: Partial<DefaultThemeLocaleData> }
Default: {}
Details:
\nSpecify locales for i18n support.
\nAll the options inside the Locale Config section can be used in locales.
\nThis option will only take effect in default theme, so don't confuse with locales in Site Config.
Also see:
\nConfig of this section can be used as normal config, and can also be used in the locales option.
\nType: 'auto' | 'light' | 'dark'
Default: 'auto'
Details:
\nDefault color mode.
\nIf set to 'auto', the initial color mode will be automatically set according to prefers-color-scheme.
Also see:
\n\nType: boolean
Default: true
Details:
\nEnable color mode switching or not.
\nIf set to true, a button to switch color mode will be displayed in the navbar.
Also see:
\n\nType: string
Default: /
Details:
\nSpecify the path of the homepage.
\nThis will be used for:
\nType: false | (NavbarItem | NavbarGroup | string)[]
Default: []
Details:
\nConfiguration of navbar.
\nSet to false to disable navbar.
To configure the navbar items, you can set it to a navbar array, each item of which could be a NavbarItem object, a NavbarGroup object, or a string:
NavbarItem object should have a text field and a link field, could have an optional activeMatch field.NavbarGroup object should have a text field and a children field. The children field should be a navbar array, too.NavbarItem object, using the page title as text, and the page route path as link.Example 1:
\nexport default {\n theme: defaultTheme({\n navbar: [\n // NavbarItem\n {\n text: 'Foo',\n link: '/foo/',\n },\n // NavbarGroup\n {\n text: 'Group',\n children: ['/group/foo.md', '/group/bar.md'],\n },\n // string - page file path\n '/bar/README.md',\n ],\n }),\n}\nexport default {\n theme: defaultTheme({\n navbar: [\n // nested group - max depth is 2\n {\n text: 'Group',\n children: [\n {\n text: 'SubGroup',\n children: ['/group/sub/foo.md', '/group/sub/bar.md'],\n },\n ],\n },\n // control when should the item be active\n {\n text: 'Group 2',\n children: [\n {\n text: 'Always active',\n link: '/',\n // this item will always be active\n activeMatch: '/',\n },\n {\n text: 'Active on /foo/',\n link: '/not-foo/',\n // this item will be active when current route path starts with /foo/\n // regular expression is supported\n activeMatch: '^/foo/',\n },\n ],\n },\n ],\n }),\n}\nType: null | string
Details:
\nSpecify the url of logo image.
\nThe logo image will be displayed at the left end of the navbar.
\nSet to null to disable logo.
Example:
\nexport default {\n theme: defaultTheme({\n // public file path\n logo: '/hero.png',\n // url\n logo: 'https://vuejs.org/images/logo.png',\n }),\n}\nType: null | string
Details:
\nSpecify the url of logo image to be used in dark mode.
\nYou can make use of this option if you want to use different logo config in dark mode.
\nSet to null to disable logo in dark mode. Omit this option to use logo in dark mode.
Also see:
\n\nType: null | string
Details:
\nSpecify the alt text of the logo image.
\nIf not specified, defaults to be the same as the site title.
\nType: string
Details:
\nSpecify the repository url of your project.
\nThis will be used as the link of the repository link, which will be displayed as the last item of the navbar.
\nexport default {\n theme: defaultTheme({\n // If you set it in the form of `organization/repository`\n // we will take it as a GitHub repo\n repo: 'vuejs/vuepress',\n // You can also set it to a URL directly\n repo: 'https://gitlab.com/foo/bar',\n }),\n}\nType: false | 'auto' | SidebarConfigArray | SidebarConfigObject
Default: 'auto'
Details:
\nConfiguration of sidebar.
\nYou can override this global option via sidebar frontmatter in your pages.
\nSet to false to disable sidebar.
If you set it to 'auto', the sidebar will be automatically generated from the page headers.
To configure the sidebar items manually, you can set this option to a sidebar array, each item of which could be a SidebarItem object or a string:
SidebarItem object should have a text field, could have an optional link field, an optional children field and an optional collapsible field. The children field should be a sidebar array. The collapsible field controls whether the item is collapsible.SidebarItem object, whose text is the page title, link is the page route path, and children is automatically generated from the page headers.If you want to set different sidebar for different sub paths, you can set this option to a sidebar object:
\n'heading' to automatically generate the sidebar from the page headers for just the corresponding path.Example 1:
\nexport default {\n theme: defaultTheme({\n // sidebar array\n // all pages will use the same sidebar\n sidebar: [\n // SidebarItem\n {\n text: 'Foo',\n link: '/foo/',\n children: [\n // SidebarItem\n {\n text: 'github',\n link: 'https://github.com',\n children: [],\n },\n // string - page file path\n '/foo/bar.md',\n ],\n },\n // string - page file path\n '/bar/README.md',\n ],\n }),\n}\nexport default {\n theme: defaultTheme({\n // sidebar object\n // pages under different sub paths will use different sidebar\n sidebar: {\n '/guide/': [\n {\n text: 'Guide',\n children: ['/guide/introduction.md', '/guide/getting-started.md'],\n },\n ],\n '/reference/': 'heading',\n },\n }),\n}\nexport default {\n theme: defaultTheme({\n // collapsible sidebar\n sidebar: {\n '/reference/': [\n {\n text: 'VuePress Reference',\n collapsible: true,\n children: ['/reference/cli.md', '/reference/config.md'],\n },\n {\n text: 'Bundlers Reference',\n collapsible: true,\n children: [\n '/reference/bundler/vite.md',\n '/reference/bundler/webpack.md',\n ],\n },\n ],\n },\n }),\n}\nType: number
Default: 2
Details:
\nSet the maximum depth of the sidebar children which are automatically generated from the page headers.
\n0 to disable all levels of headers.1 to include <h2> headers.2 to include <h2> and <h3> headers.The max value depends on which levels of headers you have extracted via markdown.headers.level.
\nThe default value of markdown.headers.level is [2, 3], so the default max value of sidebarDepth is 2.
You can override this global option via sidebarDepth frontmatter in your pages.
\nType: boolean
Default: true
Details:
\nEnable the edit this page link or not.
\nYou can override this global option via editLink frontmatter in your pages.
\nType: string
Details:
\nSpecify the pattern of the edit this page link.
\nThis will be used for generating the edit this page link.
\nIf you don't set this option, the pattern will be inferred from the docsRepo option. But if your documentation repository is not hosted on a common platform, for example, GitHub, GitLab, Bitbucket, Gitee, etc., you have to set this option explicitly to make the edit this page link work.
\nUsage:
\n| Pattern | Description |\n|
\nVuePress default theme is widely used by users, so it is designed to be extendable, allowing users to make their own customization with ease.
\nDefault theme's Layout provides some slots:
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottomWith the help of them, you can add or replace content easily. Here comes an example to introduce how to extend default theme with layout slots.
\nFirstly, create a client config file .vuepress/client.ts:
import { defineClientConfig } from 'vuepress/client'\nimport Layout from './layouts/Layout.vue'\n\nexport default defineClientConfig({\n layouts: {\n Layout,\n },\n})\nNext, create the .vuepress/layouts/Layout.vue, and make use of the slots that provided by the Layout of default theme:
<script setup>\nimport ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'\n</script>\n\n<template>\n <ParentLayout>\n <template #page-bottom>\n <div class=\"my-footer\">This is my custom page footer</div>\n </template>\n </ParentLayout>\n</template>\n\n<style lang=\"css\">\n.my-footer {\n text-align: center;\n}\n</style>\nThen the default Layout layout has been overridden by your own local layout, which will add a custom footer to every normal pages in default theme (excluding homepage):
![\"extending-a-theme\"](\"/images/cookbook/extending-a-theme-01.png\")
The layout slots are useful, but sometimes you might find it's not flexible enough. Default theme also provides the ability to replace a single component.
\nDefault theme has registered alias for every non-global components with a @theme prefix. For example, the alias of HomeFooter.vue is @theme/HomeFooter.vue.
Then, if you want to replace the HomeFooter.vue component, just override the alias in your config file .vuepress/config.ts:
import { defaultTheme } from '@vuepress/theme-default'\nimport { getDirname, path } from 'vuepress/utils'\nimport { defineUserConfig } from 'vuepress'\n\nconst __dirname = getDirname(import.meta.url)\n\nexport default defineUserConfig({\n theme: defaultTheme(),\n alias: {\n '@theme/HomeFooter.vue': path.resolve(\n __dirname,\n './components/MyHomeFooter.vue',\n ),\n },\n})\nInstead of extending the default theme directly in .vuepress/config.ts and .vuepress/client.ts, you can also develop your own theme extending the default theme:
import { defaultTheme, type DefaultThemeOptions } from '@vuepress/theme-default'\nimport type { Theme } from 'vuepress/core'\nimport { getDirname, path } from 'vuepress/utils'\n\nconst __dirname = getDirname(import.meta.url)\n\nexport const childTheme = (options: DefaultThemeOptions): Theme => {\n return {\n name: 'vuepress-theme-child',\n extends: defaultTheme(options),\n\n // override layouts in child theme's client config file\n // notice that you would build ts to js before publishing to npm,\n // so this should be the path to the js file\n clientConfigFile: path.resolve(__dirname, './client.js'),\n\n // override component alias\n alias: {\n '@theme/HomeFooter.vue': path.resolve(\n __dirname,\n './components/MyHomeFooter.vue',\n ),\n },\n }\n}\nThese options configure locale-related texts.
\nIf your site is served in a different language besides English, you should set these options per locale to provide translations.
\nType: string
Details:
\nSpecify the repository label of your project.
\nThis will be used as the text of the repository link, which will be displayed as the last item of the navbar.
\nIf you don't set this option explicitly, it will be automatically inferred from the repo option.
\nType: string
Details:
\nSpecify the text of the select language menu.
\nThe select language menu will appear next to the repository button in the navbar when you set multiple locales in your site config.
\nType: string
Details:
\nSpecify the aria-label attribute of the select language menu.
This is mainly for a11y purpose.
\nType: string
Details:
\nSpecify the name of the language of a locale.
\nThis option will only take effect inside the locales of your theme config. It will be used as the language name of the locale, which will be displayed in the select language menu.
\nExample:
\nexport default {\n locales: {\n '/': {\n lang: 'en-US',\n },\n '/zh/': {\n lang: 'zh-CN',\n },\n },\n theme: defaultTheme({\n locales: {\n '/': {\n selectLanguageName: 'English',\n },\n '/zh/': {\n selectLanguageName: '简体中文',\n },\n },\n }),\n}\nType: null | string
Details:
\naria-label value for main navigation in navbar.
Type: null | string
Details:
\naria-label value for next/previous page navigation.
Type: string
Default: 'Edit this page'
Details:
\nSpecify the text of the edit this page link.
\nType: string
Default: 'Last Updated'
Details:
\nSpecify the text of the last updated timestamp label.
\nType: string
Default: 'Contributors'
Details:
\nSpecify the text of the contributors list label.
\nType: string
Default: 'TIP'
Details:
\nSpecify the default title of the tip custom containers.
\nType: string
Default: 'WARNING'
Details:
\nSpecify the default title of the warning custom containers.
\nType: string
Default: 'DANGER'
Details:
\nSpecify the default title of the danger custom containers.
\nType: string[]
Default: ['Not Found']
Details:
\nSpecify the messages of the 404 page.
\nThe message will be randomly picked from the array when users enter the 404 page.
\nType: string
Default: 'Back to home'
Details:
\nSpecify the text of the back to home link in the 404 page.
\nType: string
Default: 'open in new window'
Details:
\nSpecify the sr-only text of the ExternalLinkIcon.
This is mainly for a11y purpose.
\nAlso see:
\n\nType: string
Default: 'toggle color mode'
Details:
\nTitle text for the color mode toggle button.
\nThis is mainly for a11y purpose.
\nAlso see:
\n\nType: string
Default: 'toggle sidebar'
Details:
\nTitle text for sidebar toggle button.
\nThis is mainly for a11y purpose.
\nType: string
Default: 'Prev'
Details:
\nText for the previous page navigation button.
\nType: string
Default: 'Next'
Details:
\nText for the next page navigation button.
\nYou can configure the plugins that used by default theme with themePlugins.
Default theme is using some plugins by default. You can disable a plugin if you really do not want to use it. Make sure you understand what the plugin is for before disabling it.
\nimport { defaultTheme } from '@vuepress/theme-default'\n\nexport default {\n theme: defaultTheme({\n themePlugins: {\n // customize theme plugins here\n },\n }),\n}\nType: boolean
Default: true
Details:
\nEnable @vuepress/plugin-active-header-links or not.
\nType: BackToTopPluginOptions | boolean
Default: true
Details:
\nEnable @vuepress/plugin-back-to-top or not.
\nObject value is supported as plugin options.
\nType: Record<ContainerType, boolean>
Details:
\nEnable custom containers that powered by @vuepress/plugin-container or not.
\nContainerType type is:
tipwarningdangerdetailscodeGroupcodeGroupItemAlso see:
\n\nType: CopyCodePluginOptions | boolean
Default: true
Details:
\nEnable @vuepress/plugin-copy-code or not.
\nObject value is supported as plugin options.
\nType: boolean
Default: true
Details:
\nEnable @vuepress/plugin-external-link-icon or not.
\nType: boolean
Default: true
Details:
\nEnable @vuepress/plugin-git or not.
\nType: LinksCheckPluginOptions | boolean
Default: true
Details:
\nEnable @vuepress/plugin-links-check or not.
\nType: boolean
Default: true
Details:
\nEnable @vuepress/plugin-medium-zoom or not.
\nType: boolean
Default: true
Details:
\nEnable @vuepress/plugin-nprogress or not.
\nType: boolean
Default: true
Details:
\nEnable @vuepress/plugin-prismjs or not.
\nType: SeoPluginOptions | boolean
Default: true
Details:
\nEnable @vuepress/plugin-seo or not.
\nObject value is supported as plugin options.
\nType: SitemapPluginOptions | boolean
Default: true
Details:
\nEnable @vuepress/plugin-sitemap or not.
\nObject value is supported as plugin options.
\nType: (page: Page) => Record<string, unknown>
Required: No
\nReference:
\n\nDetails:
\nFunction getting article info.
\nArticle info will be injected in route meta so that they will be available later in client composables.
\nType: (page: Page) => boolean
Default: (page) => Boolean(page.filePathRelative) && !page.frontmatter.home
Reference:
\n\nDetails:
\nPage filter, determine whether a page should be included.
\nBy default, all the pages generated from Markdown files but not homepage will be included as articles.
\nBlogCategoryOptions[]BlogTypeOptions[](name: string) => string(name) => name.replace(/ _/g, '-').replace(/[:?*|\\\\/<>]/g, \"\").toLowerCase()booleantruestring<!-- more -->Type: number
Default: 300
Reference:
\n\nDetails:
\nLength of excerpt when auto generating.
\nTIP
\nExcerpt length will be the minimal possible length reaching this value.
\nYou can set it to 0 to disable auto excerpt generation.
Type: (page: Page) => boolean
Default: filter option
Reference:
\n\nDetails:
\nPage filter, determine whether the plugin should generate excerpt for it.
\nTIP
\nYou should use this to skip pages that you don't need to generate excerpt for. E.g.: If users set excerpt or description in frontmatter, you may want to use them directly.
Type: (tagName: string) => boolean
Default: () => false
Reference:
\n\nDetails:
\nTags which is considered as custom elements.
\nThis is used to determine whether a tag is a custom element since all unknown tags are removed in excerpt.
\nType: string
Default: \"_blog\"
Details:
\nKey used when injecting info to route meta.
\nTIP
\nSetting to an empty key will inject to route meta directly instead of a field.
\nType: boolean
Default: Whether using --debug flag
Details:
\nWhether enable hotReload in devServer.
\nTo theme developers
\nIt's disabled by default because it does have performance impact in sites with a lot of categories and types. And it can slow down hotReload speed when editing Markdown.
\nIf users are adding or organizing your categories or tags, you may tell them to enable this, for the rest it's better to keep it disabled.
\nAlso, you can try to detect number of pages in users project and decide whether to enable it.
\nBlog category config should be an array, while each item is controlling a \"category\" rule.
\ninterface BlogCategoryOptions {\n /**\n * Unique category name\n */\n key: string\n\n /**\n * Function getting category from page\n */\n getter: (page: Page) => string[]\n\n /**\n * A custom function to sort the pages\n */\n sorter?: (pageA: Page, pageB: Page) => number\n\n /**\n * Path pattern of page to be registered\n *\n * @description `:key` will be replaced by the \"slugify\" result of the original key\n *\n * @default `/:key/`\n */\n path?: string\n\n /**\n * Page layout name\n *\n * @default 'Layout'\n */\n layout?: string\n\n /**\n * Frontmatter\n */\n frontmatter?: (localePath: string) => Record<string, string>\n\n /**\n * Item page path pattern or custom function to be registered\n *\n * @description When filling in a string, `:key` and `:name` will be replaced by the \"slugify\" result of the original key and name\n *\n * @default `/:key/:name/`\n */\n itemPath?: string | ((name: string) => string)\n\n /**\n * Item page layout name\n *\n * @default 'Layout'\n */\n itemLayout?: string\n\n /**\n * Items Frontmatter\n */\n itemFrontmatter?: (name: string, localePath: string) => Record<string, string>\n}\nBlog type config should be an array, while each item is controlling a \"type\" rule.
\ninterface BlogTypeOptions {\n /**\n * Unique type name\n */\n key: string\n\n /**\n * A filter function to determine whether a page should be the type\n */\n filter: (page: Page) => boolean\n\n /**\n * A custom function to sort the pages\n */\n sorter?: (pageA: Page, pageB: Page) => number\n\n /**\n * Page path to be registered\n *\n * @default '/:key/'\n */\n path?: string\n\n /**\n * Layout name\n *\n * @default 'Layout'\n */\n layout?: string\n\n /**\n * Frontmatter\n */\n frontmatter?: (localePath: string) => Record<string, string>\n}\nYou can import the following API from @vuepress/plugin-blog/client.
Blog category
\nconst useBlogCategory: <\n T extends Record<string, unknown> = Record<string, unknown>,\n>(\n key?: string,\n) => ComputedRef<BlogCategoryData<T>>\nArgument key should be the category unique key.
If no key is passed, the plugin will try to use the key in current path.
\nBlog category
\nconst useBlogType: <\n T extends Record<string, unknown> = Record<string, unknown>,\n>(\n key?: string,\n) => ComputedRef<BlogTypeData<T>>\nArgument key should be the type unique key.
If no key is passed, the plugin will try to use the key in current path.
\nReturning values are:
\ninterface Article<T extends Record<string, unknown> = Record<string, unknown>> {\n /** Article path */\n path: string\n /** Article info */\n info: T\n}\n\ninterface BlogCategoryData<\n T extends Record<string, unknown> = Record<string, unknown>,\n> {\n /** Category path */\n path: string\n\n /**\n * Only available when current route matches an item path\n */\n currentItems?: Article<T>[]\n\n /** Category map */\n map: {\n /** Unique key under current category */\n [key: string]: {\n /** Category path of the key */\n path: string\n /** Category items of the key */\n items: Article<T>[]\n }\n }\n}\n\ninterface BlogTypeData<\n T extends Record<string, unknown> = Record<string, unknown>,\n> {\n /** Type path */\n path: string\n\n /** Items under current type */\n items: Article<T>[]\n}\nWith @vuepress/plugin-blog, you can easily bring blog feature into your theme.
The plugin filters all pages using filter option to drop pages you don't want.
By default, all pages generating from Markdown files but not homepage are considered as articles.
\nYou can fully customize pages to collect through option filter, which accepts a function (page: Page) => boolean.
You should set getInfo option with a function accepting Page as argument and returning an object containing the info you want.
The plugin will collect all the info you want and write them to routeMeta field of each page, so you will be able to get this information through Composition API later.
import { blogPlugin } from '@vuepress/plugin-blog'\n\nexport default {\n name: 'vuepress-theme-xxx',\n plugins: [\n blogPlugin({\n filter: ({ filePathRelative, frontmatter }) => {\n // drop those pages which is NOT generated from file\n if (!filePathRelative) return false\n\n // drop those pages in `archives` directory\n if (filePathRelative.startsWith('archives/')) return false\n\n // drop those pages which do not use default layout\n if (frontmatter.home || frontmatter.layout) return false\n\n return true\n },\n\n getInfo: ({ frontmatter, git = {}, data = {} }) => {\n // getting page info\n const info: Record<string, any> = {\n author: frontmatter.author || '',\n categories: frontmatter.categories || [],\n date: frontmatter.date || git.createdTime || null,\n tags: frontmatter.tags || [],\n excerpt: data.excerpt || '',\n }\n\n return info\n },\n }),\n // other plugins ...\n ],\n}\nBasically, you would want 2 types of collection in your blog:
\nCategory:
\n\"Category\" means grouping articles with their labels.
\nFor example, each article may have their \"categories\" and \"tags\".
\nType:
\n\"Type\" means identifying articles with conditions.
\nFor example, you may want to describe some of your articles as diary.
\nAfter understanding description of these 2 types, you can set category and type options, each accepts an array, and each element represents a configuration.
Let's start with 2 examples here.
\nImagine you are setting tags for each articles with tag field in page frontmatter. You want a tag mapping page in /tag/ with TagMap layout, and group each tag list with tagName in /tag/tagName with TagList layout, you probably need a configuration like this:
import { blogPlugin } from '@vuepress/plugin-blog'\n\nexport default {\n name: 'vuepress-theme-xxx',\n plugins: [\n blogPlugin({\n // other options ...\n category: [\n {\n key: 'tag',\n getter: ({ frontmatter }) => frontmatter.tag || [],\n path: '/tag/',\n layout: 'TagMap',\n frontmatter: () => ({ title: 'Tag page' }),\n itemPath: '/tag/:name/',\n itemLayout: 'TagList',\n itemFrontmatter: (name) => ({ title: `Tag ${name}` }),\n },\n ],\n }),\n // other plugins ...\n ],\n}\nAlso, you may want to star some of your articles, and display them to visitors. When you are setting star: true in frontmatter to mark them, you probably need a configuration like this to display them in /star/ path with StarList layout:
import { blogPlugin } from '@vuepress/plugin-blog'\n\nexport default {\n name: 'vuepress-theme-xxx',\n plugins: [\n blogPlugin({\n // other options ...\n type: [\n {\n key: 'star',\n filter: ({ frontmatter }) => frontmatter.star,\n path: '/star/',\n layout: 'StarList',\n frontmatter: () => ({ title: 'Star page' }),\n },\n ],\n }),\n // other plugins ...\n ],\n}\nSee, setting these 2 types is easy. For full options, please see Category Config and Type Config.
\nWhen generating each page, the plugin will set following information under frontmatter.blog:
interface BlogFrontmatterOptions {\n /** Current type of the page */\n type: 'category' | 'type'\n /** Unique key under current category or tag */\n key: string\n /**\n * Current category name\n *\n * @description Only available in category item page\n */\n name?: string\n}\nSo you can invoke useBlogCategory() and useBlogType() directly, and the result will be the category or type bind to current route.
Also, you can pass key you want as argument, then you will get information bind to that key.
So with node side settings above, you can get information about \"tag\" and \"star\" in client side:
\nTagMap layout:
<script setup lang=\"ts\">\nimport { useBlogCategory } from '@vuepress/plugin-blog'\nimport { RouteLink } from 'vuepress/client'\n\nconst categoryMap = useBlogCategory('tag')\n</script>\n\n<template>\n <div>\n <h1>Tag page</h1>\n <ul>\n <li v-for=\"({ items, path }, name) in categoryMap.map\">\n <RouteLink :key=\"name\" :to=\"path\" class=\"category\">\n {{ name }}\n <span class=\"category-num\">\n {{ items.length }}\n </span>\n </RouteLink>\n </li>\n </ul>\n </div>\n</template>\nTagList layout:
<script setup lang=\"ts\">\nimport { useBlogCategory } from '@vuepress/plugin-blog'\n\nconst categoryMap = useBlogCategory('tag')\n</script>\n\n<template>\n <div>\n <h1>Tag page</h1>\n <div class=\"category-wrapper\">\n <RouteLink\n v-for=\"({ items, path }, name) in categoryMap.map\"\n :key=\"name\"\n :to=\"path\"\n class=\"category\"\n >\n {{ name }}\n <span class=\"category-num\">\n {{ items.length }}\n </span>\n </RouteLink>\n </div>\n <div class=\"article-wrapper\" v-if=\"categoryMap.currentItems\">\n <div v-if=\"!categoryMap.currentItems.length\">Nothing in here.</div>\n <article\n v-for=\"{ info, path } in categoryMap.currentItems\"\n class=\"article\"\n @click=\"$router.push(path)\"\n >\n <header class=\"title\">\n {{\n (isTimeline\n ? `${new Date(info.date).toLocaleDateString()}: `\n : '') + info.title\n }}\n </header>\n <hr />\n <div class=\"article-info\">\n <span v-if=\"info.author\" class=\"author\"\n >Author: {{ info.author }}</span\n >\n <span v-if=\"info.date && !isTimeline\" class=\"date\"\n >Date: {{ new Date(info.date).toLocaleDateString() }}</span\n >\n <span v-if=\"info.category\" class=\"category\"\n >Category: {{ info.category.join(', ') }}</span\n >\n <span v-if=\"info.tag\" class=\"tag\"\n >Tag: {{ info.tag.join(', ') }}</span\n >\n </div>\n <div v-if=\"info.excerpt\" class=\"excerpt\" v-html=\"info.excerpt\" />\n </article>\n </div>\n </div>\n</template>\nStarList layout:
<script setup lang=\"ts\">\nimport { useBlogType } from '@vuepress/plugin-blog/client'\nimport { RouteLink } from 'vuepress/client'\n\nimport ArticleList from '../components/ArticleList.vue'\nimport ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'\n\nconst stars = useBlogType('star')\n</script>\n\n<template>\n <div class=\"article-wrapper\" v-if=\"stars.items\">\n <div v-if=\"!stars.items.length\">Nothing in here.</div>\n <article\n v-for=\"{ info, path } in stars.items\"\n class=\"article\"\n @click=\"$router.push(path)\"\n >\n <header class=\"title\">\n {{\n (isTimeline ? `${new Date(info.date).toLocaleDateString()}: ` : '') +\n info.title\n }}\n </header>\n <hr />\n <div class=\"article-info\">\n <span v-if=\"info.author\" class=\"author\">Author: {{ info.author }}</span>\n <span v-if=\"info.date && !isTimeline\" class=\"date\"\n >Date: {{ new Date(info.date).toLocaleDateString() }}</span\n >\n <span v-if=\"info.category\" class=\"category\"\n >Category: {{ info.category.join(', ') }}</span\n >\n <span v-if=\"info.tag\" class=\"tag\">Tag: {{ info.tag.join(', ') }}</span>\n </div>\n <div v-if=\"info.excerpt\" class=\"excerpt\" v-html=\"info.excerpt\" />\n </article>\n </div>\n</template>\nFor return types, please see Composition API Return Types.
\nThis plugin adds native i18n support, so your settings will be automatically applied to each language.
\nFor example, if user has the following locales' config, and you are setting the \"star\" example above:
\nexport default {\n locales: {\n '/': {\n lang: 'en-US',\n },\n '/zh/': {\n lang: 'zh-CN',\n },\n },\n}\nThen /zh/star/ and /star/ will both be available, and only articles under the correct locale will appear.
This plugin provides a built-in excerpt generator, which can be enabled by setting excerpt option to true.
Excerpt introduction
\nAn excerpt is an HTML fragment that is used to display a short description of an article in the blog list, so the excerpt has the following restrictions:
\nisCustomElement option..vuepress/public or full URL to ensure they can be accessed in other places.The excerpt generator will try to find a valid excerpt separator from markdown contents, if it finds one, it will use content before the separator. The separator is default <!-- more -->, and you can customize it by setting excerptSeparator option.
If it cannot find a valid separator, it will parse content from the beginning of markdown file, and stop till its length reaches a preset value. The value is default 300, and you can customize it by setting excerptLength option.
To choose which page should generate excerpt, you can use excerptFilter option.
Example
\nNormally you may want to use frontmatter.description if users set them, so you can let filter function return false if frontmatter.description is not empty.
You can both set options with plugin options on Node side and set options in client config file on Browser side.
\nimport { commentPlugin } from 'vuepress-plugin-comment2'\n\n// .vuepress/config.ts\nexport default {\n plugins: [\n commentPlugin({\n provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo\n\n // other options here\n // ...\n }),\n ],\n}\nimport { defineClientConfig } from 'vuepress/client'\nimport {\n defineArtalkConfig,\n // defineGiscusConfig,\n // defineTwikooConfig,\n // defineWalineConfig,\n} from 'vuepress-plugin-comment2/client'\n\ndefineArtalkConfig({\n // 选项\n})\n\nexport default defineClientConfig({\n // ...\n})\nBut here are some limitations you should remember:
\nprovider, locales and other resource related option must be set in plugin options.
To ensure tree-shaking works, we must optimize entries at node so that bundler can understand which resource should be included in the final bundle.
\nThese options will be marked with
\nOptions which can not be serialized to JSON must be set in client config.
\nOptions that receives function values can not be set in plugin options, as plugins are running under Node.js environment, so we can not pass these values and their contexts to browser.
\nThese options will be marked with
\nThis plugin globally registers a component <CommentService />.
alias and layout slots to insert the component. We recommended you to insert the comment component (<CommentService />) after the <PageNav /> component, and the current page is a demo with default theme.By default, <CommentService /> component is enabled globally, and you can use comment option in both plugin options and page frontmatter to control it.
comment: false in page frontmatter.comment to false in the plugin options. Then you can set comment: true in page frontmatter to enable it locally.You can set commentID option in page frontmatter to customize comment ID, which is used to identify comment storage item to use for a page. By default it will be the path of the page, which means if you are deploying the site to multiple places, page with same content across sites will share the same comment data.
Currently, you can choose from Giscus, Waline, Artalk and Twikoo.
\nRecommended comment services
\n\"Artalk\" | \"Giscus\" | \"Twikoo\" | \"Waline\" | \"None\"\"None\"booleantrueThe channel plugin option is used to config the feed channel.
\nstringSiteConfig.titleChannel title
\nstringoptions.hostname and context.base)Channel address
\nstringSiteConfig.descriptionChannel description
\nType: string
Default:
\nsiteConfig.locales['/'].lang\"en-US\"The language of the channel
\nType: string
Default:
\nauthor.name in channel options, and fall back to Copyright by $authorRecommended to set manually: Yes
\nChannel copyright information
\nstring (must be a valid Date ISOString)Publish date of the Channel
\nstring (must be a valid Date ISOString)Last update time of channel content
\nnumberThe effective time of the content. It's the time to keep the cache after request without making new requests.
\nstringA picture presenting the channel. A square picture with a size not smaller than 512×512 is recommended.
\nstringAn icon representing a channel, a square picture, with not less than 128×128 in size, and transparent background color is recommended.
\nFeedAuthorThe author of the channel.
\ninterface FeedAuthor {\n /** Author name */\n name: string\n /** Author's email */\n email?: string\n /** Author's site */\n url?: string\n /**\n * Author's avatar address\n *\n * Square, preferably not less than 128×128 with transparent background\n */\n avatar?: string\n}\nstringLink to Websub. Websub requires a server backend, which is inconsistent with VuePress, so ignore it if there is no special need.
\nWebSub
\nFor details, see Websub.
\nstringThe domain name of the deployment site.
\nbooleanfalseWhether to output Atom syntax files.
\nbooleanfalseWhether output JSON syntax files.
\nbooleanfalseWhether to output RSS syntax files.
\nstringA large image/icon of the feed, probably used as banner.
\nstringA small icon of the feed, probably used as favicon.
\nnumber100Set the maximum number of items in the feed. After all pages are sorted, the first count items will be intercepted.
If your site has a lot of articles, you may consider this option to reduce feed file size.
\n(RegExp | string)[] | (tagName: string) => booleanCustom element or component which should be preserved in feed.
\nBy default, all unknown tags will be removed.
\nType: (page: Page)=> boolean
Default:
\n;({ frontmatter, filePathRelative }: Page): boolean =>\n !(\n frontmatter.home ||\n !filePathRelative ||\n frontmatter.article === false ||\n frontmatter.feed === false\n )\nA custom filter function, used to filter feed items.
\nType: (pageA: Page, pageB: Page)=> number
Default:
\n// dateSorter is from @vuepress/helper\n;(pageA: Page, pageB: Page): number =>\n dateSorter(\n pageA.data.git?.createdTime\n ? new Date(pageA.data.git?.createdTime)\n : pageA.frontmatter.date,\n pageB.data.git?.createdTime\n ? new Date(pageB.data.git?.createdTime)\n : pageB.frontmatter.date,\n )\nCustom sorter function for feed items.
\nThe default sorting behavior is by file adding time coming from git (needs @vuepress/plugin-git).
TIP
\nYou should enable @vuepress/plugin-git to get the newest created pages as feed items. Otherwise, the feed items will be sorted by the default order of pages in VuePress.
channel option is used to config Feed Channels.
For available options, please see Config → Channel
\nbooleanfalseWhether enabled in devServer.
\nTIP
\nFor performance reasons, we do not provide hot reload. Reboot your devServer to sync your changes.
\nstring\"http://localhost:${port}\"Hostname to use in devServer
\nstring\"atom.xml\"Atom syntax output filename, relative to dest folder.
\nstring@vuepress/plugin-feed/templates/atom.xslAtom xsl template file content.
\nstring\"atom.xsl\"Atom xsl filename, relative to dest folder.
\nstring\"feed.json\"JSON syntax output filename, relative to dest folder.
\nstring\"rss.xml\"RSS syntax output filename, relative to dest folder.
\nstring@vuepress/plugin-feed/templates/rss.xslRSS xsl template file content.
\nstring\"rss.xsl\"RSS syntax xsl filename, relative to dest folder.
\nFeed generation controller, see Feed Getter.
\nThe plugin has a built-in getter, only set this if you want full control of feed generation.
\nRecord<string, BaseFeedOptions>You can use it to specific options for each locale.
\nAny options above are supported except hostname.
You can control each feed item generation by setting page frontmatter.
\nBy default, all articles are added to the feed stream. Set feed: false in frontmatter to remove a page from feed.
stringAutomatically generated by VuePress, defaults to the h1 content of the page
\nstringDescription of the page
\nDateDate when the page was published
\nbooleanWhether the page is an article
\n\n\nIf this is set to
\nfalse, the page will not be included in the final feed.
stringPage copyright information
\nstringImage used as page cover , should be full link or absolute link.
\nstringThe title of the feed item
\nstringDescription of the feed item
\nstringThe content of the feed item
\nFeedAuthor[] | FeedAuthorThe author of the feed item
\ninterface FeedAuthor {\n /**\n * Author name\n */\n name?: string\n\n /**\n * Author email\n */\n email?: string\n\n /**\n * Author site\n *\n * @description json format only\n */\n url?: string\n\n /**\n * Author avatar\n *\n * @description json format only\n */\n avatar?: string\n}\nFeedContributor[] | FeedContributorContributors to feed item
\ninterface FeedContributor {\n /**\n * Author name\n */\n name?: string\n\n /**\n * Author email\n */\n email?: string\n\n /**\n * Author site\n *\n * @description json format only\n */\n url?: string\n\n /**\n * Author avatar\n *\n * @description json format only\n */\n avatar?: string\n}\nstringThe identifier of feed item, used to identify the feed item.
\nYou should ensure every feed has a unique guid.
\nYou can take full control of feed items generation by setting getter in the plugin options.
(page: Page) => stringItem title getter
\n(page: Page) => stringItem link getter
\n(page: Page) => string | undefinedItem description getter
\nTIP
\nDue to Atom support HTML in summary, so you can return HTML content here if possible, but the content must start with mark html:.
(page: Page) => stringItem content getter
\n(page: Page) => FeedAuthor[]Item author getter.
\nThe getter should return an empty array when author information is missing.
\ninterface FeedAuthor {\n /**\n * Author name\n */\n name?: string\n\n /**\n * Author email\n */\n email?: string\n\n /**\n * Author site\n *\n * @description json format only\n */\n url?: string\n\n /**\n * Author avatar\n *\n * @description json format only\n */\n avatar?: string\n}\n(page: Page) => FeedCategory[] | undefinedItem category getter.
\ninterface FeedCategory {\n /**\n * Category Name\n */\n name: string\n\n /**\n * A string that identifies a categorization taxonomy\n *\n * @description rss format only\n */\n domain?: string\n\n /**\n * the categorization scheme via a URI\n *\n * @description atom format only\n */\n scheme?: string\n}\n(page: Page) => FeedEnclosure | undefinedItem enclosure getter.
\ninterface FeedEnclosure {\n /**\n * Enclosure link\n */\n url: string\n\n /**\n * what its type is\n *\n * @description should be a standard MIME Type, rss format only\n */\n Type: string\n\n /**\n * Size in bytes\n *\n * @description rss format only\n */\n length?: number\n}\n(page: Page) => Date | undefinedItem release date getter
\n(page: Page) => DateItem last update date getter
\n(page: Page) => stringItem Image Getter
\nEnsure it's returning a full URL
\n(page: Page) => FeedContributor[]Item Contributor Getter
\nThe getter should return an empty array when contributor information is missing.
\ninterface FeedContributor {\n /**\n * Author name\n */\n name?: string\n\n /**\n * Author email\n */\n email?: string\n\n /**\n * Author site\n *\n * @description json format only\n */\n url?: string\n\n /**\n * Author avatar\n *\n * @description json format only\n */\n avatar?: string\n}\n(page: Page) => string | undefinedItem copyright getter
\n", + "date_modified": "2024-02-01T04:46:03.000Z", + "authors": [], + "tags": [] + }, + { + "title": "Guide", + "url": "https://ecosystem.vuejs.press/ecosystem/plugins/feed/guide.html", + "id": "https://ecosystem.vuejs.press/ecosystem/plugins/feed/guide.html", + "summary": "Guide Usage The plugin can generate feed files in the following three formats for you: Atom 1.0 JSON 1.1 RSS 2.0 Please set atom, json or rss to true in the plugin options accor...", + "content_html": "\nThe plugin can generate feed files in the following three formats for you:
\nPlease set atom, json or rss to true in the plugin options according to the formats you want to generate.
To correctly generate feed links, you need to set hostname in the plugin options,
When you open the feed file in browser, we magically convert atom and rss feed xml to human readable html via xsl template. Check atom and rss feed of this site as an example!
\nIf you want to preview your feed in devServer, set devServer: true in plugin options. You may also need to set devHostname if you are not using the default http://localhost:{port}.
You can customize the feed channel information by setting the channel option.
We recommend the following settings:
\nchannel.pubDatechannel.ttl (unit: minutes)channel.copyrightchannel.author.For detailed options and their default values, see Channel Config
\nBy default, all articles are added to the feed stream.
\nYou can set feed and other options in page frontmatter to control contents of feed item. See Frontmatter Config for how they are converted.
You can take full control of feed items generation by configuring the getter in the plugin options. For detailed options and their default values, see Configuration → Feed Getter.
The plugin generates separate feeds for each language.
\nYou can provide different settings for different languages via locales in the plugin options.
booleanfalseType: AppManifest
Details:
\nYou can fill with an object which will be parsed to manifest.webmanifest.
\nTIP
\nSome options have their fallback if you don't set them.
\nsiteConfig.title || siteConfig.locales['/'].title || \"Site\"siteConfig.title || siteConfig.locales['/'].title || \"Site\"siteConfig.description || siteConfig.locales['/'].description || \"A site built with vuepress\"siteConfig.locales['/'].lang || \"en-US\"context.basecontext.base\"standalone\"\"#46bd87\"\"#ffffff\"\"portrait-primary\"falseReference:
\n\nType: string
Details:
\nLink of favicon.ico.
\nWARNING
\nWe recommend you to set favicon for your site.
\nType: string
Default: \"#46bd87\"
Details:
\nTheme Color of the pwa.
\nType: boolean
Default: false
Details:
\nWhether cache HTML files besides home page and 404 page.
\nType: boolean
Default: false
Details:
\nWhether cache pictures
\nType: number
Default: 2048
Details:
\nMax size allowed to be cached, with KB unit
\nWARNING
\nThis option has the highest priority, and any files exceeding this value will be excluded.
\nSo if you generate very large HTML or JS files, please consider increasing this value, otherwise your PWA may not work normally in offline mode.
\nType: number
Default: 1024
Details:\nMax picture size allowed to be cached, with KB unit
\nThe value must not be greater than maxSize option
\nType: \"disabled\" | \"available\" | \"hint\" | \"force\"
Default: \"available\"
Details:\nControl logic when new content is found.
\n\"disabled\": Do nothing even when new service worker is available. After new service work succeeds installing and starts waiting, it will control page and provide new content in next visit.
\"available\": Only display update popup when the new service worker is available
\"hint\": Display a hint to let user choose to refresh immediately
This is helpful when you want users to see new docs immediately.
\nTIP
\nIf users choose to refresh, the current service worker will be unregister, and request will start coming to web. Later the new service worker will start installing and control current page after installed.
\n\"force\": unregister current service worker immediately then refresh to get new content
DANGER
\nAlthough this ensures users are viewing the latest content, it may affect viewing experiences.
\nTIP
\nHow docs are updated is controlled by a previous version, so the current option only effect next update from this version.
\nSpecial settings for better supporting Safari, ignoring these options are safe.
\nstring\"black\" | \"white\"\"black\"stringSpecial settings for Microsoft tiles, ignoring these options are safe.
\nstringstringthemeColorstring\"PwaFoundPopup\"string\"PwaReadyPopup\"booleanfalseDetails:
\nOptions passed to workbox-build, for details, see Workbox documentation
Type: PwaPluginLocaleConfig
interface PwaPluginLocaleData {\n /**\n * Install button text\n */\n install: string\n\n /**\n * iOS install hint text\n */\n iOSInstall: string\n\n /**\n * Cancel button text\n */\n cancel: string\n\n /**\n * Close button text\n */\n close: string\n\n /**\n * Previous image text\n */\n prevImage: string\n\n /**\n * Next image text\n */\n nextImage: string\n\n /**\n * Install explain text\n */\n explain: string\n\n /**\n * Description label text\n */\n desc: string\n\n /**\n * Feature label text\n */\n feature: string\n\n /**\n * Update hint text\n */\n hint: string\n\n /**\n * Update available text\n */\n update: string\n}\n\ninterface PwaPluginLocaleConfig {\n [localePath: string]: PwaPluginLocaleData\n}\nDetails:\nLocales config for pwa plugin.
\nDetails:
\nReturns the event emitter of this plugin.
\nYou can add listener function to events that provided by register-service-worker.
\nExample:
\nimport { usePwaEvent } from '@vuepress/plugin-pwa/client'\n\nexport default {\n setup() {\n const event = usePwaEvent()\n event.on('ready', (registration) => {\n console.log('Service worker is active.')\n })\n },\n}\nDetails:
\nForce update the page when an update is found.
\nExample:
\nimport { forceUpdate } from '@vuepress/plugin-pwa/client'\nimport { onMounted } from 'vue'\n\nexport default {\n setup() {\n onMounted(() => {\n forceUpdate()\n })\n },\n}\nDetails:
\nRegister service worker manually.
\nParameters:
\n| Parameter | Type | Description |\n|
\n", + "date_modified": "2024-02-20T02:57:55.000Z", + "authors": [], + "tags": [] + }, + { + "title": "Guide", + "url": "https://ecosystem.vuejs.press/ecosystem/plugins/pwa/guide.html", + "id": "https://ecosystem.vuejs.press/ecosystem/plugins/pwa/guide.html", + "summary": "Guide Intro Make your VuePress site a Progressive Web Application (PWA)[1]. This plugin uses workbox-build to generate service worker file, and uses register-service-worker to r...", + "content_html": "\nMake your VuePress site a Progressive Web Application (PWA)[1].
\nThis plugin uses workbox-build to generate service worker file, and uses register-service-worker to register service worker.
\nWARNING
\nIf you enabled this plugin once and you want to disable it, you might need `@vuepress/plugin-remove-pwa to remove the existing service worker.
\nA PWA uses a Service Worker [2] (SW for short) to cache and proxy site content.
\nTo make your website fully compliant with PWA, a Web app manifests [3] file is needed, and your pwa should satisfy the installability [4] specification.
\nYou can set manifest option to customize the manifest file, or provide a manifest.webmanifest or manifest.json in public folder. The former has higher priority.
The plugin will automatically generate manifest.webmanifest for you and add manifest link declaration in each page, while you should still at least set a valid icon through manifest.icons or other icon related options in the PWA plugin.
WARNING
\nThe installability [4:1] specification requires at least one valid icon to be declared in the manifest.
\nSo if you do not configure manifest.icons, visitors can only enjoy the offline accessibility brought by the Service Worker cache, while cannot install your site as a PWA.
Besides the plugin does not process anything in the manifest by default, but outputs them as-is. This means that if you plan to deploy to a subdirectory, you should append the URL prefix to manifest Urls yourself. If everything you need is all under base directory, you can set appendBase: true in plugin options to let the plugin append base to any links in manifest.
To better control what the Service Worker can pre-cache, the plugin provides related options for cache control.
\nBy default, the plugin will pre-cache all js css files, and only homepage and 404 html are cached. The plugin will also cache font files (woff, woff2, eot, ttf, otf) and SVG icons.
If your site has only a few important images, and want them displayed in offline mode, you can cache site images by setting cacheImage: true .
We recognize images by file extension. Any files ending with .png, .jpg, .jpeg, .gif, .bmp, .webp will be regarded as images.
If you have small sites, and would like to make document fully offline available, you can set cacheHTML to true to cache all HTML files.
Why only home and 404 page been cached by default?
\nThough VuePress generates HTML files through SSG[5] for all pages, these files are mainly used for SEO[6] and allow you to directly configure the backend without SPA[7] Visit any link.
\nVuePress is essentially an SPA. This means that you only need to cache the home page and enter from the home page to access all pages normally. Therefore, not caching other HTML by default can effectively reduce the cache size (40% smaller in size) and speed up the SW update speed.
\nBut this also has the disadvantage. If the user enters the site directly from a non-home page, the HTML file for the first page still needs to be loaded from the internet. Also, in offline environment, users can only enter through the homepage and then navigate to the corresponding page by themselves. If they directly access a link, an inaccessible prompt will appear.
\nTo prevent large files from being included in the pre-cache list, any files > 2 MB or images > 1 MB will be omitted. You can customize these limits with maxSize and maxImageSize options (in KB unit).
We provide the update option to control how users receive updates.
The default value of the update option is \"available\", which means that when new content available, the new SW will be installed and its resources will be fetched silently in the background. A pop-up window appears once the new SW is ready, and users can choose whether to refresh immediately to view new content. This means users are reading old content before a new SW is ready.
If your project is still in building stage, and you want to alert the user that he may be reading outdated content, you can set this to \"hint\". This allows users to be notified that new content has been published within seconds after visiting docs. But the negative effect of this is that if the user chooses to update before the new SW is ready, he will need to get all the resources of the page from the internet before the new SW installs and controls the page.
If your docs are stable, or you're hosting a blog and don't care much about users receiving the latest version right away, you can set this to \"disabled\", which means that the new SW will be installed completely silently in the background and start waiting, when all pages controlled by old SW are all closed, the new SW will start to take control and provide users with new content during next visit. This setting can prevent users from being disturbed during the visit.
To speed up user access under weak or no network conditions through SW, but also want users to always access new content, you can set this option to \"force\". This means any old SW will be removed as soon as a new SW is detected, and all pages are refreshed to ensure the user is browsing the latest content. The biggest disadvantage is that all users will experience unexpected sudden refresh within seconds after reentering an updated site.
When new content is detected (new SW detected), a update found popup appears; and when the new content is ready, an update ready popup appears.
\nIf you are not satisfied with the default popup content, you can use your own component. Import PwaFoundPopup or PwaReadyPopup from @vuepress/plugin-pwa/client and use its slot to customize the popup content, then pass the component path to foundComponent or readyComponent option:
<script setup lang=\"ts\">\nimport { PwaFoundPopup } from '@vuepress/plugin-pwa/client'\n</script>\n<template>\n <PwaFoundPopup v-slot=\"{ found, refresh }\">\n <div v-if=\"found\">\n New content is found.\n <button @click=\"refresh\">Refresh</button>\n </div>\n </PwaFoundPopup>\n</template>\n<script setup lang=\"ts\">\nimport { PwaReadyPopup } from '@vuepress/plugin-pwa/client'\n</script>\n<template>\n <PwaReadyPopup v-slot=\"{ isReady, reload }\">\n <div v-if=\"isReady\">\n New content is ready.\n <button @click=\"reload\">Apply</button>\n </div>\n </PwaReadyPopup>\n</template>\nThe plugin also provides other PWA-related options, such as Microsoft tile icon and color settings, Apple icon and so on. If you are an advanced user, you can also set generateSwConfig to configure workbox-build. Check Plugin options for more details.
For more details, please see:
\n\nPWA introduction
\nPWA, full name Progressive Web app. PWA standard is stipulated by W3C.
\nIt allows sites to install the site as an App on supported platform through a browser that supports this feature.
\nSee https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps for details. ↩︎
\nService Worker Introduction
\nThe Service Worker will get and cache all the files registered in it during the registration process.
\nAfter the registration complete, the Service Worker is activated, and starts to proxy and control all your requests.
\nWhenever you want to initiate an access request through the browser, the Service Worker will check whether it exists in its own cache list, if it exists, it will directly return the cached result, otherwise it will call its own fetch method to get it. You can use a custom fetch method to fully control the result of the request for resources in the web page, such as providing a fallback web page when offline.
\nEvery time the user reopens the site, the Service Worker will request to the link when it was registered. If a new version of Service Worker is detected, it will update itself and start caching the list of resources registered in the new Service Worker . After the content update is successfully obtained, the Service Worker will trigger the update event. The user can be notified through this event, for example, a pop-up window will be displayed in the lower right corner, prompting the user that new content is available and allowing the user to trigger an update.
Manifest File
\nThe manifest file uses the JSON format and is responsible for declaring various information of the PWA, such as name, description, icon, and shortcut actions.
\nIn order for your site to be registered as a PWA, you need to meet the basic specifications of the manifest to make the browser consider the site as an installable PWA and allow users to install it.
\nTIP
\nFor Manifest standards and specifications, please see MDN Web app manifests and W3C Manifest.
\nInstallable
\nTo let the site be registered as a PWA, the site needs to successfully register a valid service worker by itself, and declare a valid manifest file with its link in meta tag.
\nThe manifest file should contain at least name (or short_name) icons start_url.
On safari, the maximum cache size of the service worker is 50 MB. ↩︎ ↩︎
\nSSG: Static Site Generation, ↩︎
\nSEO: Search Engine Optimization. ↩︎
\nSPA: Single Page Application, most of them only have the homepage, and use history mode to handle routing instead of actually navigating between pages. ↩︎
\nType: string
Required: Yes
\nDetails:
\nDeploy hostname.
\nType: Author
type AuthorName = string\n\ninterface AuthorInfo {\n /**\n * Author name\n */\n name: string\n\n /**\n * Author website\n */\n url?: string\n\n /**\n * Author email\n */\n email?: string\n}\n\ntype Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]\nRequired: No
\nDetails:
\nDefault author.
\nType: boolean
Default: true
Details:
\nWhether generate description automatically
\nType: string | ((page: Page) => string | null)
Details:
\nCanonical link
\nType: string
Details:
\nFallback Image link when no image are found
\nType: string
Details:
\nThe age rating of the content, the format is [int]+, such as \"13+\".
Type: string
Details:
\nFill in your twitter username.
\nType: (page: Page) => boolean
Details:
\nUse this option to judge whether the page is an article.
\nType:
\nfunction ogp(\n /** OGP info inferred by plugin */\n ogp: SeoContent,\n /** Page Object */\n page: Page,\n /** VuePress App */\n app: App,\n): SeoContent\nRequired: No
\nDetails:
\nCustom OPG Generator.
\nYou can use this options to edit OGP tags.
\nType:
\nfunction jsonLd(\n /** JSON-LD Object inferred by plugin */\n jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,\n /** Page Object */\n page: Page,\n /** VuePress App */\n app: App,\n): ArticleSchema | BlogPostingSchema | WebPageSchema\nRequired: No
\nDetails:
\nCustom JSON-LD Generator.
\nYou can use this options to edit JSON-LD properties.
\nType:
\nfunction customHead(\n /** Head tag config */\n head: HeadConfig[],\n /** Page Object */\n page: Page,\n /** VuePress App */\n app: App,\n): void\nRequired: No
\nDetails:
\nYou can use this options to edit tags injected to <head>.
This plugin will make your site fully support Open Content Protocol OGP and JSON-LD 1.1 to enhance the SEO of the site.
\n\nThe plugin works out of the box. Without any config, it will extract information from the page content as much as possible to complete the necessary tags required by OGP and JSON-LD.
\nBy default, the plugin will read the site config and page frontmatter to automatically generate tags as much as possible. Such as site name, page title, page type, writing date, last update date, and article tags are all automatically generated.
\nThe following are the <meta> tags and their values that will be injected into <head> by default:
The following are the <meta> tags and their value injected into <head> by default to satisfy OGP:
| Meta Name | Value |\n| :
\n", + "date_modified": "2024-03-10T14:51:27.000Z", + "authors": [], + "tags": [] + }, + { + "title": "sitemap", + "url": "https://ecosystem.vuejs.press/ecosystem/plugins/sitemap/", + "id": "https://ecosystem.vuejs.press/ecosystem/plugins/sitemap/", + "summary": "sitemap", + "content_html": "\n", + "date_modified": "2024-02-01T04:46:03.000Z", + "authors": [], + "tags": [] + }, + { + "title": "Config", + "url": "https://ecosystem.vuejs.press/ecosystem/plugins/sitemap/config.html", + "id": "https://ecosystem.vuejs.press/ecosystem/plugins/sitemap/config.html", + "summary": "Config hostname Type: string Required: Yes Details: The domain name where the current site is deployed, the plugin needs this option to work. extraUrls Type: string[] Details: E...", + "content_html": "\nType: string
Required: Yes
\nDetails:
\nThe domain name where the current site is deployed, the plugin needs this option to work.
\nType: string[]
Details:
\nExtra link to be included.
\nIf you have some links not including in VuePress Router (normally in public directory or generated by other tools directly), you may need this option.
\nExample: ['/about.html', '/api/']
Type: string[]
Default: ['/404.html']
Details:
\nUrls excluding from sitemap, starting with absolute path.
\nBy default, all the urls generated by VuePress (excluding 404 page) will be added into sitemap.
\nType: boolean
Default: false
Details:
\nWhether enabled in devServer.
\nTIP
\nFor performance reasons, we do not provide hot reload. Reboot your devServer to sync your changes.
\nType: string
Default: \"http://localhost:${port}\"
Details:
\nHostname to use in devServer
\nType: string
Default value: \"sitemap.xml\"
Details:
\nThe output filename, relative to output directory.
\nType: string
Default value: \"sitemap.xsl\"
Details:
\nOutput xsl filename, relative to dest folder.
\nType: string
Default value: \"@vuepress/plugin-sitemap/templates/sitemap.xsl\"
Details:
\nXSL content used as template.
\nType: \"always\" | \"hourly\" | \"daily\" | \"weekly\" |\"monthly\" | \"yearly\" | \"never\"
Default value: \"daily\"
Details:
\nPage default update frequency, will be overridden by sitemap.changefreq in Frontmatter.
\nType: number
Default: 0.5
Details:
\nPage priority, from 0 to 1.
Type: (page: Page, app: App) => string
Details:
\nLast modify time getter. By default, the plugin will use the timestamp generated by git plugin.
\nType: SitemapFrontmatterOptions | false
Details:
\nfalse means exclude the page from sitemap.
Type: \"always\" | \"hourly\" | \"daily\" | \"weekly\" | \"monthly\" | \"yearly\" | \"never\"
Default: \"daily\"
Details:
\nPage default update frequency. This will override changefreq in Plugin Options.
\nType: number
Default: 0.5
Details:
\nPage priority, range from 0 to 1.
This plugin will automatically generate a Sitemap for your site. To let this plugin work, you need to pass the deployed domain name to the hostname option of the plugin. If you want to preview in devServer, set devServer options.
The plugin will automatically generate the last update time of the page based on the Git timestamp of the page, and will also declare the alternative links of the page in other languages according to the locales' config.
\nBy default, all site links except 404 page will be added to the Sitemap.
\nTo add other pages to the Sitemap outside the VuePress project page, please turn them into an array and pass to the extraUrls plugin option.
If you don't want certain pages to appear in the sitemap, you can turn their paths into an array and pass to the excludePaths plugin option, or set sitemap to false in the frontmatter of the corresponding page.
You can also control the output link through the sitemapFilename option of the plugin, the link is relative to output directory. By default, the plugin will use sitemap.xml.
The default update cycle of the page is daily (every day). To modify the entire page cycle, please set changefreq in the plugin options. You can also set sitemap.changefreq in the frontmatter of the page. Note that page has a higher priority.
The legal frequencies are:
\n\"always\"\"hourly\"\"daily\"\"weekly\"\"monthly\"\"yearly\"\"never\"You can set priority in the plugin to provide a default value. At the same time you can set the priority for each page through sitemap.priority in frontmatter. Acceptable values are floating point numbers from 0 to 1.
You can use option modifyTimeGetter to return a time in ISO string format, which is generated by the Git plugin by default.
The following is an example based on the last modification time of a file.
\n// Based on file last modified time\n({\n modifyTimeGetter: (page, app) =>\n fs.statSync(app.dir.source(page.filePathRelative)).mtime.toISOString();\n})\nSitemaps provide SEO (Search Engine Optimization):
\nA sitemap enhances SEO by making all pages findable.
\nMost search engines only follow a limited number of links within a page, so when the site is very large, a sitemap becomes essential to make everything on the site accessible to search engines and visitors.
\nSitemaps is a protocol for site administrators to publish pages that can be crawled on a site to search engine spiders. The content of sitemap files must follow the definition in XML format. Each URL can contain the update period and last update time, the priority of the URL across the site. This allows search engines to crawl site content better and more efficiently.
\nTogether with robots.txt
\nSitemap is basically used by search engines, when using this plugin, you'd better ensure that you have a valid robots.txt in the .vuepress/public directory to allow search engines spiders to visit your site. The simplest robots.txt is as follows (allow all search engines to access all paths)
User-agent: *\n\nAllow: /\nCheck whether a component is registered globally.
\nTIP
\nsetup scope, you need to pass the app instance as the second parameter.export const hasGlobalComponent: (name: string, app?: App) => boolean\n// if you globally register `<my-component>`\nhasGlobalComponent('MyComponent') // true\nhasGlobalComponent('my-component') // true\n\nhasGlobalComponent('MyComponent2') // false\nGet current locale config from locales settings.
\nexport const useLocaleConfig: <T extends LocaleData>(\n localesConfig: RequiredLocaleConfig<T>,\n) => ComputedRef<T>\nconst localesCOnfig = {\n '/': 'Title',\n '/zh/': '标题',\n}\n\nconst locale = useLocaleConfig(localesConfig)\n\n// under `/page`\nlocale.value // 'Title'\n\n// under `/zh/page`\nlocale.value // '标题'\nThe following functions are available on both Node.js and Client.
\nEncode/decode and zip/unzip data.
\nThis is useful in markdown plugins when you want to encode string content and pass it to the component through props.
\nYou may simply achieve this with encodeURIComponent and decodeURIComponent, but it can be very large if the content contains lots of special characters.
So we provide encodeData and decodeData to zip and encode content.
export const encodeData: (\n data: string,\n level: DeflateOptions['level'] = 6,\n) => string\n\nexport const decodeData: (compressed: string) => string\nconst content = `\n{\n \"type\": \"bar\",\n \"data\": {\n \"labels\": [\"Red\", \"Blue\", \"Yellow\", \"Green\", \"Purple\", \"Orange\"],\n \"datasets\": [\n {\n \"label\": \"# of Votes\",\n \"data\": [12, 19, 3, 5, 2, 3],\n \"backgroundColor\": [\n \"rgba(255, 99, 132, 0.2)\",\n \"rgba(54, 162, 235, 0.2)\",\n \"rgba(255, 206, 86, 0.2)\",\n \"rgba(75, 192, 192, 0.2)\",\n \"rgba(153, 102, 255, 0.2)\",\n \"rgba(255, 159, 64, 0.2)\"\n ],\n \"borderColor\": [\n \"rgba(255, 99, 132, 1)\",\n \"rgba(54, 162, 235, 1)\",\n \"rgba(255, 206, 86, 1)\",\n \"rgba(75, 192, 192, 1)\",\n \"rgba(153, 102, 255, 1)\",\n \"rgba(255, 159, 64, 1)\"\n ],\n \"borderWidth\": 1\n }\n ]\n },\n \"options\": {\n \"scales\": {\n \"y\": {\n \"beginAtZero\": true\n }\n }\n }\n}\n`\n\nconst prop = encodeData(content) // \"eJyNUsFOwzAMve8rrHABKZqWlg5WxAE4cARxAMHEIV1NmQhNlaaCCe3fcdKtW0sLWGpjxy/v+UV512mlcIyfhTa2hHP4GgHYVYExsEQaxqlMpZWxbwAomaAqY5izO0wZB3apKnTrIyqlP1x2bRBzl9xWplC+eWNkniF7dmw1X4nWsfgaNtwNP2kfgH6Be22x9CPUUQ8yFwEHMeMQcog4UBFuiF0kcvGWGV3l6ZVW2uw0XDCTJfIwiOjYjAhESIcn4+BoT2MLio6pP6V+EBJ6AOSZgsmUwyl9A6ATwoiZn3lYTkTkRkycnuP8TU9ENPqUxuuA9i9BmxTNPy9A/G2/F9I23wtpW++FdIwPKzW2W5Afph+WqX2NQWz313XicT7XhV3qnB5f/ejKhVTYVACrXUqUmC3zC/uERsdgTYUdVr/Qb302+gZxe7S/\"\n\ndecodeData(prop) // will be the original content\n\n// if you use `encodeURIComponent`, it will be much longer\nencodeURIComponent(content) // '%0A%7B%0A%20%20%22type%22%3A%20%22bar%22%2C%0A%20%20%22data%22%3A%20%7B%0A%20%20%20%20%22labels%22%3A%20%5B%22Red%22%2C%20%22Blue%22%2C%20%22Yellow%22%2C%20%22Green%22%2C%20%22Purple%22%2C%20%22Orange%22%5D%2C%0A%20%20%20%20%22datasets%22%3A%20%5B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%22label%22%3A%20%22%23%20of%20Votes%22%2C%0A%20%20%20%20%20%20%20%20%22data%22%3A%20%5B12%2C%2019%2C%203%2C%205%2C%202%2C%203%5D%2C%0A%20%20%20%20%20%20%20%20%22backgroundColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%200.2)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%201)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderWidth%22%3A%201%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%0A%20%20%7D%2C%0A%20%20%22options%22%3A%20%7B%0A%20%20%20%20%22scales%22%3A%20%7B%0A%20%20%20%20%20%20%22y%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22beginAtZero%22%3A%20true%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A'\nisDef(x): Check if x is defined.isBoolean(x): Check if x is a boolean.isString(x): Check if x is a string.isNumber(x): Check if x is a number.isPlainObject(x): Check if x is a plain object.isArray(x): Check if x is an array.isFunction(x): Check if x is a function.isRegExp(x): Check if x is a regular expression.startsWith(a, b): Check if string a starts with string b.endsWith(a, b): Check if string a ends with string b.Return false if a is not a string.
keys(x): Return an array of keys of object x.
values(x): Return an array of values of object x.
entries(x): Convert object x to an array of key-value pairs.
fromEntries(x): Convert an array of key-value pairs x to an object.
deepAssign(x, y, ...): A deep version of Object.assign.
// or @vuepress/helper/client\nimport { deepAssign } from '@vuepress/helper'\n\nconst defaultOptions = {\n optionA: {\n optionA1: 'defaultOptionA1',\n optionA2: 'defaultOptionA2',\n optionA3: 'defaultOptionA3',\n },\n optionB: true,\n optionC: 'optionC',\n}\n\nconst userOptions = {\n optionA: {\n optionA1: 'optionA1',\n optionA2: 'optionA2',\n },\n optionB: false,\n}\n\ndeepAssign(defaultOptions, userOptions)\n// {\n// optionA: {\n// optionA1: \"optionA1\",\n// optionA2: \"optionA2\",\n// optionA3: \"defaultOptionA3\",\n// },\n// optionB: false,\n// optionC: \"optionC\",\n// }\ngetDate(x): Convert input x to a date. It can support Date, timestamp, and date string. The support degree of date string depends on the Date.parse support degree of the environment. Return null when it cannot be converted to a date.
getDate('2021-01-01') // a Date object represents 2021-01-01\ngetDate(1609459200000) // a Date object represents 2021-01-01\ngetDate('2021-01-01T00:00:00.000Z') // a Date object represents 2021-01-01\ngetDate('2021/01/01') // a Date object represents 2021-01-01 (might be null in some browsers)\ngetDate('invalid date') // null\ngetDate(undefined) // null\ngetDate(-32) // null\ndateSorter: Sort the values that can be converted to dates from new to old, and the values that cannot be converted to dates will be at the end.
const arr = [\n '2020-01-01',\n 1609459200000,\n '2022-01-01T00:00:00.000Z',\n '2023/01/01',\n 'invalid date',\n undefined,\n -32,\n]\n\narr.sort(dateSorter)\n// [\n// '2023/01/01',\n// '2022-01-01T00:00:00.000Z',\n// 1609459200000,\n// '2020-01-01',\n// 'invalid date',\n// undefined,\n// -32,\n// ]\nisLinkHttp(x): Check if x is a valid HTTP URL.isLinkWithProtocol(x): Check if x is a valid URL with protocol.isLinkExternal(x): Check if x is a valid external URL.isLinkAbsolute(x): Check if x is a valid absolute URL.ensureEndingSlash(x): Ensure x ends with a slash.ensureLeadingSlash(x): Ensure x starts with a slash.removeEndingSlash(x): Ensure x does not end with a slash.removeLeadingSlash(x): Ensure x does not start with a slash.Artalk is a neat self-hosted commenting system that you can easily deploy on your server and put into your front-end page.
\nCome to your blog, or anywhere, place the Artalk comment box, so that the page has rich social functions.
\n\nnpm i -D artalk\nSee the Artalk documentation.
\nPlease set provider: \"Artalk\" and pass your server link to server in the plugin options.
For other configuration items, see Artalk Config.
\nTIP
\nThe plugin retains the el option and inserts Artalk itself on the page. At the same time, the plugin will automatically set the pageTitle, pageKey and site options for you according to the VuePress information.
To let Artalk apply the correct theme, you need to pass a boolean value to <CommentService /> through darkmode prop, representing whether the dark mode is currently enabled.
See Artalk Configuration for details.
\nThe el pageTitle, pageKey and site options are reserved for plugins, they will be inferred from VuePress config.
Two function options imgUploader and avatarURLBuilder can only be set on client side.
You can directly configure serializable options in the plugin options:
\nimport { defineUserConfig } from 'vuepress'\nimport { commentPlugin } from 'vuepress-plugin-comment2'\n\nexport default defineUserConfig({\n plugins: [\n commentPlugin({\n provider: 'Artalk',\n // other options\n // ...\n }),\n ],\n})\nYou can use the defineArtalkConfig function to customize Artalk:
import { defineClientConfig } from 'vuepress/client'\nimport { defineArtalkConfig } from 'vuepress-plugin-comment2/client'\n\ndefineArtalkConfig({\n // Artalk config\n})\n\nexport default defineClientConfig({\n // ...\n})\nGiscus is a commenting system based on GitHub Discussion that is easy to start.
\n\nCreate a public repository and open discussion panel as a place to store comments.
\nInstall the Giscus App to have permission to access the corresponding repository.
\nAfter completing the above steps, please go to the Giscus page to get your settings.
\nYou just need to fill in the repository and Discussion categories, then scroll to the \"Enable giscus\" section at the bottom of the page and obtain four attributes: data-repo, data-repo-id, data-category and data-category-id.
Please set provider: \"Giscus\" and pass data-repo, data-repo-id, data-category and data-category-id as plugin options as repo, repoId, category categoryId.
For other options, see Giscus Config.
\nBy default, the theme of Giscus is light or dark (based on darkmode status).
Darkmode
\nTo let Giscus apply the correct theme, you need to pass a boolean value to <CommentService /> via darkmode property, indicating whether darkmode is currently enabled.
If you want to customize theme in lightmode and darkmode, you can set lightTheme and darkTheme option with a built-in theme keyword or a custom CSS link starting with https://.
stringstringstringstringstring\"pathname\"booleantruebooleantruebooleantrue\"top\" | \"bottom\"\"top\"Type: GiscusTheme
type GiscusTheme =\n | 'light'\n | 'light_high_contrast'\n | 'light_protanopia'\n | 'dark'\n | 'dark_high_contrast'\n | 'dark_protanopia'\n | 'dark_dimmed'\n | 'transparent_dark'\n | 'preferred_color_scheme'\n | `https://${string}`\nDefault: \"light\"
Details:
\nGiscus theme used in lightmode
\nShould be a built-in theme keyword or a css link starting with https://.
Type: GiscusTheme
type GiscusTheme =\n | 'light'\n | 'light_high_contrast'\n | 'light_protanopia'\n | 'dark'\n | 'dark_high_contrast'\n | 'dark_protanopia'\n | 'dark_dimmed'\n | 'transparent_dark'\n | 'preferred_color_scheme'\n | `https://${string}`\nDefault: \"dark\"
Details:
\nGiscus theme used in darkmode
\nShould be a built-in theme keyword or a css link starting with https://.
You can directly configure serializable options in the plugin options:
\nimport { defineUserConfig } from 'vuepress'\nimport { commentPlugin } from 'vuepress-plugin-comment2'\n\nexport default defineUserConfig({\n plugins: [\n commentPlugin({\n provider: 'Giscus',\n // other options\n // ...\n }),\n ],\n})\nYou can use the defineGiscusConfig function to customize Giscus:
import { defineClientConfig } from 'vuepress/client'\nimport { defineGiscusConfig } from 'vuepress-plugin-comment2/client'\n\ndefineGiscusConfig({\n // Giscus config\n})\n\nexport default defineClientConfig({\n // ...\n})\nA concise, safe and free static site commenting system, based on Tencent Cloud Development.
\n\nnpm i -D twikoo\nApply for MongoDB account
\nCreate a free MongoDB database, the recommended region is AWS / N. Virginia (us-east-1)
Click CONNECT on the Clusters page, follow the steps to allow connections from all IP addresses (Why?), create Database user, and record the database connection string, please change the <password> in the connection string to the database password
Sign up for a Vercel account
\nClick the button below to deploy Twikoo to Vercel in one click
\nGo to Settings - Environment Variables, add the environment variable MONGODB_URI, the value is the database connection string in step 3
Go to Overview, click the link under Domains, if the environment configuration is correct, you can see the prompt \"Twikoo cloud function is running normally\"
\nVercel Domains (with https:// prefix, e.g. https://xxx.vercel.app) is your environment ID
Please set provider: \"Twikoo\" and set envId in the plugin options.
For other configuration items, see Twikoo Config.
\n", + "image": "https://vercel.com/button", + "date_modified": "2024-03-11T08:20:01.000Z", + "authors": [], + "tags": [] + }, + { + "title": "Twikoo Options", + "url": "https://ecosystem.vuejs.press/ecosystem/plugins/comment/twikoo/config.html", + "id": "https://ecosystem.vuejs.press/ecosystem/plugins/comment/twikoo/config.html", + "summary": "Twikoo Options Config envId Type: string Required: Yes Details: Vercel address. Plugin Config You can directly configure serializable options in the plugin options: Client Confi...", + "content_html": "\nstringYou can directly configure serializable options in the plugin options:
\nimport { defineUserConfig } from 'vuepress'\nimport { commentPlugin } from 'vuepress-plugin-comment2'\n\nexport default defineUserConfig({\n plugins: [\n commentPlugin({\n provider: 'Twikoo',\n // other options\n // ...\n }),\n ],\n})\nYou can use the defineTwikooConfig function to customize Twikoo:
import { defineClientConfig } from 'vuepress/client'\nimport { defineTwikooConfig } from 'vuepress-plugin-comment2/client'\n\ndefineTwikooConfig({\n // Twikoo config\n})\n\nexport default defineClientConfig({\n // ...\n})\nA safe comment system with backend.
\n\nnpm i -D @waline/client\nClick Create app button to create a new app and enter a name you like:
\n\nEnter the app, then select Settings > App Keys at the left bottom corner. You will see APP ID, APP Key and Master Key of your app. We will use them later
Click the dark button above, it will redirect you to vercel to deploy with waline template.
\nTIP
\nIf you haven't logged in, we recommend you to sign in with GitHub.
\nInput your Vercel project name then click Create.
![\"skip](\"/images/comment/vercel-2.png\")
Repo which named you input before will be created and initialized automatically base on waline example template by Vercel.
\n![\"deploy\"](\"/images/comment/vercel-3.png\")
After one minute or two, vercel should finish the deployment. Click Go to Dashboard button to redirect to your application dashboard.
![\"deploy\"](\"/images/comment/vercel-4.png\")
Click Settings menu on the top, and Environment Variables button on the side to go to environment variables setting page. Then set LEAN_ID, LEAN_KEY and LEAN_MASTER_KEY. The variables' value should be the ones you got in the previous step. APP ID is the value of LEAN_ID, and APP Key to LEAN_KEY, Master Key to LEAN_MASTER_KEY.
![\"set](\"/images/comment/vercel-5.png\")
To let your environment variables setting active, you need redeploy your application. Click Deployments menu on the top and find the latest deployment at the top of list, click Redeploy button in the right dropdown menu.
![\"redeploy\"](\"/images/comment/vercel-6.png\")
If everything is ok, vercel will redirect to Overview page to start redeployment. Wait a moment the STATUS will change to Ready. Now you can click Visit to visit the site. This link is your server address.
![\"redeploy](\"/images/comment/vercel-7.png\")
Click Settings - Domains to go to domain setting page.
Input domain you want to assign and click Add button.
![\"Add](\"/images/comment/vercel-8.png\")
Add a new CNAME record in your domain service server.
| Type | Name | Value |\n|
\nstringType: (string | WalineEmojiInfo)[] | false
type WalineEmojiPresets = `http://${string}` | `https://${string}`\n\ninterface WalineEmojiInfo {\n /**\n * Emoji name show on tab\n */\n name: string\n /**\n * Current folder link\n */\n folder?: string\n /**\n * Common prefix of Emoji icons\n */\n prefix?: string\n /**\n * Type of Emoji icons, will be regarded as file extension\n */\n type?: string\n /**\n * Emoji icon show on tab\n */\n icon: string\n /**\n * Emoji image list\n */\n items: string[]\n}\nDefault: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
Reference:
\nDetails: Emoji settings.
\nType: string | boolean
Default: false
Reference:
\nDetails:
\nDarkmode support
\n'auto' will display darkmode due to device settings.Type: WalineCommentSorting
Default: 'latest'
Details:
\nComment list sorting methods.
\nOptional values: 'latest', 'oldest', 'hottest'
Type: string[]
Default: ['nick','mail','link']
Details:
\nReviewer attributes.
\nOptional values: 'nick', 'mail', 'link'
Type: string[]
Default: []
Details:
\nSet required fields, optional values:
\n[]['nick']['nick','mail']Type: string
Default value: 'enable'
Details:
\nLogin mode status, optional values:
\n'enable': enable login (default)'disable': Login is disabled, users should fill in information to comment'force': Forced login, users must login to commentType: number | [number, number]
Default: 0
Details:
\nComment words limit. When a single number is filled in, it 's the maximum number of comment words. No limit when set to 0.
Type: number
Default: 10
Details:
\nNumber of comments per page.
\nType: WalineImageUploader | false
type WalineImageUploader = (image: File) => Promise<string>\nReference:
\n\nDetails:
\nCustom image upload method. The default behavior is to embed images Base 64 encoded, you can set this to false to disable image uploading.
The function should receive an image object and return a Promise that provides the image address.
\nType: WalineHighlighter | false
type WalineHighlighter = (code: string, lang: string) => string\nReference:
\n\nDetails:
\nCode highlighting, use hanabi by default. The function passes in original content of code block and language of the code block. You should return a string directly.
You can pass in a code highlighter of your own, or set to false to disable code highlighting.
Type: WalineTexRenderer | false
type WalineTexRenderer = (blockMode: boolean, tex: string) => string\nReference:
\n\nDetails:
\nCustomize TeX rendering, the default behavior is to prompt that the preview mode does not support TeX. The function provides two parameters, the first parameter indicates whether it should be rendered in block level, and the second parameter is the string of the TeX content, and return a HTML string as render result.
\nYou can import TeX renderer to provide preview feature. We recommend you to use Katex or MathJax, or you can set to false to disable parsing TeX.
Type: WalineSearchOptions | false
interface WalineSearchImageData extends Record<string, unknown> {\n /**\n * Image link\n */\n src: string\n\n /**\n * Image title\n *\n * @description Used for alt attribute of image\n */\n title?: string\n\n /**\n * Image preview link\n *\n * @description For better loading performance, we will use this thumbnail first in the list\n *\n * @default src\n */\n preview?: string\n}\n\ntype WalineSearchResult = WalineSearchImageData[]\n\ninterface WalineSearchOptions {\n /**\n * Search action\n */\n search: (word: string) => Promise<WalineSearchResult>\n\n /**\n * Default result when opening list\n *\n * @default () => search('')\n */\n default?: () => Promise<WalineSearchResult>\n\n /**\n * Fetch more action\n *\n * @description It will be triggered when the list scrolls to the bottom. If your search service supports paging, you should set this to achieve infinite scrolling\n *\n * @default (word) => search(word)\n */\n more?: (word: string, currentCount: number) => Promise<WalineSearchResult>\n}\nDetails: Customize search features, you can disable search function by setting it to false.
Type: string
Details:
\nreCAPTCHA V3 is a captcha service provided by Google. You can add reCAPTCHA V3 site key with recaptchaV3Key to enable it.
You should also set environment variable RECAPTCHA_V3_SECRET for server.
Type: boolean | string[]
Default: false
Details:
\nAdd emoji interaction function to the article, set it to true to provide the default emoji, you can also customize the emoji image by setting the emoji url array, and supports a maximum of 8 emojis.
booleantrueType: WalineLocales
interface WalineLocales {\n [localePath: string]: WalineLocale\n}\nReference:
\nDetails:\nWaline locales.
\nYou can directly configure serializable options in the plugin options:
\nimport { defineUserConfig } from 'vuepress'\nimport { commentPlugin } from 'vuepress-plugin-comment2'\n\nexport default defineUserConfig({\n plugins: [\n commentPlugin({\n provider: 'Waline',\n // other options\n // ...\n }),\n ],\n})\nYou can use the defineWalineConfig function to customize Waline:
import { defineClientConfig } from 'vuepress/client'\nimport { defineWalineConfig } from 'vuepress-plugin-comment2/client'\n\ndefineWalineConfig({\n // Waline config\n})\n\nexport default defineClientConfig({\n // ...\n})\nBundler function is for appending or modifying bundler options in theme and plugins.
\nAll functions should be called in extendsBundlerOptions lifecycle hook.
TIP
\nWe are omitting that in examples. The actual code should be like this:
\n// import functions you need\nimport { addCustomElement } from '@vuepress/helper'\n\nexport const yourPlugin = {\n // ...\n extendsBundlerOptions: (bundlerOptions, app) => {\n // add them here\n addCustomElement(bundlerOptions, app, 'my-custom-element')\n },\n}\nGet current bundler name.
\nexport const getBundlerName: (app: App) => string\n// @vuepress/bundler-vite\ngetBundleName(app) === 'vite' // true\n// @vuepress/bundler-webpack\ngetBundleName(app) === 'webpack' // true\nAdd a custom element declaration to the current bundler.
\n/**\n * Add tags as customElement\n *\n * @param bundlerOptions VuePress Bundler config\n * @param app VuePress Node App\n * @param customElements tags recognized as custom element\n */\nexport const addCustomElement = (\n bundlerOptions: unknown,\n app: App,\n customElement: string[] | string | RegExp\n) => void;\nimport { addCustomElement } from '@vuepress/helper'\n\naddCustomElement(bundlerConfig, app, 'my-custom-element')\naddCustomElement(bundlerOptions, app, [\n 'custom-element1',\n 'custom-element2',\n // all tags start with `math-`\n /^math-/,\n])\nProvides contents for specific path in dev server.
\nexport interface DevServerOptions {\n /**\n * Path to be responded\n */\n path: string;\n /**\n * Respond function\n */\n response: (request?: IncomingMessage) => Promise<string | Buffer>;\n\n /**\n * error msg\n */\n errMsg?: string;\n}\n\n/**\n * Handle specific path when running VuePress Dev Server\n *\n * @param bundlerOptions VuePress Bundler config\n * @param app VuePress Node App\n * @param path Path to be responded\n * @param response respond function\n * @param errMsg error msg\n */\nexport const customizeDevServer: (\n bundlerOptions: unknown,\n app: App,\n {\n errMsg:\"The server encountered an error\",\n response: responseHandler,\n path,\n }: CustomServerOptions\n) => void;\nimport { useCustomDevServer } from '@vuepress/helper'\n\n// handle `/api/` path\nuseCustomDevServer(bundlerOptions, app, {\n path: '/api/',\n response: async () => getData(),\n errMsg: 'Unexpected api error',\n})\naddViteOptimizeDepsInclude
\nAdd modules to Vite optimizeDeps.include list
TIP
\nIf a package meets one of the following conditions, you should consider adding it here.
\nimport()addViteOptimizeDepsExclude
\nAdd modules to Vite optimizeDeps.exclude list
If a package and its dependencies are all pure ESM packages, you should consider adding it here.
\naddViteSsrExternal
\nAdd modules to Vite ssr.external list
If a package is a pure ESM package and does not use aliases or define variables, you should consider adding it here.
\naddViteSsrNoExternal
\nAdd modules to Vite ssr.noExternal list
If an alias or define is used within a package, you must add it here.
\n/**\n * Add modules to Vite `optimizeDeps.include` list\n */\nexport const addViteOptimizeDepsInclude: (\n bundlerOptions: unknown,\n app: App,\n module: string | string[],\n) => void\n\n/**\n * Add modules to Vite `optimizeDeps.exclude` list\n */\nexport const addViteOptimizeDepsExclude: (\n bundlerOptions: unknown,\n app: App,\n module: string | string[],\n) => void\n\n/**\n * Add modules to Vite `ssr.external` list\n */\nexport const addViteSsrExternal: (\n bundlerOptions: unknown,\n app: App,\n module: string | string[],\n) => void\n\n/**\n * Add modules to Vite `ssr.noExternal` list\n */\nexport const addViteSsrNoExternal: (\n bundlerOptions: unknown,\n app: App,\n module: string | string[],\n) => void\nimport {\n addViteOptimizeDepsInclude,\n addViteOptimizeDepsExclude,\n addViteSsrExternal,\n addViteSsrNoExternal,\n} from '@vuepress/helper'\n\naddViteOptimizeDepsInclude(bundlerOptions, app, ['vue', 'vue-router'])\naddViteOptimizeDepsExclude(bundlerOptions, app, 'packageA')\naddViteSsrNoExternal(bundlerOptions, app, ['vue', 'vue-router'])\naddViteSsrExternal(bundlerOptions, app, 'packageA')\naddViteConfig
\nA function for you to add vite config
\nexport const addViteConfig: (\n bundlerOptions: unknown,\n app: App,\n config: Record<string, unknown>,\n) => void\nimport { addViteConfig } from '@vuepress/helper'\n\naddViteConfig(bundlerOptions, app, {\n build: {\n charset: 'utf8',\n },\n})\nmergeViteConfig
\nA function for you to merge vite config.
\nWARNING
\nYour users may choose to use other bundler so it's pretty bad to declare vite as deps!
\nexport const mergeViteConfig: (\n defaults: Record<string, any>,\n overrides: Record<string, any>,\n) => Record<string, any>\nimport { mergeViteConfig } from '@vuepress/helper'\n\nconfig.viteOptions = mergeViteConfig(config.viteOptions, {\n build: {\n charset: 'utf8',\n },\n})\nchainWebpack
\nChain webpack config.
\nexport const chainWebpack: (\n bundlerOptions: unknown,\n app: App,\n chainWebpack: (\n config: WebpackChainConfig,\n isServer: boolean,\n isBuild: boolean,\n ) => void,\n) => void\nimport { chainWebpack } from '@vuepress/helper'\n\nchainWebpack(bundlerOptions, app, (config, isServer, isBuild) => {\n // do some customize here\n})\nconfigWebpack
\nConfig Webpack
\nexport const configWebpack: (\n bundlerOptions: unknown,\n app: App,\n configureWebpack: (\n config: WebpackConfiguration,\n isServer: boolean,\n isBuild: boolean,\n ) => void,\n) => void\nimport { configWebpack } from '@vuepress/helper'\n\nconfigWebpack(bundlerOptions, app, (config, isServer, isBuild) => {\n // do some customize here\n})\nThese functions generate common information for your pages.
\nGet the excerpt of the page.
\nexport interface PageExcerptOptions {\n /**\n * Excerpt separator\n *\n * @default \"<!-- more -->\"\n */\n separator?: string\n\n /**\n * Length of excerpt\n *\n * @description Excerpt length will be the minimal possible length reaching this value\n *\n * @default 300\n */\n length?: number\n\n /**\n * Tags which is considered as custom elements\n *\n * @description This is used to determine whether a tag is a custom element since all unknown tags are removed in excerpt.\n */\n isCustomElement?: (tagName: string) => boolean\n\n /**\n * Whether keep page title (first h1) in excerpt\n *\n * @default false\n */\n keepPageTitle?: boolean\n\n /**\n * Whether preserve tags like line numbers and highlight lines for code blocks\n *\n * @default false\n */\n keepFenceDom?: boolean\n}\n\nexport const getPageExcerpt: (\n app: App,\n page: Page,\n options?: PageExcerptOptions,\n) => string\nGet plain text of the page.
\nexport interface PageTextOptions {\n /**\n * Whether convert text to single line content\n *\n * @default false\n */\n singleLine?: boolean\n\n /**\n * Length of text\n *\n * @description Text length will be the minimal possible length reaching this value\n *\n * @default 300\n */\n length?: number\n\n /**\n * Tags to be removed\n *\n * @description Table and code blocks are removed by default.\n *\n * @default ['table', 'pre']\n */\n removedTags?: string[]\n}\n\nexport const getPageText: (\n app: App,\n page: Page,\n options?: PageTextOptions,\n) => string\n
This plugin will listen to page scroll event. When the page scrolls to a certain header anchor, this plugin will change the route hash to that header anchor if there is a corresponding header link.
This plugin is mainly used to develop themes, and has been integrated into the default theme. You won't need to use it directly in most cases.
npm i -D @vuepress/plugin-active-header-links@next
+import { activeHeaderLinksPlugin } from '@vuepress/plugin-active-header-links'
+
+export default {
+ plugins: [
+ activeHeaderLinksPlugin({
+ // options
+ }),
+ ],
+}
+Type: string
Default: 'a.sidebar-item'
Details:
Selector of header link.
If a header anchor does not have a corresponding header link, this plugin won't change the route hash to that anchor when scrolling to it.
Type: string
Default: '.header-anchor'
Details:
Selector of header anchor.
You don't need to specify this option unless you have changed the permalinkClass option of markdown-it-anchor via markdown.anchor.
Also see:
Type: number
Default: 200
Details:
The delay of the debounced scroll event listener.
Type: number
Default: 5
Details:
Even if you click the link of the header anchor directly, the scrollTop might not be exactly equal to offsetTop of the header anchor, so we add an offset to avoid the error.
This plugin will append writing date to frontmatter with @vuepress/plugin-git.
npm i -D @vuepress/plugin-append-date@next
+import { appendDatePlugin } from '@vuepress/plugin-append-date'
+
+export default {
+ plugins: [appendDatePlugin()],
+}
+Type: string
Default: "date"
Details:
Frontmatter key to use when appending date.
Type: "date" | "time" | "full"
Default: "date"
Details:
Format of the date value when appending date.
This plugin will add a back to top button to your site. The button will be displayed in the bottom right corner of the page when scrolling down. By clicking the button, the page will scroll to the top.
This plugin has been integrated into the default theme.
npm i -D @vuepress/plugin-back-to-top@next
+import { backToTopPlugin } from '@vuepress/plugin-back-to-top'
+
+export default {
+ plugins: [backToTopPlugin()],
+}
+number100booleantrueYou can customize the style of the back to top button via CSS variables:
:root {
+ --back-to-top-z-index: 5;
+ --back-to-top-icon: url("back-to-top.svg");
+ --back-to-top-bg-color: #fff;
+ --back-to-top-color: #3eaf7c;
+ --back-to-top-color-hover: #71cda3;
+ --back-to-top-shadow: rgb(0 0 0 / 20%);
+}
+Integrate Baidu Analytics into VuePress.
TIP
Do not enable SPA mode in Baidu Analytics. The plugin will report page view events correctly.
npm i -D @vuepress/plugin-baidu-analytics@next
+import { baiduAnalyticsPlugin } from '@vuepress/plugin-baidu-analytics'
+
+export default {
+ plugins: [
+ baiduAnalyticsPlugin({
+ // options
+ }),
+ ],
+}
+The plugin will automatically report page view events when visiting and switching pages.
Besides, a global hmt array is available on the window object, and you can use it for custom events reporting.
Type: string
Details: The ID of Baidu Analytics, which is the query of hm.js URL.
Type: (page: Page) => Record<string, unknown>
Required: No
Reference:
Details:
Function getting article info.
Article info will be injected in route meta so that they will be available later in client composables.
Type: (page: Page) => boolean
Default: (page) => Boolean(page.filePathRelative) && !page.frontmatter.home
Reference:
Details:
Page filter, determine whether a page should be included.
By default, all the pages generated from Markdown files but not homepage will be included as articles.
BlogCategoryOptions[]BlogTypeOptions[](name: string) => string(name) => name.replace(/ _/g, '-').replace(/[:?*|\\/<>]/g, "").toLowerCase()booleantruestring<!-- more -->Type: number
Default: 300
Reference:
Details:
Length of excerpt when auto generating.
TIP
Excerpt length will be the minimal possible length reaching this value.
You can set it to 0 to disable auto excerpt generation.
Type: (page: Page) => boolean
Default: filter option
Reference:
Details:
Page filter, determine whether the plugin should generate excerpt for it.
TIP
You should use this to skip pages that you don't need to generate excerpt for. E.g.: If users set excerpt or description in frontmatter, you may want to use them directly.
Type: (tagName: string) => boolean
Default: () => false
Reference:
Details:
Tags which is considered as custom elements.
This is used to determine whether a tag is a custom element since all unknown tags are removed in excerpt.
Type: string
Default: "_blog"
Details:
Key used when injecting info to route meta.
TIP
Setting to an empty key will inject to route meta directly instead of a field.
Type: boolean
Default: Whether using --debug flag
Details:
Whether enable hotReload in devServer.
To theme developers
It's disabled by default because it does have performance impact in sites with a lot of categories and types. And it can slow down hotReload speed when editing Markdown.
If users are adding or organizing your categories or tags, you may tell them to enable this, for the rest it's better to keep it disabled.
Also, you can try to detect number of pages in users project and decide whether to enable it.
Blog category config should be an array, while each item is controlling a "category" rule.
interface BlogCategoryOptions {
+ /**
+ * Unique category name
+ */
+ key: string
+
+ /**
+ * Function getting category from page
+ */
+ getter: (page: Page) => string[]
+
+ /**
+ * A custom function to sort the pages
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * Path pattern of page to be registered
+ *
+ * @description `:key` will be replaced by the "slugify" result of the original key
+ *
+ * @default `/:key/`
+ */
+ path?: string
+
+ /**
+ * Page layout name
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Frontmatter
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+
+ /**
+ * Item page path pattern or custom function to be registered
+ *
+ * @description When filling in a string, `:key` and `:name` will be replaced by the "slugify" result of the original key and name
+ *
+ * @default `/:key/:name/`
+ */
+ itemPath?: string | ((name: string) => string)
+
+ /**
+ * Item page layout name
+ *
+ * @default 'Layout'
+ */
+ itemLayout?: string
+
+ /**
+ * Items Frontmatter
+ */
+ itemFrontmatter?: (name: string, localePath: string) => Record<string, string>
+}
+Blog type config should be an array, while each item is controlling a "type" rule.
interface BlogTypeOptions {
+ /**
+ * Unique type name
+ */
+ key: string
+
+ /**
+ * A filter function to determine whether a page should be the type
+ */
+ filter: (page: Page) => boolean
+
+ /**
+ * A custom function to sort the pages
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * Page path to be registered
+ *
+ * @default '/:key/'
+ */
+ path?: string
+
+ /**
+ * Layout name
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Frontmatter
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+}
+You can import the following API from @vuepress/plugin-blog/client.
Blog category
const useBlogCategory: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogCategoryData<T>>
+Argument key should be the category unique key.
If no key is passed, the plugin will try to use the key in current path.
Blog category
const useBlogType: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogTypeData<T>>
+Argument key should be the type unique key.
If no key is passed, the plugin will try to use the key in current path.
Returning values are:
interface Article<T extends Record<string, unknown> = Record<string, unknown>> {
+ /** Article path */
+ path: string
+ /** Article info */
+ info: T
+}
+
+interface BlogCategoryData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** Category path */
+ path: string
+
+ /**
+ * Only available when current route matches an item path
+ */
+ currentItems?: Article<T>[]
+
+ /** Category map */
+ map: {
+ /** Unique key under current category */
+ [key: string]: {
+ /** Category path of the key */
+ path: string
+ /** Category items of the key */
+ items: Article<T>[]
+ }
+ }
+}
+
+interface BlogTypeData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** Type path */
+ path: string
+
+ /** Items under current type */
+ items: Article<T>[]
+}
+With @vuepress/plugin-blog, you can easily bring blog feature into your theme.
The plugin filters all pages using filter option to drop pages you don't want.
By default, all pages generating from Markdown files but not homepage are considered as articles.
You can fully customize pages to collect through option filter, which accepts a function (page: Page) => boolean.
You should set getInfo option with a function accepting Page as argument and returning an object containing the info you want.
The plugin will collect all the info you want and write them to routeMeta field of each page, so you will be able to get this information through Composition API later.
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ filter: ({ filePathRelative, frontmatter }) => {
+ // drop those pages which is NOT generated from file
+ if (!filePathRelative) return false
+
+ // drop those pages in `archives` directory
+ if (filePathRelative.startsWith('archives/')) return false
+
+ // drop those pages which do not use default layout
+ if (frontmatter.home || frontmatter.layout) return false
+
+ return true
+ },
+
+ getInfo: ({ frontmatter, git = {}, data = {} }) => {
+ // getting page info
+ const info: Record<string, any> = {
+ author: frontmatter.author || '',
+ categories: frontmatter.categories || [],
+ date: frontmatter.date || git.createdTime || null,
+ tags: frontmatter.tags || [],
+ excerpt: data.excerpt || '',
+ }
+
+ return info
+ },
+ }),
+ // other plugins ...
+ ],
+}
+Basically, you would want 2 types of collection in your blog:
Category:
"Category" means grouping articles with their labels.
For example, each article may have their "categories" and "tags".
Type:
"Type" means identifying articles with conditions.
For example, you may want to describe some of your articles as diary.
After understanding description of these 2 types, you can set category and type options, each accepts an array, and each element represents a configuration.
Let's start with 2 examples here.
Imagine you are setting tags for each articles with tag field in page frontmatter. You want a tag mapping page in /tag/ with TagMap layout, and group each tag list with tagName in /tag/tagName with TagList layout, you probably need a configuration like this:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // other options ...
+ category: [
+ {
+ key: 'tag',
+ getter: ({ frontmatter }) => frontmatter.tag || [],
+ path: '/tag/',
+ layout: 'TagMap',
+ frontmatter: () => ({ title: 'Tag page' }),
+ itemPath: '/tag/:name/',
+ itemLayout: 'TagList',
+ itemFrontmatter: (name) => ({ title: `Tag ${name}` }),
+ },
+ ],
+ }),
+ // other plugins ...
+ ],
+}
+Also, you may want to star some of your articles, and display them to visitors. When you are setting star: true in frontmatter to mark them, you probably need a configuration like this to display them in /star/ path with StarList layout:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // other options ...
+ type: [
+ {
+ key: 'star',
+ filter: ({ frontmatter }) => frontmatter.star,
+ path: '/star/',
+ layout: 'StarList',
+ frontmatter: () => ({ title: 'Star page' }),
+ },
+ ],
+ }),
+ // other plugins ...
+ ],
+}
+See, setting these 2 types is easy. For full options, please see Category Config and Type Config.
When generating each page, the plugin will set following information under frontmatter.blog:
interface BlogFrontmatterOptions {
+ /** Current type of the page */
+ type: 'category' | 'type'
+ /** Unique key under current category or tag */
+ key: string
+ /**
+ * Current category name
+ *
+ * @description Only available in category item page
+ */
+ name?: string
+}
+So you can invoke useBlogCategory() and useBlogType() directly, and the result will be the category or type bind to current route.
Also, you can pass key you want as argument, then you will get information bind to that key.
So with node side settings above, you can get information about "tag" and "star" in client side:
TagMap layout:
<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+
+<template>
+ <div>
+ <h1>Tag page</h1>
+ <ul>
+ <li v-for="({ items, path }, name) in categoryMap.map">
+ <RouteLink :key="name" :to="path" class="category">
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </li>
+ </ul>
+ </div>
+</template>
+TagList layout:
<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+
+<template>
+ <div>
+ <h1>Tag page</h1>
+ <div class="category-wrapper">
+ <RouteLink
+ v-for="({ items, path }, name) in categoryMap.map"
+ :key="name"
+ :to="path"
+ class="category"
+ >
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </div>
+ <div class="article-wrapper" v-if="categoryMap.currentItems">
+ <div v-if="!categoryMap.currentItems.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in categoryMap.currentItems"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline
+ ? `${new Date(info.date).toLocaleDateString()}: `
+ : '') + info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author"
+ >Author: {{ info.author }}</span
+ >
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag"
+ >Tag: {{ info.tag.join(', ') }}</span
+ >
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+ </div>
+</template>
+StarList layout:
<script setup lang="ts">
+import { useBlogType } from '@vuepress/plugin-blog/client'
+import { RouteLink } from 'vuepress/client'
+
+import ArticleList from '../components/ArticleList.vue'
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+
+const stars = useBlogType('star')
+</script>
+
+<template>
+ <div class="article-wrapper" v-if="stars.items">
+ <div v-if="!stars.items.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in stars.items"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline ? `${new Date(info.date).toLocaleDateString()}: ` : '') +
+ info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author">Author: {{ info.author }}</span>
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag">Tag: {{ info.tag.join(', ') }}</span>
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+</template>
+For return types, please see Composition API Return Types.
This plugin adds native i18n support, so your settings will be automatically applied to each language.
For example, if user has the following locales' config, and you are setting the "star" example above:
export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+}
+Then /zh/star/ and /star/ will both be available, and only articles under the correct locale will appear.
This plugin provides a built-in excerpt generator, which can be enabled by setting excerpt option to true.
Excerpt introduction
An excerpt is an HTML fragment that is used to display a short description of an article in the blog list, so the excerpt has the following restrictions:
isCustomElement option..vuepress/public or full URL to ensure they can be accessed in other places.The excerpt generator will try to find a valid excerpt separator from markdown contents, if it finds one, it will use content before the separator. The separator is default <!-- more -->, and you can customize it by setting excerptSeparator option.
If it cannot find a valid separator, it will parse content from the beginning of markdown file, and stop till its length reaches a preset value. The value is default 300, and you can customize it by setting excerptLength option.
To choose which page should generate excerpt, you can use excerptFilter option.
Example
Normally you may want to use frontmatter.description if users set them, so you can let filter function return false if frontmatter.description is not empty.
The plugin can automatically generate catalog pages and provide catalog components.
npm i -D @vuepress/plugin-catalog@next
+import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ plugins: [
+ catalogPlugin({
+ // Your options
+ }),
+ ],
+}
+First, you should set catalog info in routeMeta:
import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ extendsPage: (page) => {
+ // set catalog info in routeMeta
+ page.routeMeta = {
+ // catalog title
+ title: page.title,
+ // ... other information
+ }
+ },
+}
+You can then import defineCatalogInfoGetter from @vuepress/plugin-catalog/client and use it in client config file to extract catalog info from meta.
import { defineCatalogInfoGetter } from '@vuepress/plugin-catalog/client'
+
+defineCatalogInfoGetter((meta) => (meta.title ? { title: meta.title } : null))
+
+export default {}
+Catalog info should contains:
title: catalog titleorder: catalog order (optional)content: catalog content component (optional)Sorting with order
The plugin will sort pages by order in the following way:
// order positive numbers from small to large
+Project with order 1
+Project with order 2
+...
+Project with order 10
+...
+// Project without order
+Project without order
+Project without order
+...
+// order negative numbers from small to large
+Project with order -10
+// ...
+Project with order -2
+Project with order -1
+1 | 2 | 33booleanfalseType: (path: string) => Record<string, any>
Required: No
Details: Frontmatter getter for the generated page.
Example:
import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ plugins: [
+ catalogPlugin({
+ frontmatter: (path) => ({
+ // frontmatter you want
+ // you may customize title, author. time, etc.
+ }),
+ }),
+ ],
+}
+Type: (RegExp | string)[]
Default: []
Details:
Catalog page path to be excluded during generation.
"/foo/" means only exclude catalog page generation at /foo/ folder./^\/foo\// means exclude catalog page generation at /foo/ folder and its subfolders.404 pages will be automatically excluded.
stringType: CatalogPluginLocaleConfig
interface CatalogPluginLocaleData {
+ /**
+ * Catalog title
+ */
+ title: string
+
+ /**
+ * Empty hint
+ */
+ empty: string
+}
+
+interface CatalogPluginLocaleConfig {
+ [localePath: string]: CatalogPluginLocaleData
+}
+Required: No
Details: Locales config for catalog component.
interface CatalogInfo {
+ /** Catalog title */
+ title: string
+ /** Catalog order */
+ order?: number
+ /** Catalog content */
+ content?: Component
+}
+
+type CatalogInfoGetter = (meta: Record<string, unknown>) => CatalogInfo | null
+
+const defineCatalogInfoGetter: (options: CatalogInfoGetter) => void
+Customize how to extract catalog info from meta.
Details:
The plugin will globally register a <Catalog /> component by default (unless you set the component option).
You can use <Catalog /> in the theme layout or directly in the Markdown file.
The component supports four props:
level: Change the display depth (maximum support 3 levels), default is 3.base: Display catalog of the specified folder, default is the current folder directory.index: Add an index number to the directory item, default is no number.hideHeading: Hide the component title, default is to display the Catalog title.You can customize the style of catalog via CSS variables:
:root {
+ --catalog-bg-color: #fff;
+ --catalog-bg-secondary-color: #f8f8f8;
+ --catalog-border-color: #e5e5e5;
+ --catalog-active-color: #3eaf7c;
+ --catalog-hover-color: #71cda3;
+}
+See Artalk Configuration for details.
The el pageTitle, pageKey and site options are reserved for plugins, they will be inferred from VuePress config.
Two function options imgUploader and avatarURLBuilder can only be set on client side.
You can directly configure serializable options in the plugin options:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineArtalkConfig function to customize Artalk:
import { defineClientConfig } from 'vuepress/client'
+import { defineArtalkConfig } from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // Artalk config
+})
+
+export default defineClientConfig({
+ // ...
+})
+Artalk is a neat self-hosted commenting system that you can easily deploy on your server and put into your front-end page.
Come to your blog, or anywhere, place the Artalk comment box, so that the page has rich social functions.
npm i -D artalk
+See the Artalk documentation.
Please set provider: "Artalk" and pass your server link to server in the plugin options.
For other configuration items, see Artalk Config.
TIP
The plugin retains the el option and inserts Artalk itself on the page. At the same time, the plugin will automatically set the pageTitle, pageKey and site options for you according to the VuePress information.
To let Artalk apply the correct theme, you need to pass a boolean value to <CommentService /> through darkmode prop, representing whether the dark mode is currently enabled.
stringstringstringstringstring"pathname"booleantruebooleantruebooleantrue"top" | "bottom""top"Type: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+Default: "light"
Details:
Giscus theme used in lightmode
Should be a built-in theme keyword or a css link starting with https://.
Type: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+Default: "dark"
Details:
Giscus theme used in darkmode
Should be a built-in theme keyword or a css link starting with https://.
You can directly configure serializable options in the plugin options:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Giscus',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineGiscusConfig function to customize Giscus:
import { defineClientConfig } from 'vuepress/client'
+import { defineGiscusConfig } from 'vuepress-plugin-comment2/client'
+
+defineGiscusConfig({
+ // Giscus config
+})
+
+export default defineClientConfig({
+ // ...
+})
+Giscus is a commenting system based on GitHub Discussion that is easy to start.
Create a public repository and open discussion panel as a place to store comments.
Install the Giscus App to have permission to access the corresponding repository.
After completing the above steps, please go to the Giscus page to get your settings.
You just need to fill in the repository and Discussion categories, then scroll to the "Enable giscus" section at the bottom of the page and obtain four attributes: data-repo, data-repo-id, data-category and data-category-id.
Please set provider: "Giscus" and pass data-repo, data-repo-id, data-category and data-category-id as plugin options as repo, repoId, category categoryId.
For other options, see Giscus Config.
By default, the theme of Giscus is light or dark (based on darkmode status).
Darkmode
To let Giscus apply the correct theme, you need to pass a boolean value to <CommentService /> via darkmode property, indicating whether darkmode is currently enabled.
If you want to customize theme in lightmode and darkmode, you can set lightTheme and darkTheme option with a built-in theme keyword or a custom CSS link starting with https://.
You can both set options with plugin options on Node side and set options in client config file on Browser side.
import { commentPlugin } from 'vuepress-plugin-comment2'
+
+// .vuepress/config.ts
+export default {
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo
+
+ // other options here
+ // ...
+ }),
+ ],
+}
+import { defineClientConfig } from 'vuepress/client'
+import {
+ defineArtalkConfig,
+ // defineGiscusConfig,
+ // defineTwikooConfig,
+ // defineWalineConfig,
+} from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+But here are some limitations you should remember:
provider, locales and other resource related option must be set in plugin options.
To ensure tree-shaking works, we must optimize entries at node so that bundler can understand which resource should be included in the final bundle.
These options will be marked with Plugin Option Only in config reference.
Options which can not be serialized to JSON must be set in client config.
Options that receives function values can not be set in plugin options, as plugins are running under Node.js environment, so we can not pass these values and their contexts to browser.
These options will be marked with Client Config Only in config reference.
This plugin globally registers a component <CommentService />.
alias and layout slots to insert the component. We recommended you to insert the comment component (<CommentService />) after the <PageNav /> component, and the current page is a demo with default theme.By default, <CommentService /> component is enabled globally, and you can use comment option in both plugin options and page frontmatter to control it.
comment: false in page frontmatter.comment to false in the plugin options. Then you can set comment: true in page frontmatter to enable it locally.You can set commentID option in page frontmatter to customize comment ID, which is used to identify comment storage item to use for a page. By default it will be the path of the page, which means if you are deploying the site to multiple places, page with same content across sites will share the same comment data.
Currently, you can choose from Giscus, Waline, Artalk and Twikoo.
Recommended comment services
"Artalk" | "Giscus" | "Twikoo" | "Waline" | "None""None"booleantruestringYou can directly configure serializable options in the plugin options:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Twikoo',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineTwikooConfig function to customize Twikoo:
import { defineClientConfig } from 'vuepress/client'
+import { defineTwikooConfig } from 'vuepress-plugin-comment2/client'
+
+defineTwikooConfig({
+ // Twikoo config
+})
+
+export default defineClientConfig({
+ // ...
+})
+A concise, safe and free static site commenting system, based on Tencent Cloud Development.
npm i -D twikoo
+Apply for MongoDB account
Create a free MongoDB database, the recommended region is AWS / N. Virginia (us-east-1)
Click CONNECT on the Clusters page, follow the steps to allow connections from all IP addresses (Why?), create Database user, and record the database connection string, please change the <password> in the connection string to the database password
Sign up for a Vercel account
Click the button below to deploy Twikoo to Vercel in one click
Go to Settings - Environment Variables, add the environment variable MONGODB_URI, the value is the database connection string in step 3
Go to Overview, click the link under Domains, if the environment configuration is correct, you can see the prompt "Twikoo cloud function is running normally"
Vercel Domains (with https:// prefix, e.g. https://xxx.vercel.app) is your environment ID
Please set provider: "Twikoo" and set envId in the plugin options.
For other configuration items, see Twikoo Config.
stringType: (string | WalineEmojiInfo)[] | false
type WalineEmojiPresets = `http://${string}` | `https://${string}`
+
+interface WalineEmojiInfo {
+ /**
+ * Emoji name show on tab
+ */
+ name: string
+ /**
+ * Current folder link
+ */
+ folder?: string
+ /**
+ * Common prefix of Emoji icons
+ */
+ prefix?: string
+ /**
+ * Type of Emoji icons, will be regarded as file extension
+ */
+ type?: string
+ /**
+ * Emoji icon show on tab
+ */
+ icon: string
+ /**
+ * Emoji image list
+ */
+ items: string[]
+}
+Default: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
Reference:
Details: Emoji settings.
Type: string | boolean
Default: false
Reference:
Details:
Darkmode support
'auto' will display darkmode due to device settings.Type: WalineCommentSorting
Default: 'latest'
Details:
Comment list sorting methods.
Optional values: 'latest', 'oldest', 'hottest'
Type: string[]
Default: ['nick','mail','link']
Details:
Reviewer attributes.
Optional values: 'nick', 'mail', 'link'
Type: string[]
Default: []
Details:
Set required fields, optional values:
[]['nick']['nick','mail']Type: string
Default value: 'enable'
Details:
Login mode status, optional values:
'enable': enable login (default)'disable': Login is disabled, users should fill in information to comment'force': Forced login, users must login to commentType: number | [number, number]
Default: 0
Details:
Comment words limit. When a single number is filled in, it 's the maximum number of comment words. No limit when set to 0.
Type: number
Default: 10
Details:
Number of comments per page.
Type: WalineImageUploader | false
type WalineImageUploader = (image: File) => Promise<string>
+Reference:
Details:
Custom image upload method. The default behavior is to embed images Base 64 encoded, you can set this to false to disable image uploading.
The function should receive an image object and return a Promise that provides the image address.
Type: WalineHighlighter | false
type WalineHighlighter = (code: string, lang: string) => string
+Reference:
Details:
Code highlighting, use hanabi by default. The function passes in original content of code block and language of the code block. You should return a string directly.
You can pass in a code highlighter of your own, or set to false to disable code highlighting.
Type: WalineTexRenderer | false
type WalineTexRenderer = (blockMode: boolean, tex: string) => string
+Reference:
Details:
Customize TeX rendering, the default behavior is to prompt that the preview mode does not support TeX. The function provides two parameters, the first parameter indicates whether it should be rendered in block level, and the second parameter is the string of the TeX content, and return a HTML string as render result.
You can import TeX renderer to provide preview feature. We recommend you to use Katex or MathJax, or you can set to false to disable parsing TeX.
Type: WalineSearchOptions | false
interface WalineSearchImageData extends Record<string, unknown> {
+ /**
+ * Image link
+ */
+ src: string
+
+ /**
+ * Image title
+ *
+ * @description Used for alt attribute of image
+ */
+ title?: string
+
+ /**
+ * Image preview link
+ *
+ * @description For better loading performance, we will use this thumbnail first in the list
+ *
+ * @default src
+ */
+ preview?: string
+}
+
+type WalineSearchResult = WalineSearchImageData[]
+
+interface WalineSearchOptions {
+ /**
+ * Search action
+ */
+ search: (word: string) => Promise<WalineSearchResult>
+
+ /**
+ * Default result when opening list
+ *
+ * @default () => search('')
+ */
+ default?: () => Promise<WalineSearchResult>
+
+ /**
+ * Fetch more action
+ *
+ * @description It will be triggered when the list scrolls to the bottom. If your search service supports paging, you should set this to achieve infinite scrolling
+ *
+ * @default (word) => search(word)
+ */
+ more?: (word: string, currentCount: number) => Promise<WalineSearchResult>
+}
+Details: Customize search features, you can disable search function by setting it to false.
Type: string
Details:
reCAPTCHA V3 is a captcha service provided by Google. You can add reCAPTCHA V3 site key with recaptchaV3Key to enable it.
You should also set environment variable RECAPTCHA_V3_SECRET for server.
Type: boolean | string[]
Default: false
Details:
Add emoji interaction function to the article, set it to true to provide the default emoji, you can also customize the emoji image by setting the emoji url array, and supports a maximum of 8 emojis.
booleantrueType: WalineLocales
interface WalineLocales {
+ [localePath: string]: WalineLocale
+}
+Reference:
Details: Waline locales.
You can directly configure serializable options in the plugin options:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Waline',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineWalineConfig function to customize Waline:
import { defineClientConfig } from 'vuepress/client'
+import { defineWalineConfig } from 'vuepress-plugin-comment2/client'
+
+defineWalineConfig({
+ // Waline config
+})
+
+export default defineClientConfig({
+ // ...
+})
+A safe comment system with backend.
npm i -D @waline/client
+Click Create app button to create a new app and enter a name you like:
Enter the app, then select Settings > App Keys at the left bottom corner. You will see APP ID, APP Key and Master Key of your app. We will use them later
Click the dark button above, it will redirect you to vercel to deploy with waline template.
TIP
If you haven't logged in, we recommend you to sign in with GitHub.
Input your Vercel project name then click Create.
Repo which named you input before will be created and initialized automatically base on waline example template by Vercel.
After one minute or two, vercel should finish the deployment. Click Go to Dashboard button to redirect to your application dashboard.
Click Settings menu on the top, and Environment Variables button on the side to go to environment variables setting page. Then set LEAN_ID, LEAN_KEY and LEAN_MASTER_KEY. The variables' value should be the ones you got in the previous step. APP ID is the value of LEAN_ID, and APP Key to LEAN_KEY, Master Key to LEAN_MASTER_KEY.
To let your environment variables setting active, you need redeploy your application. Click Deployments menu on the top and find the latest deployment at the top of list, click Redeploy button in the right dropdown menu.
If everything is ok, vercel will redirect to Overview page to start redeployment. Wait a moment the STATUS will change to Ready. Now you can click Visit to visit the site. This link is your server address.
Click Settings - Domains to go to domain setting page.
Input domain you want to assign and click Add button.
Add a new CNAME record in your domain service server.
| Type | Name | Value |
|---|---|---|
| CNAME | example | cname.vercel-dns.com |
You can use your own domain to visit waline comment system after go into effect. 🎉
Set provider: "Waline" in the plugin options, and set serverURL as the link obtained in the previous step.
Then, place the <CommentService> component at a suitable location in your site (usually at the bottom of the page), you will be able to see the comment box.
TIP
You can also pass in other options supported by Waline (except el). For details, see Waline Config
<serverURL>/ui/register to register. The first person to register will be set as an administrator.Register markdown custom containers in your VuePress site.
This plugin simplifies the use of markdown-it-container, but also retains its original capabilities.
The Custom Containers of default theme is powered by this plugin.
npm i -D @vuepress/plugin-container@next
+import { containerPlugin } from '@vuepress/plugin-container'
+
+export default {
+ plugins: [
+ containerPlugin({
+ // options
+ }),
+ ],
+}
+::: <type> [info]
+[content]
+:::
+type is required and should be specified via type option.info is optional, and the default value can be specified via defaultInfo in locales option.content can be any valid markdown content.TIP
This plugin can be used multiple times to support different types of containers.
Type: string
Details:
The type of the container.
It will be used as the name param of markdown-it-container.
Type: Record<string, { defaultInfo: string }>
Details:
The default info of the container in different locales.
If this option is not specified, the default info will fallback to the uppercase of the type option.
Example:
export default {
+ plugins: [
+ containerPlugin({
+ type: 'tip',
+ locales: {
+ '/': {
+ defaultInfo: 'TIP',
+ },
+ '/zh/': {
+ defaultInfo: '提示',
+ },
+ },
+ }),
+ ],
+}
+Type: (info: string) => string
Default:
(info: string): string =>
+ `<div class="custom-container ${type}">${info ? `<p class="custom-container-title">${info}</p>` : ''}\n`
+Details:
A function to render the starting tag of the container.
The first param is the info part of container syntax.
This option will not take effect if you don't specify the after option.
Type: (info: string) => string
Default:
(): string => '</div>\n'
+Details:
A function to render the ending tag of the container.
The first param is the info part of container syntax.
This option will not take effect if you don't specify the before option.
type MarkdownItContainerRenderFunction = (
+ tokens: Token[],
+ index: number,
+ options: any,
+ env: MarkdownEnv,
+ self: Renderer,
+) => string
+Details:
The render option of markdown-it-container.
This plugin uses a default render function. If you specify this option, the default render function will be replaced, and the locales, before and after options will be ignored.
Type: (params: string) => boolean
Details:
The validate option of markdown-it-container.
Type: string
Details:
The marker option of markdown-it-container.
This plugin will automatically add a copy button to the top right corner of each code block on PC devices.
The default selector matches @vuepress/theme-default, so you might need to change it when integrating your own theme.
npm i -D @vuepress/plugin-copy-code@next
+import { copyCodePlugin } from '@vuepress/plugin-copy-code'
+
+export default {
+ plugins: [
+ copyCodePlugin({
+ // options
+ }),
+ ],
+}
+Type: string | string[]
Default: '.theme-default-content div[class*="language-"] pre'
Details:
Code block selector
Type: boolean
Default: false
Details:
Whether to display copy button on the mobile device
Type: number
Default: 2000
Details:
Hint display time, setting it to 0 will disable the hint.
Type: number
Default: 800
Details:
The delay of registering copy code buttons, in ms.
If the theme you are using has a switching animation, it is recommended to configure this option to Switch animation duration + 200.
Type: CopyCodePluginLocaleConfig
interface CopyCodePluginLocaleData {
+ /**
+ * Copy text
+ */
+ copy: string
+
+ /**
+ * Copied text
+ */
+ copied: string
+}
+
+interface CopyCodePluginLocaleConfig {
+ [localePath: string]: CopyCodePluginLocaleData
+}
+Required: No
Details:
Locales config for copy code plugin.
Example:
import { copyCodePlugin } from '@vuepress/plugin-copy-code'
+
+export default {
+ locales: {
+ '/': {
+ // this is a supported language
+ lang: 'en-US',
+ },
+ '/xx/': {
+ // the plugin does not support this language
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ copyCodePlugin({
+ locales: {
+ '/': {
+ // Override copy button label text
+ copy: 'Copy Codes from code block',
+ },
+
+ '/xx/': {
+ // Complete locale config for `mm-NN` language here
+ },
+ },
+ }),
+ ],
+}
+You can customize the icon of the copy button via CSS variables:
:root {
+ --code-copy-icon: url("copy-button.svg");
+ --code-copied-icon: url("copied-button.svg");
+ --copy-code-color: #9e9e9e;
+ --copy-code-hover: rgb(0 0 0 / 50%);
+}
+This plugin can automatically append copyright information when visitors copy content from your site, and can also prohibit site copying or selection.
npm i -D @vuepress/plugin-copyright@next
+import { copyrightPlugin } from '@vuepress/plugin-copyright'
+
+export default {
+ plugins: [
+ copyrightPlugin({
+ // options
+ }),
+ ],
+}
+This plugin is disabled globally by default, you can:
copy: true in page frontmatterglobal: true in plugin options to enable it globally, and set copy: false in page frontmatter to disable it.To avoid disturbing visitors, copyright information will be appended only when the copied content length is greater than 100. Set triggerLength in plugin options if you want to change this threshold, or via copy.triggerLength in page frontmatter.
You can set default author and license information via author and license in plugin options.
If your site have different authors and license in different pages, you can set authorGetter and licenseGetter with function (page: Page) => string that takes the current page object as parameter and returns the corresponding information.
The plugin will generate copyright information from author, license, and page link via template by default, and append it when copying. If you think that this is not flexible enough, you can set copyrightGetter option to return a completely customized information with Page object or return null to use the default template.
If you want to prevent users copying long content, you can set maxLength in plugin options to customize this limit, or via copy.maxLength in page frontmatter.
disableCopy in plugin options or copy.disableCopy in page frontmatter, the latter has higher priority.disableSelection in plugin options or copy.disableSelection in page frontmatter. This option has higher priority.stringstring(page: Page) => string | null(page: Page) => string | null(page: Page) => string | nullnumber100number00 means no limit.booleanfalsebooleanfalsebooleanfalsestringExample
If you are deploying same content under https://myblog.com and https://blog.com/username/, you may want to prefer one site as reference link.
canonical to https://myblog.comcanonical to https://blog.com/username/So copyright message triggered on another site also points to your preferred site.
Type: CopyrightPluginLocaleConfig
interface CopyrightPluginLocaleData {
+ /**
+ * Author text
+ *
+ * @description `:author` will be replaced by author
+ */
+ author: string
+
+ /**
+ * License text
+ *
+ * @description `:license` will be replaced by current license
+ */
+ license: string
+
+ /**
+ * Link text
+ *
+ * @description `:link` will be replaced by current page link
+ */
+ link: string
+}
+
+interface CopyrightPluginLocaleConfig {
+ [localePath: string]: CopyrightPluginLocaleData
+}
+Details: Locale config for copyright plugin.
Example:
import { copyrightPlugin } from '@vuepress/plugin-copyright'
+
+export default {
+ locales: {
+ '/': {
+ // this is a supported language
+ lang: 'en-US',
+ },
+ '/xx/': {
+ // the plugin does not support this language
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ copyrightPlugin({
+ locales: {
+ '/': {
+ // Override link text
+ link: 'Original posted at :link',
+ },
+
+ '/xx/': {
+ // Complete locale config for `mm-NN` language here
+ },
+ },
+ }),
+ ],
+}
+number100number00 means no limit.booleanfalsebooleanfalseIntegrate Algolia DocSearch into VuePress, which can provide search to your documentation site.
TIP
Default theme will add DocSearch to the navbar once you configure this plugin correctly.
This plugin may not be used directly in other themes, so you'd better refer to the documentation of your theme for more details.
npm i -D @vuepress/plugin-docsearch@next
+import { docsearchPlugin } from '@vuepress/plugin-docsearch'
+
+export default {
+ plugins: [
+ docsearchPlugin({
+ // options
+ }),
+ ],
+}
+You need to submit the URL of your site to join the DocSearch program. The DocSearch team will send apiKey and indexName to your email once the index is generated. Then you can configure this plugin to enable DocSearch in VuePress.
Alternatively, you can run your own crawler to generate the index, and then use your own appId, apiKey and indexName to configure this plugin.
new Crawler({
+ appId: 'YOUR_APP_ID',
+ apiKey: 'YOUR_API_KEY',
+ rateLimit: 8,
+ startUrls: [
+ // These are urls which algolia start to craw
+ // If your site is divided in to mutiple parts,
+ // you may want to set mutiple entry links
+ 'https://YOUR_WEBSITE_URL/',
+ ],
+ sitemaps: [
+ // if you are using sitemap plugins (e.g.: @vuepress-plugin/sitemap), you may provide one
+ 'https://YOUR_WEBSITE_URL/sitemap.xml',
+ ],
+ ignoreCanonicalTo: false,
+ exclusionPatterns: [
+ // You can use this to stop algolia crawing some paths
+ ],
+ discoveryPatterns: [
+ // These are urls which algolia looking for,
+ 'https://YOUR_WEBSITE_URL/**',
+ ],
+ // Crawler schedule, set it according to your docs update frequency
+ schedule: 'at 02:00 every 1 day',
+ actions: [
+ // you may have mutiple actions, especially when you are deploying mutiple docs under one domain
+ {
+ // name the index with name you like
+ indexName: 'YOUR_INDEX_NAME',
+ // paths where the index take effect
+ pathsToMatch: ['https://YOUR_WEBSITE_URL/**'],
+ // controls how algolia extracts records from your site
+ recordExtractor: ({ $, helpers }) => {
+ // options for @vuepress/theme-default
+ return helpers.docsearch({
+ recordProps: {
+ lvl0: {
+ selectors: '.sidebar-heading.active',
+ defaultValue: 'Documentation',
+ },
+ lvl1: '.theme-default-content h1',
+ lvl2: '.theme-default-content h2',
+ lvl3: '.theme-default-content h3',
+ lvl4: '.theme-default-content h4',
+ lvl5: '.theme-default-content h5',
+ lvl6: '.theme-default-content h6',
+ content: '.theme-default-content p, .theme-default-content li',
+ },
+ indexHeadings: true,
+ })
+ },
+ },
+ ],
+ initialIndexSettings: {
+ // controls how index are initialized
+ // only has effects before index are initialize
+ // you may need to delete your index and recraw after modification
+ YOUR_INDEX_NAME: {
+ attributesForFaceting: ['type', 'lang'],
+ attributesToRetrieve: ['hierarchy', 'content', 'anchor', 'url'],
+ attributesToHighlight: ['hierarchy', 'hierarchy_camel', 'content'],
+ attributesToSnippet: ['content:10'],
+ camelCaseAttributes: ['hierarchy', 'hierarchy_radio', 'content'],
+ searchableAttributes: [
+ 'unordered(hierarchy_radio_camel.lvl0)',
+ 'unordered(hierarchy_radio.lvl0)',
+ 'unordered(hierarchy_radio_camel.lvl1)',
+ 'unordered(hierarchy_radio.lvl1)',
+ 'unordered(hierarchy_radio_camel.lvl2)',
+ 'unordered(hierarchy_radio.lvl2)',
+ 'unordered(hierarchy_radio_camel.lvl3)',
+ 'unordered(hierarchy_radio.lvl3)',
+ 'unordered(hierarchy_radio_camel.lvl4)',
+ 'unordered(hierarchy_radio.lvl4)',
+ 'unordered(hierarchy_radio_camel.lvl5)',
+ 'unordered(hierarchy_radio.lvl5)',
+ 'unordered(hierarchy_radio_camel.lvl6)',
+ 'unordered(hierarchy_radio.lvl6)',
+ 'unordered(hierarchy_camel.lvl0)',
+ 'unordered(hierarchy.lvl0)',
+ 'unordered(hierarchy_camel.lvl1)',
+ 'unordered(hierarchy.lvl1)',
+ 'unordered(hierarchy_camel.lvl2)',
+ 'unordered(hierarchy.lvl2)',
+ 'unordered(hierarchy_camel.lvl3)',
+ 'unordered(hierarchy.lvl3)',
+ 'unordered(hierarchy_camel.lvl4)',
+ 'unordered(hierarchy.lvl4)',
+ 'unordered(hierarchy_camel.lvl5)',
+ 'unordered(hierarchy.lvl5)',
+ 'unordered(hierarchy_camel.lvl6)',
+ 'unordered(hierarchy.lvl6)',
+ 'content',
+ ],
+ distinct: true,
+ attributeForDistinct: 'url',
+ customRanking: [
+ 'desc(weight.pageRank)',
+ 'desc(weight.level)',
+ 'asc(weight.position)',
+ ],
+ ranking: [
+ 'words',
+ 'filters',
+ 'typo',
+ 'attribute',
+ 'proximity',
+ 'exact',
+ 'custom',
+ ],
+ highlightPreTag: '<span class="algolia-docsearch-suggestion--highlight">',
+ highlightPostTag: '</span>',
+ minWordSizefor1Typo: 3,
+ minWordSizefor2Typos: 7,
+ allowTyposOnNumericTokens: false,
+ minProximity: 1,
+ ignorePlurals: true,
+ advancedSyntax: true,
+ attributeCriteriaComputedByMinProximity: true,
+ removeWordsIfNoResults: 'allOptional',
+ },
+ },
+})
+The above recordProps is the configuration used for the default theme. You can modify them according to the theme you are using.
Notice that the initialIndexSettings.YOUR_INDEX_NAME.attributesForFaceting fields must include 'lang' to make this plugin work properly.
TIP
If you are not using default theme, or you meet any problems when using docsearch, you can also check the above example crawler config, and ahead to Algolia Crawler, and edit your config with 'Editor' panel in project sidebar.
Type: string
Required: true
Details:
The apiKey that you received from the DocSearch team, or generated by yourself.
Also see:
Type: string
Required: true
Details:
The indexName that you received from the DocSearch team, or generated by yourself.
Also see:
Type: string
Required: true
Details:
It defines your own application ID.
Also see:
Type: SearchParameters
Details:
Parameters of Algolia Search API.
Also see:
Type: string
Default: 'Search docs'
Details:
The placeholder attribute of the search input.
Also see:
Type: boolean
Default: false
Details:
Whether to disable all personalized features: recent searches, favorite searches, etc.
Also see:
Type: string
Details:
The initial query when the modal opens.
Also see:
Type: Partial<DocSearchTranslations>
Details:
Allow replacing the default text in the DocSearch button or modal.
Also see:
Type: Record<string, DocsearchPluginOptions>
Details:
Options of this plugin in different locales.
All other options of this plugin are acceptable in locale config.
Example:
export default {
+ plugins: [
+ docsearchPlugin({
+ appId: '<APP_ID>',
+ apiKey: '<API_KEY>',
+ indexName: '<INDEX_NAME>',
+ locales: {
+ '/': {
+ placeholder: 'Search Documentation',
+ translations: {
+ button: {
+ buttonText: 'Search Documentation',
+ },
+ },
+ },
+ '/zh/': {
+ placeholder: '搜索文档',
+ translations: {
+ button: {
+ buttonText: '搜索文档',
+ },
+ },
+ },
+ },
+ }),
+ ],
+}
+Type: string
Default: base
Details:
The base path of the search index.
If you are deploying your site to multiple domains, you don't need to submit all of them to DocSearch and generate search index separately. You could choose one of the domains as the index domain, and only submit the index domain to Docsearch for crawling search index. Then, you could reuse the search index across all deployments.
However, if the base of your deployments are different for different domains, you need to set the option to the base of your index domain, so that other deployments could reuse the search index correctly.
Type: boolean
Default: true
Details:
Whether to inject the default styles of DocSearch or not.
If you think the default styles of DocSearch is not compatible with your site, you can try to override the default styles, or set this option to false to totally exclude the default styles.
When this option is disabled, you need to import your own styles for DocSearch. Also notice that all styles customization in Styles section would be unavailable.
You can customize styles via CSS variables that provided by @docsearch/css:
:root {
+ --docsearch-primary-color: rgb(84, 104, 255);
+ --docsearch-text-color: rgb(28, 30, 33);
+ --docsearch-spacing: 12px;
+ --docsearch-icon-stroke-width: 1.4;
+ --docsearch-highlight-color: var(--docsearch-primary-color);
+ --docsearch-muted-color: rgb(150, 159, 175);
+ --docsearch-container-background: rgba(101, 108, 133, 0.8);
+ --docsearch-logo-color: rgba(84, 104, 255);
+
+ /* modal */
+ --docsearch-modal-width: 560px;
+ --docsearch-modal-height: 600px;
+ --docsearch-modal-background: rgb(245, 246, 247);
+ --docsearch-modal-shadow: inset 1px 1px 0 0 rgba(255, 255, 255, 0.5), 0 3px
+ 8px 0 rgba(85, 90, 100, 1);
+
+ /* searchbox */
+ --docsearch-searchbox-height: 56px;
+ --docsearch-searchbox-background: rgb(235, 237, 240);
+ --docsearch-searchbox-focus-background: #fff;
+ --docsearch-searchbox-shadow: inset 0 0 0 2px var(--docsearch-primary-color);
+
+ /* hit */
+ --docsearch-hit-height: 56px;
+ --docsearch-hit-color: rgb(68, 73, 80);
+ --docsearch-hit-active-color: #fff;
+ --docsearch-hit-background: #fff;
+ --docsearch-hit-shadow: 0 1px 3px 0 rgb(212, 217, 225);
+
+ /* key */
+ --docsearch-key-gradient: linear-gradient(
+ -225deg,
+ rgb(213, 219, 228) 0%,
+ rgb(248, 248, 248) 100%
+ );
+ --docsearch-key-shadow: inset 0 -2px 0 0 rgb(205, 205, 230), inset 0 0 1px 1px
+ #fff, 0 1px 2px 1px rgba(30, 35, 90, 0.4);
+
+ /* footer */
+ --docsearch-footer-height: 44px;
+ --docsearch-footer-background: #fff;
+ --docsearch-footer-shadow: 0 -1px 0 0 rgb(224, 227, 232), 0 -3px 6px 0 rgba(69, 98, 155, 0.12);
+}
+Details:
This plugin will register a <Docsearch /> component globally, and you can use it without any props.
Put this component to where you want to place the docsearch button. For example, default theme puts this component to the end of the navbar.
TIP
This component is mainly used for theme development. You don't need to use it directly in most cases.
This plugin will add an icon to the external link in your markdown content, i.e.
This plugin has been integrated into the default theme.
npm i -D @vuepress/plugin-external-link-icon@next
+import { externalLinkIconPlugin } from '@vuepress/plugin-external-link-icon'
+
+export default {
+ plugins: [
+ externalLinkIconPlugin({
+ // options
+ }),
+ ],
+}
+Type: Record<string, { openInNewWindow: string }>
Details:
The a11y text of the external link icon in different locales.
If this option is not specified, it will fallback to default text.
Example:
export default {
+ plugins: [
+ externalLinkIconPlugin({
+ locales: {
+ '/': {
+ openInNewWindow: 'open in new window',
+ },
+ '/zh/': {
+ openInNewWindow: '在新窗口打开',
+ },
+ },
+ }),
+ ],
+}
+Type: boolean
Details:
Whether to append an external link icon to external links in current page.
You can customize the style of the external link icon via CSS variables:
:root {
+ --external-link-icon-color: #aaa;
+}
+Details:
This plugin will register a <ExternalLinkIcon /> component globally, and you can use it without any props.
TIP
This component is mainly used for theme development. You don't need to use it directly in most cases.
The channel plugin option is used to config the feed channel.
stringSiteConfig.titleChannel title
stringoptions.hostname and context.base)Channel address
stringSiteConfig.descriptionChannel description
Type: string
Default:
siteConfig.locales['/'].lang"en-US"The language of the channel
Type: string
Default:
author.name in channel options, and fall back to Copyright by $authorRecommended to set manually: Yes
Channel copyright information
string (must be a valid Date ISOString)Publish date of the Channel
string (must be a valid Date ISOString)Last update time of channel content
numberThe effective time of the content. It's the time to keep the cache after request without making new requests.
stringA picture presenting the channel. A square picture with a size not smaller than 512×512 is recommended.
stringAn icon representing a channel, a square picture, with not less than 128×128 in size, and transparent background color is recommended.
FeedAuthorThe author of the channel.
interface FeedAuthor {
+ /** Author name */
+ name: string
+ /** Author's email */
+ email?: string
+ /** Author's site */
+ url?: string
+ /**
+ * Author's avatar address
+ *
+ * Square, preferably not less than 128×128 with transparent background
+ */
+ avatar?: string
+}
+stringLink to Websub. Websub requires a server backend, which is inconsistent with VuePress, so ignore it if there is no special need.
WebSub
For details, see Websub.
stringThe domain name of the deployment site.
booleanfalseWhether to output Atom syntax files.
booleanfalseWhether output JSON syntax files.
booleanfalseWhether to output RSS syntax files.
stringA large image/icon of the feed, probably used as banner.
stringA small icon of the feed, probably used as favicon.
number100Set the maximum number of items in the feed. After all pages are sorted, the first count items will be intercepted.
If your site has a lot of articles, you may consider this option to reduce feed file size.
(RegExp | string)[] | (tagName: string) => booleanCustom element or component which should be preserved in feed.
By default, all unknown tags will be removed.
Type: (page: Page)=> boolean
Default:
;({ frontmatter, filePathRelative }: Page): boolean =>
+ !(
+ frontmatter.home ||
+ !filePathRelative ||
+ frontmatter.article === false ||
+ frontmatter.feed === false
+ )
+A custom filter function, used to filter feed items.
Type: (pageA: Page, pageB: Page)=> number
Default:
// dateSorter is from @vuepress/helper
+;(pageA: Page, pageB: Page): number =>
+ dateSorter(
+ pageA.data.git?.createdTime
+ ? new Date(pageA.data.git?.createdTime)
+ : pageA.frontmatter.date,
+ pageB.data.git?.createdTime
+ ? new Date(pageB.data.git?.createdTime)
+ : pageB.frontmatter.date,
+ )
+Custom sorter function for feed items.
The default sorting behavior is by file adding time coming from git (needs @vuepress/plugin-git).
TIP
You should enable @vuepress/plugin-git to get the newest created pages as feed items. Otherwise, the feed items will be sorted by the default order of pages in VuePress.
channel option is used to config Feed Channels.
For available options, please see Config → Channel
booleanfalseWhether enabled in devServer.
TIP
For performance reasons, we do not provide hot reload. Reboot your devServer to sync your changes.
string"http://localhost:${port}"Hostname to use in devServer
string"atom.xml"Atom syntax output filename, relative to dest folder.
string@vuepress/plugin-feed/templates/atom.xslAtom xsl template file content.
string"atom.xsl"Atom xsl filename, relative to dest folder.
string"feed.json"JSON syntax output filename, relative to dest folder.
string"rss.xml"RSS syntax output filename, relative to dest folder.
string@vuepress/plugin-feed/templates/rss.xslRSS xsl template file content.
string"rss.xsl"RSS syntax xsl filename, relative to dest folder.
Feed generation controller, see Feed Getter.
The plugin has a built-in getter, only set this if you want full control of feed generation.
Record<string, BaseFeedOptions>You can use it to specific options for each locale.
Any options above are supported except hostname.
You can control each feed item generation by setting page frontmatter.
By default, all articles are added to the feed stream. Set feed: false in frontmatter to remove a page from feed.
stringAutomatically generated by VuePress, defaults to the h1 content of the page
stringDescription of the page
DateDate when the page was published
booleanWhether the page is an article
If this is set to
false, the page will not be included in the final feed.
stringPage copyright information
stringImage used as page cover , should be full link or absolute link.
stringThe title of the feed item
stringDescription of the feed item
stringThe content of the feed item
FeedAuthor[] | FeedAuthorThe author of the feed item
interface FeedAuthor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+FeedContributor[] | FeedContributorContributors to feed item
interface FeedContributor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+stringThe identifier of feed item, used to identify the feed item.
You should ensure every feed has a unique guid.
You can take full control of feed items generation by setting getter in the plugin options.
(page: Page) => stringItem title getter
(page: Page) => stringItem link getter
(page: Page) => string | undefinedItem description getter
TIP
Due to Atom support HTML in summary, so you can return HTML content here if possible, but the content must start with mark html:.
(page: Page) => stringItem content getter
(page: Page) => FeedAuthor[]Item author getter.
The getter should return an empty array when author information is missing.
interface FeedAuthor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => FeedCategory[] | undefinedItem category getter.
interface FeedCategory {
+ /**
+ * Category Name
+ */
+ name: string
+
+ /**
+ * A string that identifies a categorization taxonomy
+ *
+ * @description rss format only
+ */
+ domain?: string
+
+ /**
+ * the categorization scheme via a URI
+ *
+ * @description atom format only
+ */
+ scheme?: string
+}
+(page: Page) => FeedEnclosure | undefinedItem enclosure getter.
interface FeedEnclosure {
+ /**
+ * Enclosure link
+ */
+ url: string
+
+ /**
+ * what its type is
+ *
+ * @description should be a standard MIME Type, rss format only
+ */
+ Type: string
+
+ /**
+ * Size in bytes
+ *
+ * @description rss format only
+ */
+ length?: number
+}
+(page: Page) => Date | undefinedItem release date getter
(page: Page) => DateItem last update date getter
(page: Page) => stringItem Image Getter
Ensure it's returning a full URL
(page: Page) => FeedContributor[]Item Contributor Getter
The getter should return an empty array when contributor information is missing.
interface FeedContributor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => string | undefinedItem copyright getter
The plugin can generate feed files in the following three formats for you:
Please set atom, json or rss to true in the plugin options according to the formats you want to generate.
To correctly generate feed links, you need to set hostname in the plugin options,
When you open the feed file in browser, we magically convert atom and rss feed xml to human readable html via xsl template. Check atom and rss feed of this site as an example!
If you want to preview your feed in devServer, set devServer: true in plugin options. You may also need to set devHostname if you are not using the default http://localhost:{port}.
You can customize the feed channel information by setting the channel option.
We recommend the following settings:
channel.pubDatechannel.ttl (unit: minutes)channel.copyrightchannel.author.For detailed options and their default values, see Channel Config
By default, all articles are added to the feed stream.
You can set feed and other options in page frontmatter to control contents of feed item. See Frontmatter Config for how they are converted.
You can take full control of feed items generation by configuring the getter in the plugin options. For detailed options and their default values, see Configuration → Feed Getter.
The plugin generates separate feeds for each language.
You can provide different settings for different languages via locales in the plugin options.
This plugin will collect git information of your pages, including the created and updated time, the contributors, etc.
The lastUpdated and contributors of default theme is powered by this plugin.
This plugin is mainly used to develop themes. You won't need to use it directly in most cases.
npm i -D @vuepress/plugin-git@next
+import { gitPlugin } from '@vuepress/plugin-git'
+
+export default {
+ plugins: [
+ gitPlugin({
+ // options
+ }),
+ ],
+}
+This plugin requires your project to be inside a Git Repository, so that it can collect information from the commit history.
You should ensure all commits are available when building your site. For example, CI workflows usually clone your repository with --depth 1 to avoid fetching all commits, so you should disable the behavior to make this plugin work properly in CI.
WARNING
This plugin will significantly slow down the speed of data preparation, especially when you have a lot of pages. You can consider disabling this plugin in dev mode to get better development experience.
Type: boolean
Default: true
Details:
Whether to collect page created time or not.
Type: boolean
Default: true
Details:
Whether to collect page updated time or not.
Type: boolean
Default: true
Details:
Whether to collect page contributors or not.
Type: string[]
Details:
An array of relative paths to be included when calculating page data.
Example:
---
+gitInclude:
+ - relative/path/to/file1
+ - relative/path/to/file2
+---
+This plugin will add a git field to page data.
After using this plugin, you can get the collected git information in page data:
import type { GitPluginPageData } from '@vuepress/plugin-git'
+import { usePageData } from 'vuepress/client'
+
+export default {
+ setup() {
+ const page = usePageData<GitPluginPageData>()
+ console.log(page.value.git)
+ },
+}
+Type: number
Details:
Unix timestamp in milliseconds of the first commit of the page.
This attribute would take the minimum of the first commit timestamps of the current page and the files listed in gitInclude.
Type: number
Details:
Unix timestamp in milliseconds of the last commit of the page.
This attribute would take the maximum of the last commit timestamps of the current page and the files listed in gitInclude.
GitContributor[]interface GitContributor {
+ name: string
+ email: string
+ commits: number
+}
+Details:
The contributors information of the page.
This attribute would also include contributors to the files listed in gitInclude.
Integrate Google Analytics into VuePress.
This plugin will import gtag.js for Google Analytics 4.
npm i -D @vuepress/plugin-google-analytics@next
+import { googleAnalyticsPlugin } from '@vuepress/plugin-google-analytics'
+
+export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ // options
+ }),
+ ],
+}
+Google Analytics will automatically collect some events, such as page_view, first_visit, etc.
So if you only want to collect some basic data of your site, you don't need to do anything else except setting the Measurement ID correctly.
After using this plugin, the global gtag() function is available on the window object, and you can use it for custom events reporting.
Type: string
Details:
The Measurement ID of Google Analytics 4, which should start with 'G-'.
You can follow the instructions here to find your Measurement ID. Notice the difference between Google Analytics 4 Measurement ID (i.e. "G-" ID) and Universal Analytics Tracking ID (i.e. "UA-" ID).
Example:
export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ id: 'G-XXXXXXXXXX',
+ }),
+ ],
+}
+Type: boolean
Details:
Set to true to enable sending events to DebugView. See more information on DebugView.
Example:
export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ id: 'G-XXXXXXXXXX',
+ debug: true,
+ }),
+ ],
+}
+This plugin will check dead links in your markdown files.
This plugin has been integrated into the default theme.
npm i -D @vuepress/plugin-links-check@next
+import { linksCheckPlugin } from '@vuepress/plugin-links-check'
+
+export default {
+ plugins: [
+ linksCheckPlugin({
+ // options
+ }),
+ ],
+}
+Type: boolean
Default: true
Details:
Whether check dead links in markdown in devServer
Type: boolean | 'error'
Default: true
Details:
Whether check dead links in markdown in build. If set to 'error', the build will fail if there are dead links.
Type: (string | RegExp)[] | ((link: string, isDev: boolean) => boolean)
Details:
The links that should be excluded from checking. You can use a list of strings or regular expressions, or a function that returns a boolean.
Example:
linksCheckPlugin({
+ exclude: [
+ // exclude links by string
+ '/exclude-link',
+ // exclude links by regex
+ /\/exclude-link-regex/,
+ ],
+
+ // or exclude links by function
+ exclude: (link, isDev) => {
+ if (isDev) {
+ return link.startsWith('/exclude-link-dev')
+ }
+ return link.startsWith('/exclude-link-build')
+ },
+})
+Integrate medium-zoom into VuePress, which can provide the ability to zoom images.
This plugin has been integrated into the default theme.
npm i -D @vuepress/plugin-medium-zoom@next
+import { mediumZoomPlugin } from '@vuepress/plugin-medium-zoom'
+
+export default {
+ plugins: [
+ mediumZoomPlugin({
+ // options
+ }),
+ ],
+}
+Type: string
Default: ':not(a) > img'
Details:
Selector of zoomable images.
By default this plugin will make all images zoomable except those inside <a> tags.
Type: number
Default: 500
Details:
Delay in milliseconds.
After navigating to a new page, this plugin will make images zoomable with a delay.
Type: Object
Details:
Options for medium-zoom.
Also see:
You can customize most of the zoom styles via zoomOptions, while this plugin also provides some CSS variables for additional customization:
:root {
+ --medium-zoom-z-index: 100;
+ --medium-zoom-bg-color: #ffffff;
+ --medium-zoom-opacity: 1;
+}
+Details:
Returns the Zoom instance that used by this plugin, so that you can use the instance methods directly.
This plugin will make images zoomable after navigating to current page. But if you are going to add new images dynamically, you may need this method to make those new images zoomable, too.
This plugin adds an extra refresh method on the Zoom instance, which will call zoom.detach() then zoom.attach() with the selector as the default parameter. It will help you to refresh the zoomable images for current page.
Example:
import { nextTick } from 'vue'
+import { useMediumZoom } from '@vuepress/plugin-medium-zoom/client'
+
+export default {
+ setup() {
+ const zoom = useMediumZoom()
+
+ // ... do something to add new images in current page
+
+ // then you may need to call `refresh` manually to make those new images zoomable
+ nextTick(() => {
+ zoom.refresh()
+ })
+ },
+}
+Integrate nprogress into VuePress, which can provide a progress bar when navigating to another page.
This plugin has been integrated into the default theme.
npm i -D @vuepress/plugin-nprogress@next
+import { nprogressPlugin } from '@vuepress/plugin-nprogress'
+
+export default {
+ plugins: [nprogressPlugin()],
+}
+You can customize the style of the progress bar via CSS variables:
:root {
+ --nprogress-color: #29d;
+ --nprogress-z-index: 1031;
+}
+Provide palette support for your theme.
This plugin is mainly used to develop themes, and has been integrated into the default theme. You won't need to use it directly in most cases.
For theme authors, this plugin will help you to provide styles customization for users.
npm i -D @vuepress/plugin-palette@next
+import { palettePlugin } from '@vuepress/plugin-palette'
+
+export default {
+ plugins: [
+ palettePlugin({
+ // options
+ }),
+ ],
+}
+This plugin will provide a @vuepress/plugin-palette/palette (palette file) and a @vuepress/plugin-palette/style (style file) to be imported in your theme styles.
The palette file is used for defining style variables, so it's likely to be imported at the beginning of your theme styles. For example, users can define CSS variables, SASS variables, LESS variables or Stylus variables in the palette, and then you can use those variables in your theme styles.
The style file is used for overriding the default styles or adding extra styles, so it's likely to be imported at the end of your theme styles.
Use this plugin in your theme, assuming you are using SASS:
export default {
+ // ...
+ plugins: [palettePlugin({ preset: 'sass' })],
+}
+Import the plugin's palette file where your theme needs to use the corresponding variables, such as in the Layout.vue file:
<template>
+ <h1 class="palette-title">Hello, Palette!</h1>
+</template>
+
+<style lang="scss">
+/* import variables from the plugin's palette file */
+@import '@vuepress/plugin-palette/palette';
+
+/* set default value for variables */
+$color: red !default;
+
+/* use variables in your styles */
+.palette-title {
+ color: $color;
+}
+</style>
+Then users can customize variables in .vuepress/styles/palette.scss:
$color: green;
+Import the plugin's style file after your theme's styles, for example, in the clientConfigFile:
// import your theme's style file
+import 'path/to/your/theme/style'
+// import the plugin's style file
+import '@vuepress/plugin-palette/style'
+Then users can add extra styles in .vuepress/styles/index.scss and override the default styles of your theme:
h1 {
+ font-size: 2.5rem;
+}
+Type: 'css' | 'sass' | 'less' | 'stylus'
Default: 'css'
Details:
Set preset for other options.
If you don't need advanced customization of the plugin, it's recommended to only set this option and omit other options.
Type: string
Default:
'.vuepress/styles/palette.css''.vuepress/styles/palette.scss''.vuepress/styles/palette.less''.vuepress/styles/palette.styl'Details:
File path of the user palette file, relative to source directory.
The default value depends on the preset option.
The file is where users define style variables, and it's recommended to keep the default file path as a convention.
Type: string
Default:
'styles/palette.css''styles/palette.scss''styles/palette.less''styles/palette.styl'Details:
File path of the generated palette temp file, relative to temp directory.
The default value depends on the preset option.
You should import the palette file via '@vuepress/plugin-palette/palette' alias, so you don't need to change this option in most cases.
Type: string
Default:
'.vuepress/styles/index.css''.vuepress/styles/index.scss''.vuepress/styles/index.less''.vuepress/styles/index.styl'Details:
File path of the user style file, relative to source directory.
The default value depends on the preset option.
The file is where users override default styles or add extra styles, and it's recommended to keep the default file path as a convention.
Type: string
Default:
'styles/index.css''styles/index.scss''styles/index.less''styles/index.styl'Details:
File path of the generated style temp file, relative to temp directory.
The default value depends on the preset option.
You should import the style file via '@vuepress/plugin-palette/style' alias, so you don't need to change this option in most cases.
Type: (filePath: string) => string
Default:
(filePath) => `@import '${filePath}';\n`(filePath) => `@forward 'file:///${filePath}';\n`(filePath) => `@import '${filePath}';\n`(filePath) => `@require '${filePath}';\n`Details:
Function to generate import code.
The default value depends on the preset option.
This option is used for generating tempPaletteFile and tempStyleFile, and you don't need to change this option in most cases.
This plugin will make the pictures in the body of the page enter the preview mode when clicked.
npm i -D @vuepress/plugin-photo-swipe@next
+import { photoSwipePlugin } from '@vuepress/plugin-photo-swipe'
+
+export default {
+ plugins: [
+ photoSwipePlugin({
+ // options
+ }),
+ ],
+}
+In preview mode, you can:
TIP
string | string[]".theme-default-content :not(a) > img:not([no-view])"booleantrueType: number
Default: 800
Details:
The delay of operating dom, in ms.
TIP
If the theme you are using has a switching animation, it is recommended to configure this option to Switch animation duration + 200.
Type: PhotoSwipePluginLocaleConfig
interface PhotoSwipePluginLocaleData {
+ /**
+ * Close button label text
+ */
+ close: string
+
+ /**
+ * Full screen button label text
+ */
+ fullscreen: string
+
+ /**
+ * Share button label text
+ */
+ share: string
+
+ /**
+ * Zoom button label text
+ */
+ zoom: string
+
+ /**
+ * Previous image button label text
+ */
+ prev: string
+
+ /**
+ * Next image button label text
+ */
+ next: string
+
+ /**
+ * Share button config
+ */
+ buttons: PhotoSwipeDefaultUI.ShareButtonData[]
+}
+
+interface PhotoSwipePluginLocaleConfig {
+ [localePath: string]: PhotoSwipePluginLocaleData
+}
+Details: Locales config for photo-swipe plugin.
Example:
import { defineUserConfig } from 'vuepress'
+import { photoSwipePlugin } from '@vuepress/plugin-photo-swipe'
+
+export default defineUserConfig({
+ locales: {
+ '/': {
+ // this is a supported language
+ lang: 'en-US',
+ },
+ '/xx/': {
+ // the plugin does not support this language
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ photoSwipePlugin({
+ locales: {
+ '/': {
+ // Override share label text
+ share: 'Share with friends',
+ },
+
+ '/xx/': {
+ // Complete locale config for `mm-NN` language here
+ },
+ },
+ }),
+ ],
+})
+string | falseImage selector for the current page, or false to disable photo-swipe in current page.
Options passed to photo-swipe
import { definePhotoSwipeConfig } from '@vuepress/plugin-photo-swipe/client'
+
+definePhotoSwipeConfig({
+ // set photoswipe options here
+})
+
+export default {}
+You can also call photoswipe with apis.
createPhotoSwipe allows you to programmatically view images links with PhotoSwipe:
<script setup lang="ts">
+import { onMounted, onUnmounted } from 'vue';
+import { createPhotoSwipe } from "@vuepress/plugin-photo-swipe/client";
+
+let state: PhotoSwipeState | null = null;
+
+const openPhotoSwipe = (index: number) => {
+ state?.open(index - 1);
+};
+
+onMounted(async () => {
+ // create a new photoswipe instance with image links
+ state= await createPhotoSwipe(
+ [
+ 'https://exmaple.com/image1.png'
+ 'https://exmaple.com/image2.png'
+ 'https://exmaple.com/image3.png'
+ ],
+ {
+ // photoswipe options
+ }
+ );
+});
+
+onUnmounted(() => {
+ state?.destroy()
+})
+</script>
+
+<template>
+ <button v-for="i in 3" @click="openPhotoSwipe(i)">open photo {{ i }}</button>
+</template>
+registerPhotoSwipe allows you to register photoswipe for the given image elements:
<script setup lang="ts">
+import { onMounted, onUnmounted } from 'vue'
+import { registerPhotoSwipe } from '@vuepress/plugin-photo-swipe/client'
+
+let destroy: () => void | null = null
+
+onMounted(async () => {
+ await nextTick()
+
+ const images = Array.from(document.querySelectorAll('img'))
+
+ // create a new photoswipe instance on image elements
+ state = await registerPhotoSwipe(images, {
+ // photoswipe options
+ })
+})
+
+onUnmounted(() => {
+ destroy?.()
+})
+</script>
+You can customize the style via CSS variables:
:root {
+ --photo-swipe-bullet: #fff;
+ --photo-swipe-bullet-active: #3eaf7c;
+}
+This plugin will enable syntax highlighting for markdown code fence with Prism.js.
This plugin has been integrated into the default theme.
Notice that this plugin would only tokenize the code fence without adding styles. When using it with a custom theme, you may need to choose and import Prism.js style theme yourself.
npm i -D @vuepress/plugin-prismjs@next
+import { prismjsPlugin } from '@vuepress/plugin-prismjs'
+
+export default {
+ plugins: [
+ prismjsPlugin({
+ // options
+ }),
+ ],
+}
+Type: string[]
Default: ['markdown', 'jsdoc', 'yaml']
Details:
Languages to preload.
By default, languages will be loaded on demand when parsing markdown files.
However, Prism.js has some potential issues about loading languages dynamically. To avoid them, you can preload languages via this option.
booleanfalseType: AppManifest
Details:
You can fill with an object which will be parsed to manifest.webmanifest.
TIP
Some options have their fallback if you don't set them.
siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.description || siteConfig.locales['/'].description || "A site built with vuepress"siteConfig.locales['/'].lang || "en-US"context.basecontext.base"standalone""#46bd87""#ffffff""portrait-primary"falseReference:
Type: string
Details:
Link of favicon.ico.
WARNING
We recommend you to set favicon for your site.
Type: string
Default: "#46bd87"
Details:
Theme Color of the pwa.
Type: boolean
Default: false
Details:
Whether cache HTML files besides home page and 404 page.
Type: boolean
Default: false
Details:
Whether cache pictures
Type: number
Default: 2048
Details:
Max size allowed to be cached, with KB unit
WARNING
This option has the highest priority, and any files exceeding this value will be excluded.
So if you generate very large HTML or JS files, please consider increasing this value, otherwise your PWA may not work normally in offline mode.
Type: number
Default: 1024
Details: Max picture size allowed to be cached, with KB unit
The value must not be greater than maxSize option
Type: "disabled" | "available" | "hint" | "force"
Default: "available"
Details: Control logic when new content is found.
"disabled": Do nothing even when new service worker is available. After new service work succeeds installing and starts waiting, it will control page and provide new content in next visit.
"available": Only display update popup when the new service worker is available
"hint": Display a hint to let user choose to refresh immediately
This is helpful when you want users to see new docs immediately.
TIP
If users choose to refresh, the current service worker will be unregister, and request will start coming to web. Later the new service worker will start installing and control current page after installed.
"force": unregister current service worker immediately then refresh to get new content
DANGER
Although this ensures users are viewing the latest content, it may affect viewing experiences.
TIP
How docs are updated is controlled by a previous version, so the current option only effect next update from this version.
Special settings for better supporting Safari, ignoring these options are safe.
string"black" | "white""black"stringSpecial settings for Microsoft tiles, ignoring these options are safe.
stringstringthemeColorstring"PwaFoundPopup"string"PwaReadyPopup"booleanfalseDetails:
Options passed to workbox-build, for details, see Workbox documentation
Type: PwaPluginLocaleConfig
interface PwaPluginLocaleData {
+ /**
+ * Install button text
+ */
+ install: string
+
+ /**
+ * iOS install hint text
+ */
+ iOSInstall: string
+
+ /**
+ * Cancel button text
+ */
+ cancel: string
+
+ /**
+ * Close button text
+ */
+ close: string
+
+ /**
+ * Previous image text
+ */
+ prevImage: string
+
+ /**
+ * Next image text
+ */
+ nextImage: string
+
+ /**
+ * Install explain text
+ */
+ explain: string
+
+ /**
+ * Description label text
+ */
+ desc: string
+
+ /**
+ * Feature label text
+ */
+ feature: string
+
+ /**
+ * Update hint text
+ */
+ hint: string
+
+ /**
+ * Update available text
+ */
+ update: string
+}
+
+interface PwaPluginLocaleConfig {
+ [localePath: string]: PwaPluginLocaleData
+}
+Details: Locales config for pwa plugin.
Details:
Returns the event emitter of this plugin.
You can add listener function to events that provided by register-service-worker.
Example:
import { usePwaEvent } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+ event.on('ready', (registration) => {
+ console.log('Service worker is active.')
+ })
+ },
+}
+Details:
Force update the page when an update is found.
Example:
import { forceUpdate } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ forceUpdate()
+ })
+ },
+}
+Details:
Register service worker manually.
Parameters:
| Parameter | Type | Description |
|---|---|---|
| serviceWorkerPath | string | Path of the service worker |
| hooks | object | Hooks of service worker |
| showStatus | boolean | Log service worker status in console |
interface Hooks {
+ registrationOptions?: RegistrationOptions
+ ready?: (registration: ServiceWorkerRegistration) => void
+ registered?: (registration: ServiceWorkerRegistration) => void
+ cached?: (registration: ServiceWorkerRegistration) => void
+ updated?: (registration: ServiceWorkerRegistration) => void
+ updatefound?: (registration: ServiceWorkerRegistration) => void
+ offline?: () => void
+ error?: (error: Error) => void
+}
+import { registerSW } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ registerSW('/service-worker.js', {
+ ready(registration) {
+ console.log('Service worker is active.')
+ },
+ })
+ })
+ },
+}
+Details:
Activate the waiting service worker.
Parameters:
| Parameter | Type | Description |
|---|---|---|
| registration | ServiceWorkerRegistration | The registration of the service worker you want activate |
import { usePwaEvent, skipWaiting } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+
+ event.on('updated', (registration) => {
+ console.log('The waiting service worker is available.')
+ // activate the waiting service worker
+ skipWaiting(registration)
+ })
+ },
+}
+Details:
Unregister service worker manually.
Example:
import { unregisterSW } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ unregisterSW()
+ })
+ },
+}
+You can customize the style via CSS variables:
:root {
+ --pwa-z-index: 10;
+ --pwa-color: #2c3e50;
+ --pwa-bg-color: #ffffff;
+ --pwa-border-color: #3eaf7c;
+ --pwa-shadow-color: rgb(0 0 0 / 15%);
+ --pwa-btn-text-color: #ffffff;
+ --pwa-btn-bg-color: #3eaf7c;
+ --pwa-btn-hover-bg-color: #4abf8a;
+ --pwa-content-color: #333;
+ --pwa-content-light-color: #666;
+}
+Make your VuePress site a Progressive Web Application (PWA)[1].
This plugin uses workbox-build to generate service worker file, and uses register-service-worker to register service worker.
WARNING
If you enabled this plugin once and you want to disable it, you might need `@vuepress/plugin-remove-pwa to remove the existing service worker.
A PWA uses a Service Worker [2] (SW for short) to cache and proxy site content.
To make your website fully compliant with PWA, a Web app manifests [3] file is needed, and your pwa should satisfy the installability [4] specification.
You can set manifest option to customize the manifest file, or provide a manifest.webmanifest or manifest.json in public folder. The former has higher priority.
The plugin will automatically generate manifest.webmanifest for you and add manifest link declaration in each page, while you should still at least set a valid icon through manifest.icons or other icon related options in the PWA plugin.
WARNING
The installability [4:1] specification requires at least one valid icon to be declared in the manifest.
So if you do not configure manifest.icons, visitors can only enjoy the offline accessibility brought by the Service Worker cache, while cannot install your site as a PWA.
Besides the plugin does not process anything in the manifest by default, but outputs them as-is. This means that if you plan to deploy to a subdirectory, you should append the URL prefix to manifest Urls yourself. If everything you need is all under base directory, you can set appendBase: true in plugin options to let the plugin append base to any links in manifest.
To better control what the Service Worker can pre-cache, the plugin provides related options for cache control.
By default, the plugin will pre-cache all js css files, and only homepage and 404 html are cached. The plugin will also cache font files (woff, woff2, eot, ttf, otf) and SVG icons.
If your site has only a few important images, and want them displayed in offline mode, you can cache site images by setting cacheImage: true .
We recognize images by file extension. Any files ending with .png, .jpg, .jpeg, .gif, .bmp, .webp will be regarded as images.
If you have small sites, and would like to make document fully offline available, you can set cacheHTML to true to cache all HTML files.
Why only home and 404 page been cached by default?
Though VuePress generates HTML files through SSG[5] for all pages, these files are mainly used for SEO[6] and allow you to directly configure the backend without SPA[7] Visit any link.
VuePress is essentially an SPA. This means that you only need to cache the home page and enter from the home page to access all pages normally. Therefore, not caching other HTML by default can effectively reduce the cache size (40% smaller in size) and speed up the SW update speed.
But this also has the disadvantage. If the user enters the site directly from a non-home page, the HTML file for the first page still needs to be loaded from the internet. Also, in offline environment, users can only enter through the homepage and then navigate to the corresponding page by themselves. If they directly access a link, an inaccessible prompt will appear.
To prevent large files from being included in the pre-cache list, any files > 2 MB or images > 1 MB will be omitted. You can customize these limits with maxSize and maxImageSize options (in KB unit).
We provide the update option to control how users receive updates.
The default value of the update option is "available", which means that when new content available, the new SW will be installed and its resources will be fetched silently in the background. A pop-up window appears once the new SW is ready, and users can choose whether to refresh immediately to view new content. This means users are reading old content before a new SW is ready.
If your project is still in building stage, and you want to alert the user that he may be reading outdated content, you can set this to "hint". This allows users to be notified that new content has been published within seconds after visiting docs. But the negative effect of this is that if the user chooses to update before the new SW is ready, he will need to get all the resources of the page from the internet before the new SW installs and controls the page.
If your docs are stable, or you're hosting a blog and don't care much about users receiving the latest version right away, you can set this to "disabled", which means that the new SW will be installed completely silently in the background and start waiting, when all pages controlled by old SW are all closed, the new SW will start to take control and provide users with new content during next visit. This setting can prevent users from being disturbed during the visit.
To speed up user access under weak or no network conditions through SW, but also want users to always access new content, you can set this option to "force". This means any old SW will be removed as soon as a new SW is detected, and all pages are refreshed to ensure the user is browsing the latest content. The biggest disadvantage is that all users will experience unexpected sudden refresh within seconds after reentering an updated site.
When new content is detected (new SW detected), a update found popup appears; and when the new content is ready, an update ready popup appears.
If you are not satisfied with the default popup content, you can use your own component. Import PwaFoundPopup or PwaReadyPopup from @vuepress/plugin-pwa/client and use its slot to customize the popup content, then pass the component path to foundComponent or readyComponent option:
<script setup lang="ts">
+import { PwaFoundPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaFoundPopup v-slot="{ found, refresh }">
+ <div v-if="found">
+ New content is found.
+ <button @click="refresh">Refresh</button>
+ </div>
+ </PwaFoundPopup>
+</template>
+<script setup lang="ts">
+import { PwaReadyPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaReadyPopup v-slot="{ isReady, reload }">
+ <div v-if="isReady">
+ New content is ready.
+ <button @click="reload">Apply</button>
+ </div>
+ </PwaReadyPopup>
+</template>
+The plugin also provides other PWA-related options, such as Microsoft tile icon and color settings, Apple icon and so on. If you are an advanced user, you can also set generateSwConfig to configure workbox-build. Check Plugin options for more details.
For more details, please see:
PWA introduction
PWA, full name Progressive Web app. PWA standard is stipulated by W3C.
It allows sites to install the site as an App on supported platform through a browser that supports this feature.
See https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps for details. ↩︎
Service Worker Introduction
The Service Worker will get and cache all the files registered in it during the registration process.
After the registration complete, the Service Worker is activated, and starts to proxy and control all your requests.
Whenever you want to initiate an access request through the browser, the Service Worker will check whether it exists in its own cache list, if it exists, it will directly return the cached result, otherwise it will call its own fetch method to get it. You can use a custom fetch method to fully control the result of the request for resources in the web page, such as providing a fallback web page when offline.
Every time the user reopens the site, the Service Worker will request to the link when it was registered. If a new version of Service Worker is detected, it will update itself and start caching the list of resources registered in the new Service Worker . After the content update is successfully obtained, the Service Worker will trigger the update event. The user can be notified through this event, for example, a pop-up window will be displayed in the lower right corner, prompting the user that new content is available and allowing the user to trigger an update.
Manifest File
The manifest file uses the JSON format and is responsible for declaring various information of the PWA, such as name, description, icon, and shortcut actions.
In order for your site to be registered as a PWA, you need to meet the basic specifications of the manifest to make the browser consider the site as an installable PWA and allow users to install it.
TIP
For Manifest standards and specifications, please see MDN Web app manifests and W3C Manifest.
Installable
To let the site be registered as a PWA, the site needs to successfully register a valid service worker by itself, and declare a valid manifest file with its link in meta tag.
The manifest file should contain at least name (or short_name) icons start_url.
On safari, the maximum cache size of the service worker is 50 MB. ↩︎ ↩︎
SSG: Static Site Generation, ↩︎
SEO: Search Engine Optimization. ↩︎
SPA: Single Page Application, most of them only have the homepage, and use history mode to handle routing instead of actually navigating between pages. ↩︎
This plugin will generate word count and estimated reading time for each page.
npm i -D @vuepress/plugin-reading-time@next
+import { readingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default {
+ plugins: [
+ readingTimePlugin({
+ // options
+ }),
+ ],
+}
+The plugin will inject reading time information into the readingTime of the page data, where:
readingTime.minutes: estimated reading time (minutes) numberreadingTime.words: word count numberFor any page, you can get estimated reading time and word count from page.data.readingTime:
page.data.readingTime // { minutes: 3.2, words: 934 }
+You can access it for further processing in the extendsPage lifecycle and other lifecycle:
export default {
+ // ...
+ extendsPage: (page) => {
+ page.data.readingTime // { minutes: 3.2, words: 934 }
+ },
+
+ onInitialized: (app) => {
+ app.pages.map((page) => {
+ page.data.readingTime // { minutes: 3.2, words: 934 }
+ })
+ },
+}
+You can import useReadingTimeData and useReadingTimeLocale from @vuepress/plugin-reading-time/client to get the reading time data and locale data of the current page:
<script setup lang="ts">
+import {
+ useReadingTimeData,
+ useReadingTimeLocale,
+} from '@vuepress/plugin-reading-time/client'
+
+const readingTimeData = useReadingTimeData() // { minutes: 1.1, words: 100 }
+const readingTimeLocale = useReadingTimeLocale() // { time: "1 minute", words: "100 words" }
+</script>
+number300Type: ReadingTimePluginLocaleConfig
interface ReadingTimePluginLocaleData {
+ /**
+ * Word template, `$word` will be automatically replaced by actual words
+ */
+ word: string
+
+ /**
+ * Text for less than one minute
+ */
+ less1Minute: string
+
+ /**
+ * Time template
+ */
+ time: string
+}
+
+interface ReadingTimePluginLocaleConfig {
+ [localePath: string]: ReadingTimePluginLocaleData
+}
+Required: No
Details:
Locales config for reading-time plugin.
You can import and use these APIs from @vuepress/plugin-reading-time/client:
These APIs won't throw even you disable the plugin.
interface ReadingTime {
+ /** Expect reading time in minute unit */
+ minutes: number
+ /** Words count of content */
+ words: number
+}
+
+const useReadingTimeData: () => ComputedRef<ReadingTime | null>
+null is returned when the plugin is disabled.
interface ReadingTimeLocale {
+ /** Expect reading time text in locale */
+ time: string
+ /** Word count text in locale */
+ words: string
+}
+
+const useReadingTimeLocale: () => ComputedRef<ReadingTimeLocale>
+This plugin is targeting plugin and theme developers mostly, so we provide a "Use API":
import { useReadingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default (options) => (app) => {
+ useReadingTimePlugin(app, {
+ // your options
+ })
+
+ return {
+ name: 'vuepress-plugin-xxx', // or vuepress-theme-xxx
+ }
+}
+Why you should use "Use API"
useReadingTimePlugin automatically detects if the plugin is registered and avoid registering multiple times.extendsPage lifecycle, then @vuepress/plugin-reading-time must be called before your theme or plugin, otherwise you will get undefined for page.data.readingTime. The useReadingTimePlugin ensures that @vuepress/plugin-reading-time is called before your theme or plugin.We also provides a removeReadingTimePlugin api to remove the plugin.You can use this to ensure your call take effect or clear the plugin:
import { useReadingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default (options) => (app) => {
+ // this removes any existing reading time plugin at this time
+ removeReadingTimePlugin(app)
+
+ // so this will take effect even if there is a reading time plugin registered before
+ useReadingTimePlugin(app, {
+ // your options
+ })
+
+ return {
+ name: 'vuepress-plugin-xxx', // or vuepress-theme-xxx
+ }
+}
+This plugin can automatically handle redirects for your site.
npm i -D @vuepress/plugin-redirect@next
+import { redirectPlugin } from '@vuepress/plugin-redirect'
+
+export default {
+ plugins: [
+ redirectPlugin({
+ // options
+ }),
+ ],
+}
+If you change the address of an existing page, you can use the redirectFrom option in Frontmatter to redirect to the address of this page, which ensures that users are redirected to the new address when they visit the old link.
If you need to redirect an existing page to a new page, you can use the redirectTo option in Frontmatter to set the address to redirect to. This way the page will redirect to the new address when accessed.
You can also set config with a redirect map in plugin options, see config for more details.
The plugin can automatically redirect non-multilingual links to the multilingual pages the user needs based on the user's language preference.
To achieve this, you need to leave the default language directory (/) blank and set autoLocale: true in plugin options. The plugin will automatically redirect to the correct page according to the user's language.
I.E.: you need to set the following directory structure:
.
+├── en
+│ ├── ...
+│ ├── page.md
+│ └── README.md
+├── zh
+│ ├── ...
+│ ├── page.md
+│ └── README.md
+└── other_languages
+ ├── ...
+ ├── page.md
+ └── README.md
+And set locales in theme options with:
export default {
+ locales: {
+ '/en/': {
+ lang: 'en-US',
+ // ...
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ // ...
+ },
+ // other languages
+ },
+ // ...
+}
+So when a user accesses / or /page.html, they are automatically redirected to /en/ /en/page.html and /en/ /en/page.html based on current browser language.
Customizing fallback behavior
Sometimes, users may add more than one language to the system settings. By default, when a site supports a preferred language, but the page not exists for the preferred language, the plugin attempts to match the alternate language set by the user.
If you don't need to fall back to the user's alternate language, but directly match the user's preferred language, set localeFallback: false in the plugin options.
Customizing missing behavior
Sometimes, when a user visits a page, the document does not yet contain the language version the user needs (a common case is that the current page has not been localized in the relevant language), so the plugin needs to perform a default action, which you can customize by defaultBehavior in the plugin options:
"defaultLocale": Redirect to default language or first available language page (default behavior)"homepage": redirect to the home page in the current language (only available if the document contains the user's language)"404": Redirect to page 404 in current language (only available if the document contains the user's language)Customizing default locale path
You can customize the default locale path by setting defaultLocale in the plugin options. By default, the plugin uses the first locale key in locales as the default language.
The plugin supports automatically switching the link to the multilingual page that the user needs according to the user's language preference when opening a multilingual document. In order to achieve this, you need to set switchLocale in the plugin options, which can be the following two values:
direct: switch directly to the user language preference page without askingmodal: When the user's language preference is different from the current page language, show a modal asking whether to switch languageBy default, the plugin generates a locale setting by reading locale path and lang from the site's locales option. Sometimes, you may want multiple languages to hit the same path, in which case you should set localeConfig in plugin options.
For example, you might want all English users to match to /en/ and Chinese Traditional users to /zh/, then you can set:
redirect({
+ localeConfig: {
+ '/en/': ['en-US', 'en-UK', 'en'],
+ '/zh/': ['zh-CN', 'zh-TW', 'zh'],
+ },
+})
+Sometimes you may change base or use new domain for your site, so you may want the original site automatically redirects to the new one.
To solve this, the plugin provide vp-redirect cli.
Usage:
+ $ vp-redirect generate [sourceDir]
+
+Options:
+ --hostname <hostname> Hostname to redirect to (E.g.: https://new.example.com/) (default: /)
+ -c, --config <config> Set path to config file
+ -o, --output <output> Set the output directory (default: .vuepress/redirect)
+ --cache <cache> Set the directory of the cache files
+ -t, --temp <temp> Set the directory of the temporary files
+ --clean-cache Clean the cache files before generation
+ --clean-temp Clean the temporary files before generation
+ -h, --help Display this message
+You need to pass in VuePress project source dir and also set the hostname option. The redirect helper cli will initialize your VuePress project to get pages, then generate and output the redirect html files to the output directory.
By default, the plugin will output to .vuepress/redirect directory under source directory. And you should upload it to your original site to provide redirection.
Type: Record<string, string> | ((app: App) => Record<string, string>)
Details: Redirect map.
Example:
When base is set to /base/:
/base/foo.html to /base/bar.html/base/baz.html to https://example.com/qux.html.redirect({
+ config: {
+ '/foo.html': '/bar.html',
+ '/baz.html': 'https://example.com/qux.html',
+ },
+})
+Redirect post folder to posts folder:
redirect({
+ hostname: 'https://example.com',
+ config: (app) =>
+ Object.fromEntries(
+ app.pages
+ .filter(({ path }) => path.startsWith('/posts/'))
+ .map(({ path }) => [path.replace(/^\/posts\//, '/post/'), path]),
+ ),
+})
+booleanfalseType: "direct" | "modal" | false
Default: false
Details:
Whether switch to a new locale based on user preference.
"direct": redirect to the new locale directly without asking"modal": show a modal to let user choose whether to switch to the new localeType: Record<string, string | string[]>
Details: Locale language config
booleantrue"defaultLocale" | "homepage" | "404""defaultLocale"stringstring | string[]stringYou can customize the style of the redirect popup via CSS variables:
:root {
+ --redirect-z-index: 1499;
+ --redirect-bg-color: #fff;
+ --redirect-bg-color-light: #f3f4f5;
+ --redirect-bg-color-lighter: #eeeeee;
+ --redirect-text-color: #2c3e50;
+ --redirect-primary-color: #3eaf7c;
+ --redirect-primary-hover-color: #4abf8a;
+ --redirect-primary-text-color: #fff;
+}
+Register Vue components from component files or directory automatically.
npm i -D @vuepress/plugin-register-components@next
+import { registerComponentsPlugin } from '@vuepress/plugin-register-components'
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ // options
+ }),
+ ],
+}
+Type: Record<string, string>
Default: {}
Details:
An object that defines name of components and their corresponding file path.
The key will be used as the component name, and the value is an absolute path of the component file.
If the component name from this option conflicts with componentsDir option, this option will have a higher priority.
Example:
import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ components: {
+ FooBar: path.resolve(__dirname, './components/FooBar.vue'),
+ },
+ }),
+ ],
+}
+Type: string | null
Default: null
Details:
Absolute path to the components directory.
Files in this directory which are matched with componentsPatterns will be registered as Vue components automatically.
Example:
import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ componentsDir: path.resolve(__dirname, './components'),
+ }),
+ ],
+}
+Components directory:
components
+├─ FooBar.vue
+└─ Baz.vue
+Components will be registered like this:
import { defineAsyncComponent } from 'vue'
+
+app.component(
+ 'FooBar',
+ defineAsyncComponent(() => import('/path/to/components/FooBar.vue')),
+)
+
+app.component(
+ 'Baz',
+ defineAsyncComponent(() => import('/path/to/components/Baz.vue')),
+)
+Type: string[]
Default: ['**/*.vue']
Details:
Patterns to match component files using globby.
The patterns are relative to componentsDir.
Type: (filename: string) => string
Default: (filename) => path.trimExt(filename.replace(/\/|\\/g, '-'))
Details:
A function to get component name from the filename.
It will only take effect on the files in the componentsDir which are matched with the componentsPatterns.
Notice that the filename is a filepath relative to componentsDir.
This plugin removes any related service worker from your VuePress site, so that users can still get updates if you removed any PWA plugin after enabling it.
Why this plugin is needed if you used PWA plugin once?
PWA plugins like @vuepress/plugin-pwa register service worker to your site, which will cache your site and make it available offline.
However, if you remove pwa plugin, the old service worker will still be there, but they can never get an update because they can never found a new service worker to update to. So users will stay with the old version of your site.
To solve this problem:
npm i -D @vuepress/plugin-remove-pwa@next
+import { removePwaPlugin } from '@vuepress/plugin-remove-pwa'
+
+export default {
+ plugins: [
+ removePwaPlugin({
+ // options
+ }),
+ ],
+}
+string'workbox'string'service-worker.js'This plugin will set direction to rtl on configured locales.
npm i -D @vuepress/plugin-rtl@next
+import { rtlPlugin } from '@vuepress/plugin-rtl'
+
+export default {
+ plugins: [
+ rtlPlugin({
+ // options
+ locales: ['/ar/'],
+ }),
+ ],
+}
+string[]['/']Type: SelectorOptions
interface SelectorOptions {
+ [element: string]: {
+ [attrs: string]: string
+ }
+}
+Default: { 'html': { dir: 'rtl' } }
Details:
Selector to enable rtl.
The default settings mean that the dir attribute of the html element will be set to rtl in rtl locales.
Provide local search to your documentation site.
TIP
Default theme will add search box to the navbar once you configure this plugin correctly.
This plugin may not be used directly in other themes, so you'd better refer to the documentation of your theme for more details.
npm i -D @vuepress/plugin-search@next
+import { searchPlugin } from '@vuepress/plugin-search'
+
+export default {
+ plugins: [
+ searchPlugin({
+ // options
+ }),
+ ],
+}
+This plugin will generate search index from your pages locally, and load the search index file when users enter your site. In other words, this is a lightweight built-in search which does not require any external requests.
However, when your site has a large number of pages, the size of search index file would be very large, which could slow down the page loading speed. In this case, we recommend you to use a more professional solution - docsearch.
Type: Record<string, { placeholder: string }>
Details:
The text of the search box in different locales.
If this option is not specified, it will fallback to default text.
Example:
export default {
+ plugins: [
+ searchPlugin({
+ locales: {
+ '/': {
+ placeholder: 'Search',
+ },
+ '/zh/': {
+ placeholder: '搜索',
+ },
+ },
+ }),
+ ],
+}
+(string | HotKeyOptions)[]export interface HotKeyOptions {
+ /**
+ * Value of `event.key` to trigger the hot key
+ */
+ key: string;
+ /**
+ * Whether to press `event.altKey` at the same time
+ *
+ * @default false
+ */
+ alt?: boolean;
+ /**
+ * Whether to press `event.ctrlKey` at the same time
+ *
+ * @default false
+ */
+ ctrl?: boolean;
+ /**
+ * Whether to press `event.shiftKey` at the same time
+ *
+ * @default false
+ */
+ shift?: boolean;
+}
+Default: ['s', '/']
Details:
Specify the event.key of the hotkeys.
When hotkeys are pressed, the search box input will be focused.
Set to an empty array to disable hotkeys.
Type: number
Default: 5
Details:
Specify the maximum number of search results.
Type: (page: Page) => boolean
Default: () => true
Details:
A function to determine whether a page should be included in the search index.
true to include the page.false to exclude the page.Example:
export default {
+ plugins: [
+ searchPlugin({
+ // exclude the homepage
+ isSearchable: (page) => page.path !== '/',
+ }),
+ ],
+}
+Type: (page: Page) => string[]
Default: () => []
Details:
A function to add extra fields to the search index of a page.
By default, this plugin will use page title and headers as the search index. This option could help you to add more searchable fields.
Example:
export default {
+ plugins: [
+ searchPlugin({
+ // allow searching the `tags` frontmatter
+ getExtraFields: (page) => page.frontmatter.tags ?? [],
+ }),
+ ],
+}
+You can customize the style of the search box via CSS variables:
:root {
+ --search-bg-color: #ffffff;
+ --search-accent-color: #3eaf7c;
+ --search-text-color: #2c3e50;
+ --search-border-color: #eaecef;
+ --search-item-text-color: #5d81a5;
+ --search-item-focus-bg-color: #f3f4f5;
+ --search-input-width: 8rem;
+ --search-result-width: 20rem;
+}
+Details:
This plugin will register a <SearchBox /> component globally, and you can use it without any props.
Put this component to where you want to place the search box. For example, default theme puts this component to the end of the navbar.
TIP
This component is mainly used for theme development. You don't need to use it directly in most cases.
Type: string
Required: Yes
Details:
Deploy hostname.
Type: Author
type AuthorName = string
+
+interface AuthorInfo {
+ /**
+ * Author name
+ */
+ name: string
+
+ /**
+ * Author website
+ */
+ url?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+}
+
+type Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]
+Required: No
Details:
Default author.
Type: boolean
Default: true
Details:
Whether generate description automatically
Type: string | ((page: Page) => string | null)
Details:
Canonical link
Type: string
Details:
Fallback Image link when no image are found
Type: string
Details:
The age rating of the content, the format is [int]+, such as "13+".
Type: string
Details:
Fill in your twitter username.
Type: (page: Page) => boolean
Details:
Use this option to judge whether the page is an article.
Type:
function ogp(
+ /** OGP info inferred by plugin */
+ ogp: SeoContent,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+Required: No
Details:
Custom OPG Generator.
You can use this options to edit OGP tags.
Type:
function jsonLd(
+ /** JSON-LD Object inferred by plugin */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+Required: No
Details:
Custom JSON-LD Generator.
You can use this options to edit JSON-LD properties.
Type:
function customHead(
+ /** Head tag config */
+ head: HeadConfig[],
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+Required: No
Details:
You can use this options to edit tags injected to <head>.
This plugin will make your site fully support Open Content Protocol OGP and JSON-LD 1.1 to enhance the SEO of the site.
The plugin works out of the box. Without any config, it will extract information from the page content as much as possible to complete the necessary tags required by OGP and JSON-LD.
By default, the plugin will read the site config and page frontmatter to automatically generate tags as much as possible. Such as site name, page title, page type, writing date, last update date, and article tags are all automatically generated.
The following are the <meta> tags and their values that will be injected into <head> by default:
The following are the <meta> tags and their value injected into <head> by default to satisfy OGP:
| Meta Name | Value |
|---|---|
og:url | options.hostname + path |
og:site_name | siteConfig.title |
og:title | page.title |
og:description | page.frontmatter.description || auto generated (when autoDescription is true in plugin options) |
og:type | "article" |
og:image | page.frontmatter.banner || page.frontmatter.cover || first image in page || fallbackImage in plugin options |
og:updated_time | page.git.updatedTime |
og:locale | page.lang |
og:locale:alternate | Other languages in siteData.locales |
twitter:card | "summary_large_image" (only available when image found) |
twitter:image:alt | page.title (only available when image found) |
article:author | page.frontmatter.author || options.author |
article:tag | page.frontmatter.tags || page.frontmatter.tag |
article:published_time | page.frontmatter.date || page.git.createdTime |
article:modified_time | page.git.updatedTime |
| Property Name | Value |
|---|---|
@context | "https://schema.org" |
@type | "NewsArticle" |
headline | page.title |
image | image in page || options.hostname + page.frontmatter.image || siteFavIcon in plugin options |
datePublished | page.frontmatter.date || page.git.createdTime |
dateModified | page.git.updatedTime |
author | page.frontmatter.author || options.author |
You can configure the head option in the page's frontmatter to add specific tags to the page <head> to enhance SEO. For example:
---
+head:
+ - - meta
+ - name: keywords
+ content: SEO plugin
+---
+Will automatically inject <meta name="keywords" content="SEO plugin" />.
The plugin also gives you full control over the build logic.
For most pages, there are basically only two types: articles and website, so the plugin provides the isArticle option to allow you to provide logic for identifying articles.
The option accepts a function in the format (page: Page) => boolean, by default all non-home pages generated from Markdown files are treated as articles.
TIP
If a page does fit into the "unpopular" genre like books, music, etc., you can handle them by setting the three options below.
You can use the plugin options ogp to pass in a function to modify the default OGP object to your needs and return it.
function ogp(
+ /** OGP Object inferred by plugin */
+ ogp: SeoContent,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+For detailed parameter structure, see Config.
For example, if you are using a third-party theme and set a banner in frontmatter for each article according to the theme requirements, then you can pass in the following ogp:
seoPlugin({
+ ogp: (ogp, page) => ({
+ ...ogp,
+ 'og:image': page.frontmatter.banner || ogp['og:image'],
+ }),
+})
+Like OGP, you can use the plugin options jsonLd to pass in a function to modify the default JSON-LD object to your needs and return it.
function jsonLd(
+ /** JSON-LD Object inferred by plugin */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+If you are deploying your content to different sites, or same content under different URLs, you may need to set canonical option to provide a "Canonical Link" for your page. You can either set a string which will be appended before page route link, or adding a custom function (page: Page) => string | null to return a canonical link if necessary.
Example
If your sites are deployed under docs directory in example.com, but available in:
http://example.com/docs/xxxhttps://example.com/docs/xxxhttp://www.example.com/docs/xxxhttps://www.example.com/docs/xxx (primary)To let search engine results always be the primary choice, you may need to set canonical to https://www.example.com/docs/, so that search engine will know that the fourth URL is preferred to be indexed.
Sometimes you may need to fit other protocols or provide the corresponding SEO tags in the format provided by other search engines. In this case, you can use the customHead option, whose type is:
function customHead(
+ /** Head tag config */
+ head: HeadConfig[],
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+You should modify the head array in this function directly.
Search engine optimization (SEO) is the process of improving the quality and quantity of site traffic to a site or a web page from search engines. SEO targets unpaid traffic (known as "natural" or "organic" results) rather than direct traffic or paid traffic. Unpaid traffic may originate from different kinds of searches, including image search, video search, academic search, news search, and industry-specific vertical search engines.
As an internet marketing strategy, SEO considers how search engines work, the computer-programmed algorithms that dictate search engine behavior, what people search for, the actual search terms or keywords typed into search engines, and which search engines are preferred by their targeted audience. SEO is performed because a site will receive more visitors from a search engine when sites rank higher on the search engine results page (SERP). These visitors can then potentially be converted into customers.
Open Content Protocol OGP (Open Graph Protocol)
This plugin perfectly supports this protocol and will automatically generate <meta> tags that conform to the protocol.
This plugin will generate "NewsArticle" scheme for article pages.
RDFa mainly marks HTML structure. This is what the plugin cannot support. uses this feature to pass Google's rich media structure test. You can consider using it.
Schema definition site for structural markup
You can use Google Rich Media Structure Test Tool to test this site.
This plugin will enable syntax highlighting for markdown code fence with Shiki.
TIP
Shiki is the syntax highlighter being used by VSCode. It has higher fidelity, but it could be slower than Prism.js, especially when you have a lot of code blocks.
You could consider disabling this plugin in dev mode to get better development experience.
npm i -D @vuepress/plugin-shiki@next
+import { shikiPlugin } from '@vuepress/plugin-shiki'
+
+export default {
+ plugins: [
+ shikiPlugin({
+ // options
+ langs: ['ts', 'json', 'vue', 'md', 'bash', 'diff'],
+ }),
+ ],
+}
+Type: ShikiLang[]
Details:
Languages of code blocks to be parsed by Shiki.
This option will be forwarded to getHighlighter() method of Shiki.
You'd better provide the languages list you are using explicitly, otherwise Shiki will load all languages and can affect performance.
Also see:
Type: ShikiTheme
Default: 'nord'
Details:
Theme of Shiki.
This option will be forwarded to codeToHtml() method of Shiki.
Also see:
Type: Record<'dark' | 'light', ShikiTheme>
Details:
Dark / Light Dual themes of Shiki.
This option will be forwarded to codeToHtml() method of Shiki.
Also see:
Type: ShikiTransformer[]
Details:
Transformers of Shiki.
This option will be forwarded to codeToHtml() method of Shiki.
Also see:
Type: string
Required: Yes
Details:
The domain name where the current site is deployed, the plugin needs this option to work.
Type: string[]
Details:
Extra link to be included.
If you have some links not including in VuePress Router (normally in public directory or generated by other tools directly), you may need this option.
Example: ['/about.html', '/api/']
Type: string[]
Default: ['/404.html']
Details:
Urls excluding from sitemap, starting with absolute path.
By default, all the urls generated by VuePress (excluding 404 page) will be added into sitemap.
Type: boolean
Default: false
Details:
Whether enabled in devServer.
TIP
For performance reasons, we do not provide hot reload. Reboot your devServer to sync your changes.
Type: string
Default: "http://localhost:${port}"
Details:
Hostname to use in devServer
Type: string
Default value: "sitemap.xml"
Details:
The output filename, relative to output directory.
Type: string
Default value: "sitemap.xsl"
Details:
Output xsl filename, relative to dest folder.
Type: string
Default value: "@vuepress/plugin-sitemap/templates/sitemap.xsl"
Details:
XSL content used as template.
Type: "always" | "hourly" | "daily" | "weekly" |"monthly" | "yearly" | "never"
Default value: "daily"
Details:
Page default update frequency, will be overridden by sitemap.changefreq in Frontmatter.
Type: number
Default: 0.5
Details:
Page priority, from 0 to 1.
Type: (page: Page, app: App) => string
Details:
Last modify time getter. By default, the plugin will use the timestamp generated by git plugin.
Type: SitemapFrontmatterOptions | false
Details:
false means exclude the page from sitemap.
Type: "always" | "hourly" | "daily" | "weekly" | "monthly" | "yearly" | "never"
Default: "daily"
Details:
Page default update frequency. This will override changefreq in Plugin Options.
Type: number
Default: 0.5
Details:
Page priority, range from 0 to 1.
This plugin will automatically generate a Sitemap for your site. To let this plugin work, you need to pass the deployed domain name to the hostname option of the plugin. If you want to preview in devServer, set devServer options.
The plugin will automatically generate the last update time of the page based on the Git timestamp of the page, and will also declare the alternative links of the page in other languages according to the locales' config.
By default, all site links except 404 page will be added to the Sitemap.
To add other pages to the Sitemap outside the VuePress project page, please turn them into an array and pass to the extraUrls plugin option.
If you don't want certain pages to appear in the sitemap, you can turn their paths into an array and pass to the excludePaths plugin option, or set sitemap to false in the frontmatter of the corresponding page.
You can also control the output link through the sitemapFilename option of the plugin, the link is relative to output directory. By default, the plugin will use sitemap.xml.
The default update cycle of the page is daily (every day). To modify the entire page cycle, please set changefreq in the plugin options. You can also set sitemap.changefreq in the frontmatter of the page. Note that page has a higher priority.
The legal frequencies are:
"always""hourly""daily""weekly""monthly""yearly""never"You can set priority in the plugin to provide a default value. At the same time you can set the priority for each page through sitemap.priority in frontmatter. Acceptable values are floating point numbers from 0 to 1.
You can use option modifyTimeGetter to return a time in ISO string format, which is generated by the Git plugin by default.
The following is an example based on the last modification time of a file.
// Based on file last modified time
+({
+ modifyTimeGetter: (page, app) =>
+ fs.statSync(app.dir.source(page.filePathRelative)).mtime.toISOString();
+})
+Sitemaps provide SEO (Search Engine Optimization):
A sitemap enhances SEO by making all pages findable.
Most search engines only follow a limited number of links within a page, so when the site is very large, a sitemap becomes essential to make everything on the site accessible to search engines and visitors.
Sitemaps is a protocol for site administrators to publish pages that can be crawled on a site to search engine spiders. The content of sitemap files must follow the definition in XML format. Each URL can contain the update period and last update time, the priority of the URL across the site. This allows search engines to crawl site content better and more efficiently.
Together with robots.txt
Sitemap is basically used by search engines, when using this plugin, you'd better ensure that you have a valid robots.txt in the .vuepress/public directory to allow search engines spiders to visit your site. The simplest robots.txt is as follows (allow all search engines to access all paths)
User-agent: *
+
+Allow: /
+Provide client data for your theme, with VuePress i18n support.
This plugin is mainly used to develop themes, and has been integrated into the default theme. You won't need to use it directly in most cases.
For theme authors, this plugin will help you to use the same i18n mechanism as VuePress and the default theme. But if you don't want to provide i18n support, or you want to implement in your own way, you don't need this plugin.
npm i -D @vuepress/plugin-theme-data@next
+import { themeDataPlugin } from '@vuepress/plugin-theme-data'
+
+export default {
+ plugins: [
+ themeDataPlugin({
+ // options
+ }),
+ ],
+}
+Type: ThemeData
Default: {}
Details:
The theme data object that you want to use in client side.
You can provide theme data in Node side via this option, and use it in client side via useThemeData and useThemeLocaleData.
Example:
export default {
+ plugins: [
+ themeDataPlugin({
+ themeData: {
+ foo: 'foo',
+ locales: {
+ '/zh/': {
+ foo: 'zh-foo',
+ },
+ },
+ },
+ }),
+ ],
+}
+WARNING
The theme data object will be processed by JSON.stringify() before forwarding to client side, so you should ensure that you are providing a JSON-friendly object.
Details:
Returns the theme data ref object.
The value is provided by themeData option.
Example:
import { useThemeData } from '@vuepress/plugin-theme-data/client'
+import type { ThemeData } from '@vuepress/plugin-theme-data/client'
+
+type MyThemeData = ThemeData<{
+ foo: string
+}>
+
+export default {
+ setup() {
+ const themeData = useThemeData<MyThemeData>()
+ console.log(themeData.value)
+ },
+}
+Details:
Returns the theme data ref object in current locale.
The properties of current locale has been merged into the root-level properties.
Example:
import { useThemeLocaleData } from '@vuepress/plugin-theme-data/client'
+import type { ThemeData } from '@vuepress/plugin-theme-data/client'
+
+type MyThemeData = ThemeData<{
+ foo: string
+}>
+
+export default {
+ setup() {
+ const themeLocaleData = useThemeLocaleData<MyThemeData>()
+ console.log(themeLocaleData.value)
+ },
+}
+This plugin will provide a table-of-contents (TOC) component.
npm i -D @vuepress/plugin-toc@next
+import { tocPlugin } from '@vuepress/plugin-toc'
+
+export default {
+ plugins: [
+ tocPlugin({
+ // options
+ }),
+ ],
+}
+Similar to the Table of Contents Markdown Syntax, the TOC component that provided by this plugin could be used in your markdown content directly:
<!-- markdown toc syntax -->
+
+[[toc]]
+
+<!-- vue toc component -->
+<Toc />
+Both of them can be pre-rendered correctly in build mode. However, there are some differences between them.
The markdown syntax [[toc]] could only be used in markdown files. It is parsed by markdown-it, and the generated TOC is static content.
The component <Toc/> could be used in both markdown files and vue files. It is loaded by vue, and the generated TOC is a vue component.
This plugin could work together with @vuepress/plugin-active-header-links by setting the headerLinkSelector to match the linkClass option. When the page scroll to a certain header anchor, this corresponding link will be added linkActiveClass class name.
Therefore, this plugin is more useful for theme developers.
Type: string
Default: 'Toc'
Details:
Specify the name of the TOC component.
Type: Partial<TocPropsOptions>
Default: {}
Details:
Override the default values of the component options prop.
The TOC component also accepts props for customization.
<template>
+ <Toc :headers="headers" :options="options" />
+</template>
+PageHeader[]interface PageHeader {
+ level: number
+ title: string
+ slug: string
+ children: PageHeader[]
+}
+Details:
Specify the headers array to render.
If this prop is not specified, the headers of current page will be used.
Partial<TocPropsOptions>interface TocPropsOptions {
+ containerTag: string
+ containerClass: string
+ listClass: string
+ itemClass: string
+ linkTag: 'a' | 'RouterLink' | 'RouteLink'
+ linkClass: string
+ linkActiveClass: string
+ linkChildrenActiveClass: string
+}
+Default:
Following default values can be overridden by defaultPropsOptions.
const defaultOptions = {
+ containerTag: 'nav',
+ containerClass: 'vuepress-toc',
+ listClass: 'vuepress-toc-list',
+ itemClass: 'vuepress-toc-item',
+ linkTag: 'RouteLink',
+ linkClass: 'vuepress-toc-link',
+ linkActiveClass: 'active',
+ linkChildrenActiveClass: 'active',
+}
+Details:
Customize the TOC component.
If the containerTag is set to an empty string '', the <nav> container will be removed totally.
Example:
The rendered TOC component with default options looks like:
<template>
+ <!-- container -->
+ <nav class="vuepress-toc">
+ <!-- list -->
+ <ul class="vuepress-toc-list">
+ <!-- item -->
+ <li class="vuepress-toc-item">
+ <!-- link -->
+ <RouteLink class="vuepress-toc-link" to="#foo">Foo</RouteLink>
+ </li>
+ <!-- item with children -->
+ <li class="vuepress-toc-item">
+ <!-- link (children active) -->
+ <RouteLink class="vuepress-toc-link active" to="#bar">Bar</RouteLink>
+ <!-- list (children) -->
+ <ul class="vuepress-toc-list">
+ <!-- item -->
+ <li class="vuepress-toc-item">
+ <!-- link (active) -->
+ <RouteLink class="vuepress-toc-link active" to="#bar-child">
+ Bar Child
+ </RouteLink>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </nav>
+</template>
+Type: string
Details:
+Hostname to be deployed, e.g.: https://example.com
Type: { [path: string]: Partial<DefaultThemeLocaleData> }
Default: {}
Details:
+Specify locales for i18n support.
+All the options inside the Locale Config section can be used in locales.
+This option will only take effect in default theme, so don't confuse with locales in Site Config.
Also see:
+Config of this section can be used as normal config, and can also be used in the locales option.
+Type: 'auto' | 'light' | 'dark'
Default: 'auto'
Details:
+Default color mode.
+If set to 'auto', the initial color mode will be automatically set according to prefers-color-scheme.
Also see:
+ +Type: boolean
Default: true
Details:
+Enable color mode switching or not.
+If set to true, a button to switch color mode will be displayed in the navbar.
Also see:
+ +Type: string
Default: /
Details:
+Specify the path of the homepage.
+This will be used for:
+Type: false | (NavbarItem | NavbarGroup | string)[]
Default: []
Details:
+Configuration of navbar.
+Set to false to disable navbar.
To configure the navbar items, you can set it to a navbar array, each item of which could be a NavbarItem object, a NavbarGroup object, or a string:
NavbarItem object should have a text field and a link field, could have an optional activeMatch field.NavbarGroup object should have a text field and a children field. The children field should be a navbar array, too.NavbarItem object, using the page title as text, and the page route path as link.Example 1:
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // NavbarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ },
+ // NavbarGroup
+ {
+ text: 'Group',
+ children: ['/group/foo.md', '/group/bar.md'],
+ },
+ // string - page file path
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // nested group - max depth is 2
+ {
+ text: 'Group',
+ children: [
+ {
+ text: 'SubGroup',
+ children: ['/group/sub/foo.md', '/group/sub/bar.md'],
+ },
+ ],
+ },
+ // control when should the item be active
+ {
+ text: 'Group 2',
+ children: [
+ {
+ text: 'Always active',
+ link: '/',
+ // this item will always be active
+ activeMatch: '/',
+ },
+ {
+ text: 'Active on /foo/',
+ link: '/not-foo/',
+ // this item will be active when current route path starts with /foo/
+ // regular expression is supported
+ activeMatch: '^/foo/',
+ },
+ ],
+ },
+ ],
+ }),
+}
+Type: null | string
Details:
+Specify the url of logo image.
+The logo image will be displayed at the left end of the navbar.
+Set to null to disable logo.
Example:
+export default {
+ theme: defaultTheme({
+ // public file path
+ logo: '/hero.png',
+ // url
+ logo: 'https://vuejs.org/images/logo.png',
+ }),
+}
+Type: null | string
Details:
+Specify the url of logo image to be used in dark mode.
+You can make use of this option if you want to use different logo config in dark mode.
+Set to null to disable logo in dark mode. Omit this option to use logo in dark mode.
Also see:
+ +Type: null | string
Details:
+Specify the alt text of the logo image.
+If not specified, defaults to be the same as the site title.
+Type: string
Details:
+Specify the repository url of your project.
+This will be used as the link of the repository link, which will be displayed as the last item of the navbar.
+export default {
+ theme: defaultTheme({
+ // If you set it in the form of `organization/repository`
+ // we will take it as a GitHub repo
+ repo: 'vuejs/vuepress',
+ // You can also set it to a URL directly
+ repo: 'https://gitlab.com/foo/bar',
+ }),
+}
+Type: false | 'auto' | SidebarConfigArray | SidebarConfigObject
Default: 'auto'
Details:
+Configuration of sidebar.
+You can override this global option via sidebar frontmatter in your pages.
+Set to false to disable sidebar.
If you set it to 'auto', the sidebar will be automatically generated from the page headers.
To configure the sidebar items manually, you can set this option to a sidebar array, each item of which could be a SidebarItem object or a string:
SidebarItem object should have a text field, could have an optional link field, an optional children field and an optional collapsible field. The children field should be a sidebar array. The collapsible field controls whether the item is collapsible.SidebarItem object, whose text is the page title, link is the page route path, and children is automatically generated from the page headers.If you want to set different sidebar for different sub paths, you can set this option to a sidebar object:
+'heading' to automatically generate the sidebar from the page headers for just the corresponding path.Example 1:
+export default {
+ theme: defaultTheme({
+ // sidebar array
+ // all pages will use the same sidebar
+ sidebar: [
+ // SidebarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ children: [
+ // SidebarItem
+ {
+ text: 'github',
+ link: 'https://github.com',
+ children: [],
+ },
+ // string - page file path
+ '/foo/bar.md',
+ ],
+ },
+ // string - page file path
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // sidebar object
+ // pages under different sub paths will use different sidebar
+ sidebar: {
+ '/guide/': [
+ {
+ text: 'Guide',
+ children: ['/guide/introduction.md', '/guide/getting-started.md'],
+ },
+ ],
+ '/reference/': 'heading',
+ },
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // collapsible sidebar
+ sidebar: {
+ '/reference/': [
+ {
+ text: 'VuePress Reference',
+ collapsible: true,
+ children: ['/reference/cli.md', '/reference/config.md'],
+ },
+ {
+ text: 'Bundlers Reference',
+ collapsible: true,
+ children: [
+ '/reference/bundler/vite.md',
+ '/reference/bundler/webpack.md',
+ ],
+ },
+ ],
+ },
+ }),
+}
+Type: number
Default: 2
Details:
+Set the maximum depth of the sidebar children which are automatically generated from the page headers.
+0 to disable all levels of headers.1 to include <h2> headers.2 to include <h2> and <h3> headers.The max value depends on which levels of headers you have extracted via markdown.headers.level.
+The default value of markdown.headers.level is [2, 3], so the default max value of sidebarDepth is 2.
You can override this global option via sidebarDepth frontmatter in your pages.
+Type: boolean
Default: true
Details:
+Enable the edit this page link or not.
+You can override this global option via editLink frontmatter in your pages.
+Type: string
Details:
+Specify the pattern of the edit this page link.
+This will be used for generating the edit this page link.
+If you don't set this option, the pattern will be inferred from the docsRepo option. But if your documentation repository is not hosted on a common platform, for example, GitHub, GitLab, Bitbucket, Gitee, etc., you have to set this option explicitly to make the edit this page link work.
+Usage:
+| Pattern | Description | +|
+Default theme's Layout provides some slots:
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottomWith the help of them, you can add or replace content easily. Here comes an example to introduce how to extend default theme with layout slots.
+Firstly, create a client config file .vuepress/client.ts:
import { defineClientConfig } from 'vuepress/client'
+import Layout from './layouts/Layout.vue'
+
+export default defineClientConfig({
+ layouts: {
+ Layout,
+ },
+})
+Next, create the .vuepress/layouts/Layout.vue, and make use of the slots that provided by the Layout of default theme:
<script setup>
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+</script>
+
+<template>
+ <ParentLayout>
+ <template #page-bottom>
+ <div class="my-footer">This is my custom page footer</div>
+ </template>
+ </ParentLayout>
+</template>
+
+<style lang="css">
+.my-footer {
+ text-align: center;
+}
+</style>
+Then the default Layout layout has been overridden by your own local layout, which will add a custom footer to every normal pages in default theme (excluding homepage):
The layout slots are useful, but sometimes you might find it's not flexible enough. Default theme also provides the ability to replace a single component.
+Default theme has registered alias for every non-global components with a @theme prefix. For example, the alias of HomeFooter.vue is @theme/HomeFooter.vue.
Then, if you want to replace the HomeFooter.vue component, just override the alias in your config file .vuepress/config.ts:
import { defaultTheme } from '@vuepress/theme-default'
+import { getDirname, path } from 'vuepress/utils'
+import { defineUserConfig } from 'vuepress'
+
+const __dirname = getDirname(import.meta.url)
+
+export default defineUserConfig({
+ theme: defaultTheme(),
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+})
+Instead of extending the default theme directly in .vuepress/config.ts and .vuepress/client.ts, you can also develop your own theme extending the default theme:
import { defaultTheme, type DefaultThemeOptions } from '@vuepress/theme-default'
+import type { Theme } from 'vuepress/core'
+import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export const childTheme = (options: DefaultThemeOptions): Theme => {
+ return {
+ name: 'vuepress-theme-child',
+ extends: defaultTheme(options),
+
+ // override layouts in child theme's client config file
+ // notice that you would build ts to js before publishing to npm,
+ // so this should be the path to the js file
+ clientConfigFile: path.resolve(__dirname, './client.js'),
+
+ // override component alias
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+ }
+}
+If your site is served in a different language besides English, you should set these options per locale to provide translations.
+Type: string
Details:
+Specify the repository label of your project.
+This will be used as the text of the repository link, which will be displayed as the last item of the navbar.
+If you don't set this option explicitly, it will be automatically inferred from the repo option.
+Type: string
Details:
+Specify the text of the select language menu.
+The select language menu will appear next to the repository button in the navbar when you set multiple locales in your site config.
+Type: string
Details:
+Specify the aria-label attribute of the select language menu.
This is mainly for a11y purpose.
+Type: string
Details:
+Specify the name of the language of a locale.
+This option will only take effect inside the locales of your theme config. It will be used as the language name of the locale, which will be displayed in the select language menu.
+Example:
+export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+ theme: defaultTheme({
+ locales: {
+ '/': {
+ selectLanguageName: 'English',
+ },
+ '/zh/': {
+ selectLanguageName: '简体中文',
+ },
+ },
+ }),
+}
+Type: null | string
Details:
+aria-label value for main navigation in navbar.
Type: null | string
Details:
+aria-label value for next/previous page navigation.
Type: string
Default: 'Edit this page'
Details:
+Specify the text of the edit this page link.
+Type: string
Default: 'Last Updated'
Details:
+Specify the text of the last updated timestamp label.
+Type: string
Default: 'Contributors'
Details:
+Specify the text of the contributors list label.
+Type: string
Default: 'TIP'
Details:
+Specify the default title of the tip custom containers.
+Type: string
Default: 'WARNING'
Details:
+Specify the default title of the warning custom containers.
+Type: string
Default: 'DANGER'
Details:
+Specify the default title of the danger custom containers.
+Type: string[]
Default: ['Not Found']
Details:
+Specify the messages of the 404 page.
+The message will be randomly picked from the array when users enter the 404 page.
+Type: string
Default: 'Back to home'
Details:
+Specify the text of the back to home link in the 404 page.
+Type: string
Default: 'open in new window'
Details:
+Specify the sr-only text of the ExternalLinkIcon.
This is mainly for a11y purpose.
+Also see:
+ +Type: string
Default: 'toggle color mode'
Details:
+Title text for the color mode toggle button.
+This is mainly for a11y purpose.
+Also see:
+ +Type: string
Default: 'toggle sidebar'
Details:
+Title text for sidebar toggle button.
+This is mainly for a11y purpose.
+Type: string
Default: 'Prev'
Details:
+Text for the previous page navigation button.
+Type: string
Default: 'Next'
Details:
+Text for the next page navigation button.
+themePlugins.
+Default theme is using some plugins by default. You can disable a plugin if you really do not want to use it. Make sure you understand what the plugin is for before disabling it.
+import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ themePlugins: {
+ // customize theme plugins here
+ },
+ }),
+}
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-active-header-links or not.
+Type: BackToTopPluginOptions | boolean
Default: true
Details:
+Enable @vuepress/plugin-back-to-top or not.
+Object value is supported as plugin options.
+Type: Record<ContainerType, boolean>
Details:
+Enable custom containers that powered by @vuepress/plugin-container or not.
+ContainerType type is:
tipwarningdangerdetailscodeGroupcodeGroupItemAlso see:
+ +Type: CopyCodePluginOptions | boolean
Default: true
Details:
+Enable @vuepress/plugin-copy-code or not.
+Object value is supported as plugin options.
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-external-link-icon or not.
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-git or not.
+Type: LinksCheckPluginOptions | boolean
Default: true
Details:
+Enable @vuepress/plugin-links-check or not.
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-medium-zoom or not.
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-nprogress or not.
+Type: boolean
Default: true
Details:
+Enable @vuepress/plugin-prismjs or not.
+Type: SeoPluginOptions | boolean
Default: true
Details:
+Enable @vuepress/plugin-seo or not.
+Object value is supported as plugin options.
+Type: SitemapPluginOptions | boolean
Default: true
Details:
+Enable @vuepress/plugin-sitemap or not.
+Object value is supported as plugin options.
+Type: (page: Page) => Record<string, unknown>
Required: No
+Reference:
+ +Details:
+Function getting article info.
+Article info will be injected in route meta so that they will be available later in client composables.
+Type: (page: Page) => boolean
Default: (page) => Boolean(page.filePathRelative) && !page.frontmatter.home
Reference:
+ +Details:
+Page filter, determine whether a page should be included.
+By default, all the pages generated from Markdown files but not homepage will be included as articles.
+BlogCategoryOptions[]BlogTypeOptions[](name: string) => string(name) => name.replace(/ _/g, '-').replace(/[:?*|\\/<>]/g, "").toLowerCase()booleantruestring<!-- more -->Type: number
Default: 300
Reference:
+ +Details:
+Length of excerpt when auto generating.
+TIP
+Excerpt length will be the minimal possible length reaching this value.
+You can set it to 0 to disable auto excerpt generation.
Type: (page: Page) => boolean
Default: filter option
Reference:
+ +Details:
+Page filter, determine whether the plugin should generate excerpt for it.
+TIP
+You should use this to skip pages that you don't need to generate excerpt for. E.g.: If users set excerpt or description in frontmatter, you may want to use them directly.
Type: (tagName: string) => boolean
Default: () => false
Reference:
+ +Details:
+Tags which is considered as custom elements.
+This is used to determine whether a tag is a custom element since all unknown tags are removed in excerpt.
+Type: string
Default: "_blog"
Details:
+Key used when injecting info to route meta.
+TIP
+Setting to an empty key will inject to route meta directly instead of a field.
+Type: boolean
Default: Whether using --debug flag
Details:
+Whether enable hotReload in devServer.
+To theme developers
+It's disabled by default because it does have performance impact in sites with a lot of categories and types. And it can slow down hotReload speed when editing Markdown.
+If users are adding or organizing your categories or tags, you may tell them to enable this, for the rest it's better to keep it disabled.
+Also, you can try to detect number of pages in users project and decide whether to enable it.
+Blog category config should be an array, while each item is controlling a "category" rule.
+interface BlogCategoryOptions {
+ /**
+ * Unique category name
+ */
+ key: string
+
+ /**
+ * Function getting category from page
+ */
+ getter: (page: Page) => string[]
+
+ /**
+ * A custom function to sort the pages
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * Path pattern of page to be registered
+ *
+ * @description `:key` will be replaced by the "slugify" result of the original key
+ *
+ * @default `/:key/`
+ */
+ path?: string
+
+ /**
+ * Page layout name
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Frontmatter
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+
+ /**
+ * Item page path pattern or custom function to be registered
+ *
+ * @description When filling in a string, `:key` and `:name` will be replaced by the "slugify" result of the original key and name
+ *
+ * @default `/:key/:name/`
+ */
+ itemPath?: string | ((name: string) => string)
+
+ /**
+ * Item page layout name
+ *
+ * @default 'Layout'
+ */
+ itemLayout?: string
+
+ /**
+ * Items Frontmatter
+ */
+ itemFrontmatter?: (name: string, localePath: string) => Record<string, string>
+}
+Blog type config should be an array, while each item is controlling a "type" rule.
+interface BlogTypeOptions {
+ /**
+ * Unique type name
+ */
+ key: string
+
+ /**
+ * A filter function to determine whether a page should be the type
+ */
+ filter: (page: Page) => boolean
+
+ /**
+ * A custom function to sort the pages
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * Page path to be registered
+ *
+ * @default '/:key/'
+ */
+ path?: string
+
+ /**
+ * Layout name
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Frontmatter
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+}
+You can import the following API from @vuepress/plugin-blog/client.
Blog category
+const useBlogCategory: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogCategoryData<T>>
+Argument key should be the category unique key.
If no key is passed, the plugin will try to use the key in current path.
+Blog category
+const useBlogType: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogTypeData<T>>
+Argument key should be the type unique key.
If no key is passed, the plugin will try to use the key in current path.
+Returning values are:
+interface Article<T extends Record<string, unknown> = Record<string, unknown>> {
+ /** Article path */
+ path: string
+ /** Article info */
+ info: T
+}
+
+interface BlogCategoryData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** Category path */
+ path: string
+
+ /**
+ * Only available when current route matches an item path
+ */
+ currentItems?: Article<T>[]
+
+ /** Category map */
+ map: {
+ /** Unique key under current category */
+ [key: string]: {
+ /** Category path of the key */
+ path: string
+ /** Category items of the key */
+ items: Article<T>[]
+ }
+ }
+}
+
+interface BlogTypeData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** Type path */
+ path: string
+
+ /** Items under current type */
+ items: Article<T>[]
+}
+@vuepress/plugin-blog, you can easily bring blog feature into your theme.
+The plugin filters all pages using filter option to drop pages you don't want.
By default, all pages generating from Markdown files but not homepage are considered as articles.
+You can fully customize pages to collect through option filter, which accepts a function (page: Page) => boolean.
You should set getInfo option with a function accepting Page as argument and returning an object containing the info you want.
The plugin will collect all the info you want and write them to routeMeta field of each page, so you will be able to get this information through Composition API later.
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ filter: ({ filePathRelative, frontmatter }) => {
+ // drop those pages which is NOT generated from file
+ if (!filePathRelative) return false
+
+ // drop those pages in `archives` directory
+ if (filePathRelative.startsWith('archives/')) return false
+
+ // drop those pages which do not use default layout
+ if (frontmatter.home || frontmatter.layout) return false
+
+ return true
+ },
+
+ getInfo: ({ frontmatter, git = {}, data = {} }) => {
+ // getting page info
+ const info: Record<string, any> = {
+ author: frontmatter.author || '',
+ categories: frontmatter.categories || [],
+ date: frontmatter.date || git.createdTime || null,
+ tags: frontmatter.tags || [],
+ excerpt: data.excerpt || '',
+ }
+
+ return info
+ },
+ }),
+ // other plugins ...
+ ],
+}
+Basically, you would want 2 types of collection in your blog:
+Category:
+"Category" means grouping articles with their labels.
+For example, each article may have their "categories" and "tags".
+Type:
+"Type" means identifying articles with conditions.
+For example, you may want to describe some of your articles as diary.
+After understanding description of these 2 types, you can set category and type options, each accepts an array, and each element represents a configuration.
Let's start with 2 examples here.
+Imagine you are setting tags for each articles with tag field in page frontmatter. You want a tag mapping page in /tag/ with TagMap layout, and group each tag list with tagName in /tag/tagName with TagList layout, you probably need a configuration like this:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // other options ...
+ category: [
+ {
+ key: 'tag',
+ getter: ({ frontmatter }) => frontmatter.tag || [],
+ path: '/tag/',
+ layout: 'TagMap',
+ frontmatter: () => ({ title: 'Tag page' }),
+ itemPath: '/tag/:name/',
+ itemLayout: 'TagList',
+ itemFrontmatter: (name) => ({ title: `Tag ${name}` }),
+ },
+ ],
+ }),
+ // other plugins ...
+ ],
+}
+Also, you may want to star some of your articles, and display them to visitors. When you are setting star: true in frontmatter to mark them, you probably need a configuration like this to display them in /star/ path with StarList layout:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // other options ...
+ type: [
+ {
+ key: 'star',
+ filter: ({ frontmatter }) => frontmatter.star,
+ path: '/star/',
+ layout: 'StarList',
+ frontmatter: () => ({ title: 'Star page' }),
+ },
+ ],
+ }),
+ // other plugins ...
+ ],
+}
+See, setting these 2 types is easy. For full options, please see Category Config and Type Config.
+When generating each page, the plugin will set following information under frontmatter.blog:
interface BlogFrontmatterOptions {
+ /** Current type of the page */
+ type: 'category' | 'type'
+ /** Unique key under current category or tag */
+ key: string
+ /**
+ * Current category name
+ *
+ * @description Only available in category item page
+ */
+ name?: string
+}
+So you can invoke useBlogCategory() and useBlogType() directly, and the result will be the category or type bind to current route.
Also, you can pass key you want as argument, then you will get information bind to that key.
So with node side settings above, you can get information about "tag" and "star" in client side:
+TagMap layout:
<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+
+<template>
+ <div>
+ <h1>Tag page</h1>
+ <ul>
+ <li v-for="({ items, path }, name) in categoryMap.map">
+ <RouteLink :key="name" :to="path" class="category">
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </li>
+ </ul>
+ </div>
+</template>
+TagList layout:
<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+
+<template>
+ <div>
+ <h1>Tag page</h1>
+ <div class="category-wrapper">
+ <RouteLink
+ v-for="({ items, path }, name) in categoryMap.map"
+ :key="name"
+ :to="path"
+ class="category"
+ >
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </div>
+ <div class="article-wrapper" v-if="categoryMap.currentItems">
+ <div v-if="!categoryMap.currentItems.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in categoryMap.currentItems"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline
+ ? `${new Date(info.date).toLocaleDateString()}: `
+ : '') + info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author"
+ >Author: {{ info.author }}</span
+ >
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag"
+ >Tag: {{ info.tag.join(', ') }}</span
+ >
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+ </div>
+</template>
+StarList layout:
<script setup lang="ts">
+import { useBlogType } from '@vuepress/plugin-blog/client'
+import { RouteLink } from 'vuepress/client'
+
+import ArticleList from '../components/ArticleList.vue'
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+
+const stars = useBlogType('star')
+</script>
+
+<template>
+ <div class="article-wrapper" v-if="stars.items">
+ <div v-if="!stars.items.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in stars.items"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline ? `${new Date(info.date).toLocaleDateString()}: ` : '') +
+ info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author">Author: {{ info.author }}</span>
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag">Tag: {{ info.tag.join(', ') }}</span>
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+</template>
+For return types, please see Composition API Return Types.
+This plugin adds native i18n support, so your settings will be automatically applied to each language.
+For example, if user has the following locales' config, and you are setting the "star" example above:
+export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+}
+Then /zh/star/ and /star/ will both be available, and only articles under the correct locale will appear.
This plugin provides a built-in excerpt generator, which can be enabled by setting excerpt option to true.
Excerpt introduction
+An excerpt is an HTML fragment that is used to display a short description of an article in the blog list, so the excerpt has the following restrictions:
+isCustomElement option..vuepress/public or full URL to ensure they can be accessed in other places.The excerpt generator will try to find a valid excerpt separator from markdown contents, if it finds one, it will use content before the separator. The separator is default <!-- more -->, and you can customize it by setting excerptSeparator option.
If it cannot find a valid separator, it will parse content from the beginning of markdown file, and stop till its length reaches a preset value. The value is default 300, and you can customize it by setting excerptLength option.
To choose which page should generate excerpt, you can use excerptFilter option.
Example
+Normally you may want to use frontmatter.description if users set them, so you can let filter function return false if frontmatter.description is not empty.
You can both set options with plugin options on Node side and set options in client config file on Browser side.
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+// .vuepress/config.ts
+export default {
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo
+
+ // other options here
+ // ...
+ }),
+ ],
+}
+import { defineClientConfig } from 'vuepress/client'
+import {
+ defineArtalkConfig,
+ // defineGiscusConfig,
+ // defineTwikooConfig,
+ // defineWalineConfig,
+} from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+But here are some limitations you should remember:
+provider, locales and other resource related option must be set in plugin options.
To ensure tree-shaking works, we must optimize entries at node so that bundler can understand which resource should be included in the final bundle.
+These options will be marked with
+Options which can not be serialized to JSON must be set in client config.
+Options that receives function values can not be set in plugin options, as plugins are running under Node.js environment, so we can not pass these values and their contexts to browser.
+These options will be marked with
+This plugin globally registers a component <CommentService />.
alias and layout slots to insert the component. We recommended you to insert the comment component (<CommentService />) after the <PageNav /> component, and the current page is a demo with default theme.By default, <CommentService /> component is enabled globally, and you can use comment option in both plugin options and page frontmatter to control it.
comment: false in page frontmatter.comment to false in the plugin options. Then you can set comment: true in page frontmatter to enable it locally.You can set commentID option in page frontmatter to customize comment ID, which is used to identify comment storage item to use for a page. By default it will be the path of the page, which means if you are deploying the site to multiple places, page with same content across sites will share the same comment data.
Currently, you can choose from Giscus, Waline, Artalk and Twikoo.
+Recommended comment services
+"Artalk" | "Giscus" | "Twikoo" | "Waline" | "None""None"booleantruestringSiteConfig.titleChannel title
+stringoptions.hostname and context.base)Channel address
+stringSiteConfig.descriptionChannel description
+Type: string
Default:
+siteConfig.locales['/'].lang"en-US"The language of the channel
+Type: string
Default:
+author.name in channel options, and fall back to Copyright by $authorRecommended to set manually: Yes
+Channel copyright information
+string (must be a valid Date ISOString)Publish date of the Channel
+string (must be a valid Date ISOString)Last update time of channel content
+numberThe effective time of the content. It's the time to keep the cache after request without making new requests.
+stringA picture presenting the channel. A square picture with a size not smaller than 512×512 is recommended.
+stringAn icon representing a channel, a square picture, with not less than 128×128 in size, and transparent background color is recommended.
+FeedAuthorThe author of the channel.
+interface FeedAuthor {
+ /** Author name */
+ name: string
+ /** Author's email */
+ email?: string
+ /** Author's site */
+ url?: string
+ /**
+ * Author's avatar address
+ *
+ * Square, preferably not less than 128×128 with transparent background
+ */
+ avatar?: string
+}
+stringLink to Websub. Websub requires a server backend, which is inconsistent with VuePress, so ignore it if there is no special need.
+WebSub
+For details, see Websub.
+stringThe domain name of the deployment site.
+booleanfalseWhether to output Atom syntax files.
+booleanfalseWhether output JSON syntax files.
+booleanfalseWhether to output RSS syntax files.
+stringA large image/icon of the feed, probably used as banner.
+stringA small icon of the feed, probably used as favicon.
+number100Set the maximum number of items in the feed. After all pages are sorted, the first count items will be intercepted.
If your site has a lot of articles, you may consider this option to reduce feed file size.
+(RegExp | string)[] | (tagName: string) => booleanCustom element or component which should be preserved in feed.
+By default, all unknown tags will be removed.
+Type: (page: Page)=> boolean
Default:
+;({ frontmatter, filePathRelative }: Page): boolean =>
+ !(
+ frontmatter.home ||
+ !filePathRelative ||
+ frontmatter.article === false ||
+ frontmatter.feed === false
+ )
+A custom filter function, used to filter feed items.
+Type: (pageA: Page, pageB: Page)=> number
Default:
+// dateSorter is from @vuepress/helper
+;(pageA: Page, pageB: Page): number =>
+ dateSorter(
+ pageA.data.git?.createdTime
+ ? new Date(pageA.data.git?.createdTime)
+ : pageA.frontmatter.date,
+ pageB.data.git?.createdTime
+ ? new Date(pageB.data.git?.createdTime)
+ : pageB.frontmatter.date,
+ )
+Custom sorter function for feed items.
+The default sorting behavior is by file adding time coming from git (needs @vuepress/plugin-git).
TIP
+You should enable @vuepress/plugin-git to get the newest created pages as feed items. Otherwise, the feed items will be sorted by the default order of pages in VuePress.
channel option is used to config Feed Channels.
For available options, please see Config → Channel
+booleanfalseWhether enabled in devServer.
+TIP
+For performance reasons, we do not provide hot reload. Reboot your devServer to sync your changes.
+string"http://localhost:${port}"Hostname to use in devServer
+string"atom.xml"Atom syntax output filename, relative to dest folder.
+string@vuepress/plugin-feed/templates/atom.xslAtom xsl template file content.
+string"atom.xsl"Atom xsl filename, relative to dest folder.
+string"feed.json"JSON syntax output filename, relative to dest folder.
+string"rss.xml"RSS syntax output filename, relative to dest folder.
+string@vuepress/plugin-feed/templates/rss.xslRSS xsl template file content.
+string"rss.xsl"RSS syntax xsl filename, relative to dest folder.
+Feed generation controller, see Feed Getter.
+The plugin has a built-in getter, only set this if you want full control of feed generation.
+Record<string, BaseFeedOptions>You can use it to specific options for each locale.
+Any options above are supported except hostname.
By default, all articles are added to the feed stream. Set feed: false in frontmatter to remove a page from feed.
stringAutomatically generated by VuePress, defaults to the h1 content of the page
+stringDescription of the page
+DateDate when the page was published
+booleanWhether the page is an article
+++If this is set to
+false, the page will not be included in the final feed.
stringPage copyright information
+stringImage used as page cover , should be full link or absolute link.
+stringThe title of the feed item
+stringDescription of the feed item
+stringThe content of the feed item
+FeedAuthor[] | FeedAuthorThe author of the feed item
+interface FeedAuthor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+FeedContributor[] | FeedContributorContributors to feed item
+interface FeedContributor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+stringThe identifier of feed item, used to identify the feed item.
+You should ensure every feed has a unique guid.
+getter in the plugin options.
+(page: Page) => stringItem title getter
+(page: Page) => stringItem link getter
+(page: Page) => string | undefinedItem description getter
+TIP
+Due to Atom support HTML in summary, so you can return HTML content here if possible, but the content must start with mark html:.
(page: Page) => stringItem content getter
+(page: Page) => FeedAuthor[]Item author getter.
+The getter should return an empty array when author information is missing.
+interface FeedAuthor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => FeedCategory[] | undefinedItem category getter.
+interface FeedCategory {
+ /**
+ * Category Name
+ */
+ name: string
+
+ /**
+ * A string that identifies a categorization taxonomy
+ *
+ * @description rss format only
+ */
+ domain?: string
+
+ /**
+ * the categorization scheme via a URI
+ *
+ * @description atom format only
+ */
+ scheme?: string
+}
+(page: Page) => FeedEnclosure | undefinedItem enclosure getter.
+interface FeedEnclosure {
+ /**
+ * Enclosure link
+ */
+ url: string
+
+ /**
+ * what its type is
+ *
+ * @description should be a standard MIME Type, rss format only
+ */
+ Type: string
+
+ /**
+ * Size in bytes
+ *
+ * @description rss format only
+ */
+ length?: number
+}
+(page: Page) => Date | undefinedItem release date getter
+(page: Page) => DateItem last update date getter
+(page: Page) => stringItem Image Getter
+Ensure it's returning a full URL
+(page: Page) => FeedContributor[]Item Contributor Getter
+The getter should return an empty array when contributor information is missing.
+interface FeedContributor {
+ /**
+ * Author name
+ */
+ name?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+
+ /**
+ * Author site
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * Author avatar
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => string | undefinedItem copyright getter
+]]>The plugin can generate feed files in the following three formats for you:
+Please set atom, json or rss to true in the plugin options according to the formats you want to generate.
To correctly generate feed links, you need to set hostname in the plugin options,
When you open the feed file in browser, we magically convert atom and rss feed xml to human readable html via xsl template. Check atom and rss feed of this site as an example!
+If you want to preview your feed in devServer, set devServer: true in plugin options. You may also need to set devHostname if you are not using the default http://localhost:{port}.
You can customize the feed channel information by setting the channel option.
We recommend the following settings:
+channel.pubDatechannel.ttl (unit: minutes)channel.copyrightchannel.author.For detailed options and their default values, see Channel Config
+By default, all articles are added to the feed stream.
+You can set feed and other options in page frontmatter to control contents of feed item. See Frontmatter Config for how they are converted.
You can take full control of feed items generation by configuring the getter in the plugin options. For detailed options and their default values, see Configuration → Feed Getter.
The plugin generates separate feeds for each language.
+You can provide different settings for different languages via locales in the plugin options.
booleanfalseType: AppManifest
Details:
+You can fill with an object which will be parsed to manifest.webmanifest.
+TIP
+Some options have their fallback if you don't set them.
+siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.description || siteConfig.locales['/'].description || "A site built with vuepress"siteConfig.locales['/'].lang || "en-US"context.basecontext.base"standalone""#46bd87""#ffffff""portrait-primary"falseReference:
+ +Type: string
Details:
+Link of favicon.ico.
+WARNING
+We recommend you to set favicon for your site.
+Type: string
Default: "#46bd87"
Details:
+Theme Color of the pwa.
+Type: boolean
Default: false
Details:
+Whether cache HTML files besides home page and 404 page.
+Type: boolean
Default: false
Details:
+Whether cache pictures
+Type: number
Default: 2048
Details:
+Max size allowed to be cached, with KB unit
+WARNING
+This option has the highest priority, and any files exceeding this value will be excluded.
+So if you generate very large HTML or JS files, please consider increasing this value, otherwise your PWA may not work normally in offline mode.
+Type: number
Default: 1024
Details: +Max picture size allowed to be cached, with KB unit
+The value must not be greater than maxSize option
+Type: "disabled" | "available" | "hint" | "force"
Default: "available"
Details: +Control logic when new content is found.
+"disabled": Do nothing even when new service worker is available. After new service work succeeds installing and starts waiting, it will control page and provide new content in next visit.
"available": Only display update popup when the new service worker is available
"hint": Display a hint to let user choose to refresh immediately
This is helpful when you want users to see new docs immediately.
+TIP
+If users choose to refresh, the current service worker will be unregister, and request will start coming to web. Later the new service worker will start installing and control current page after installed.
+"force": unregister current service worker immediately then refresh to get new content
DANGER
+Although this ensures users are viewing the latest content, it may affect viewing experiences.
+TIP
+How docs are updated is controlled by a previous version, so the current option only effect next update from this version.
+Special settings for better supporting Safari, ignoring these options are safe.
+string"black" | "white""black"stringSpecial settings for Microsoft tiles, ignoring these options are safe.
+stringstringthemeColorstring"PwaFoundPopup"string"PwaReadyPopup"booleanfalseDetails:
+Options passed to workbox-build, for details, see Workbox documentation
Type: PwaPluginLocaleConfig
interface PwaPluginLocaleData {
+ /**
+ * Install button text
+ */
+ install: string
+
+ /**
+ * iOS install hint text
+ */
+ iOSInstall: string
+
+ /**
+ * Cancel button text
+ */
+ cancel: string
+
+ /**
+ * Close button text
+ */
+ close: string
+
+ /**
+ * Previous image text
+ */
+ prevImage: string
+
+ /**
+ * Next image text
+ */
+ nextImage: string
+
+ /**
+ * Install explain text
+ */
+ explain: string
+
+ /**
+ * Description label text
+ */
+ desc: string
+
+ /**
+ * Feature label text
+ */
+ feature: string
+
+ /**
+ * Update hint text
+ */
+ hint: string
+
+ /**
+ * Update available text
+ */
+ update: string
+}
+
+interface PwaPluginLocaleConfig {
+ [localePath: string]: PwaPluginLocaleData
+}
+Details: +Locales config for pwa plugin.
+Details:
+Returns the event emitter of this plugin.
+You can add listener function to events that provided by register-service-worker.
+Example:
+import { usePwaEvent } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+ event.on('ready', (registration) => {
+ console.log('Service worker is active.')
+ })
+ },
+}
+Details:
+Force update the page when an update is found.
+Example:
+import { forceUpdate } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ forceUpdate()
+ })
+ },
+}
+Details:
+Register service worker manually.
+Parameters:
+| Parameter | Type | Description | +|
+]]>Make your VuePress site a Progressive Web Application (PWA)[1].
+This plugin uses workbox-build to generate service worker file, and uses register-service-worker to register service worker.
+WARNING
+If you enabled this plugin once and you want to disable it, you might need `@vuepress/plugin-remove-pwa to remove the existing service worker.
+A PWA uses a Service Worker [2] (SW for short) to cache and proxy site content.
+To make your website fully compliant with PWA, a Web app manifests [3] file is needed, and your pwa should satisfy the installability [4] specification.
+You can set manifest option to customize the manifest file, or provide a manifest.webmanifest or manifest.json in public folder. The former has higher priority.
The plugin will automatically generate manifest.webmanifest for you and add manifest link declaration in each page, while you should still at least set a valid icon through manifest.icons or other icon related options in the PWA plugin.
WARNING
+The installability [4:1] specification requires at least one valid icon to be declared in the manifest.
+So if you do not configure manifest.icons, visitors can only enjoy the offline accessibility brought by the Service Worker cache, while cannot install your site as a PWA.
Besides the plugin does not process anything in the manifest by default, but outputs them as-is. This means that if you plan to deploy to a subdirectory, you should append the URL prefix to manifest Urls yourself. If everything you need is all under base directory, you can set appendBase: true in plugin options to let the plugin append base to any links in manifest.
To better control what the Service Worker can pre-cache, the plugin provides related options for cache control.
+By default, the plugin will pre-cache all js css files, and only homepage and 404 html are cached. The plugin will also cache font files (woff, woff2, eot, ttf, otf) and SVG icons.
If your site has only a few important images, and want them displayed in offline mode, you can cache site images by setting cacheImage: true .
We recognize images by file extension. Any files ending with .png, .jpg, .jpeg, .gif, .bmp, .webp will be regarded as images.
If you have small sites, and would like to make document fully offline available, you can set cacheHTML to true to cache all HTML files.
Why only home and 404 page been cached by default?
+Though VuePress generates HTML files through SSG[5] for all pages, these files are mainly used for SEO[6] and allow you to directly configure the backend without SPA[7] Visit any link.
+VuePress is essentially an SPA. This means that you only need to cache the home page and enter from the home page to access all pages normally. Therefore, not caching other HTML by default can effectively reduce the cache size (40% smaller in size) and speed up the SW update speed.
+But this also has the disadvantage. If the user enters the site directly from a non-home page, the HTML file for the first page still needs to be loaded from the internet. Also, in offline environment, users can only enter through the homepage and then navigate to the corresponding page by themselves. If they directly access a link, an inaccessible prompt will appear.
+To prevent large files from being included in the pre-cache list, any files > 2 MB or images > 1 MB will be omitted. You can customize these limits with maxSize and maxImageSize options (in KB unit).
We provide the update option to control how users receive updates.
The default value of the update option is "available", which means that when new content available, the new SW will be installed and its resources will be fetched silently in the background. A pop-up window appears once the new SW is ready, and users can choose whether to refresh immediately to view new content. This means users are reading old content before a new SW is ready.
If your project is still in building stage, and you want to alert the user that he may be reading outdated content, you can set this to "hint". This allows users to be notified that new content has been published within seconds after visiting docs. But the negative effect of this is that if the user chooses to update before the new SW is ready, he will need to get all the resources of the page from the internet before the new SW installs and controls the page.
If your docs are stable, or you're hosting a blog and don't care much about users receiving the latest version right away, you can set this to "disabled", which means that the new SW will be installed completely silently in the background and start waiting, when all pages controlled by old SW are all closed, the new SW will start to take control and provide users with new content during next visit. This setting can prevent users from being disturbed during the visit.
To speed up user access under weak or no network conditions through SW, but also want users to always access new content, you can set this option to "force". This means any old SW will be removed as soon as a new SW is detected, and all pages are refreshed to ensure the user is browsing the latest content. The biggest disadvantage is that all users will experience unexpected sudden refresh within seconds after reentering an updated site.
When new content is detected (new SW detected), a update found popup appears; and when the new content is ready, an update ready popup appears.
+If you are not satisfied with the default popup content, you can use your own component. Import PwaFoundPopup or PwaReadyPopup from @vuepress/plugin-pwa/client and use its slot to customize the popup content, then pass the component path to foundComponent or readyComponent option:
<script setup lang="ts">
+import { PwaFoundPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaFoundPopup v-slot="{ found, refresh }">
+ <div v-if="found">
+ New content is found.
+ <button @click="refresh">Refresh</button>
+ </div>
+ </PwaFoundPopup>
+</template>
+<script setup lang="ts">
+import { PwaReadyPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaReadyPopup v-slot="{ isReady, reload }">
+ <div v-if="isReady">
+ New content is ready.
+ <button @click="reload">Apply</button>
+ </div>
+ </PwaReadyPopup>
+</template>
+The plugin also provides other PWA-related options, such as Microsoft tile icon and color settings, Apple icon and so on. If you are an advanced user, you can also set generateSwConfig to configure workbox-build. Check Plugin options for more details.
For more details, please see:
+ +PWA introduction
+PWA, full name Progressive Web app. PWA standard is stipulated by W3C.
+It allows sites to install the site as an App on supported platform through a browser that supports this feature.
+See https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps for details. ↩︎
+Service Worker Introduction
+The Service Worker will get and cache all the files registered in it during the registration process.
+After the registration complete, the Service Worker is activated, and starts to proxy and control all your requests.
+Whenever you want to initiate an access request through the browser, the Service Worker will check whether it exists in its own cache list, if it exists, it will directly return the cached result, otherwise it will call its own fetch method to get it. You can use a custom fetch method to fully control the result of the request for resources in the web page, such as providing a fallback web page when offline.
+Every time the user reopens the site, the Service Worker will request to the link when it was registered. If a new version of Service Worker is detected, it will update itself and start caching the list of resources registered in the new Service Worker . After the content update is successfully obtained, the Service Worker will trigger the update event. The user can be notified through this event, for example, a pop-up window will be displayed in the lower right corner, prompting the user that new content is available and allowing the user to trigger an update.
Manifest File
+The manifest file uses the JSON format and is responsible for declaring various information of the PWA, such as name, description, icon, and shortcut actions.
+In order for your site to be registered as a PWA, you need to meet the basic specifications of the manifest to make the browser consider the site as an installable PWA and allow users to install it.
+TIP
+For Manifest standards and specifications, please see MDN Web app manifests and W3C Manifest.
+Installable
+To let the site be registered as a PWA, the site needs to successfully register a valid service worker by itself, and declare a valid manifest file with its link in meta tag.
+The manifest file should contain at least name (or short_name) icons start_url.
On safari, the maximum cache size of the service worker is 50 MB. ↩︎ ↩︎
+SSG: Static Site Generation, ↩︎
+SEO: Search Engine Optimization. ↩︎
+SPA: Single Page Application, most of them only have the homepage, and use history mode to handle routing instead of actually navigating between pages. ↩︎
+Type: string
Required: Yes
+Details:
+Deploy hostname.
+Type: Author
type AuthorName = string
+
+interface AuthorInfo {
+ /**
+ * Author name
+ */
+ name: string
+
+ /**
+ * Author website
+ */
+ url?: string
+
+ /**
+ * Author email
+ */
+ email?: string
+}
+
+type Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]
+Required: No
+Details:
+Default author.
+Type: boolean
Default: true
Details:
+Whether generate description automatically
+Type: string | ((page: Page) => string | null)
Details:
+Canonical link
+Type: string
Details:
+Fallback Image link when no image are found
+Type: string
Details:
+The age rating of the content, the format is [int]+, such as "13+".
Type: string
Details:
+Fill in your twitter username.
+Type: (page: Page) => boolean
Details:
+Use this option to judge whether the page is an article.
+Type:
+function ogp(
+ /** OGP info inferred by plugin */
+ ogp: SeoContent,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+Required: No
+Details:
+Custom OPG Generator.
+You can use this options to edit OGP tags.
+Type:
+function jsonLd(
+ /** JSON-LD Object inferred by plugin */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+Required: No
+Details:
+Custom JSON-LD Generator.
+You can use this options to edit JSON-LD properties.
+Type:
+function customHead(
+ /** Head tag config */
+ head: HeadConfig[],
+ /** Page Object */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+Required: No
+Details:
+You can use this options to edit tags injected to <head>.
The plugin works out of the box. Without any config, it will extract information from the page content as much as possible to complete the necessary tags required by OGP and JSON-LD.
+By default, the plugin will read the site config and page frontmatter to automatically generate tags as much as possible. Such as site name, page title, page type, writing date, last update date, and article tags are all automatically generated.
+The following are the <meta> tags and their values that will be injected into <head> by default:
The following are the <meta> tags and their value injected into <head> by default to satisfy OGP:
| Meta Name | Value | +| :
+]]>Type: string
Required: Yes
+Details:
+The domain name where the current site is deployed, the plugin needs this option to work.
+Type: string[]
Details:
+Extra link to be included.
+If you have some links not including in VuePress Router (normally in public directory or generated by other tools directly), you may need this option.
+Example: ['/about.html', '/api/']
Type: string[]
Default: ['/404.html']
Details:
+Urls excluding from sitemap, starting with absolute path.
+By default, all the urls generated by VuePress (excluding 404 page) will be added into sitemap.
+Type: boolean
Default: false
Details:
+Whether enabled in devServer.
+TIP
+For performance reasons, we do not provide hot reload. Reboot your devServer to sync your changes.
+Type: string
Default: "http://localhost:${port}"
Details:
+Hostname to use in devServer
+Type: string
Default value: "sitemap.xml"
Details:
+The output filename, relative to output directory.
+Type: string
Default value: "sitemap.xsl"
Details:
+Output xsl filename, relative to dest folder.
+Type: string
Default value: "@vuepress/plugin-sitemap/templates/sitemap.xsl"
Details:
+XSL content used as template.
+Type: "always" | "hourly" | "daily" | "weekly" |"monthly" | "yearly" | "never"
Default value: "daily"
Details:
+Page default update frequency, will be overridden by sitemap.changefreq in Frontmatter.
+Type: number
Default: 0.5
Details:
+Page priority, from 0 to 1.
Type: (page: Page, app: App) => string
Details:
+Last modify time getter. By default, the plugin will use the timestamp generated by git plugin.
+Type: SitemapFrontmatterOptions | false
Details:
+false means exclude the page from sitemap.
Type: "always" | "hourly" | "daily" | "weekly" | "monthly" | "yearly" | "never"
Default: "daily"
Details:
+Page default update frequency. This will override changefreq in Plugin Options.
+Type: number
Default: 0.5
Details:
+Page priority, range from 0 to 1.
hostname option of the plugin. If you want to preview in devServer, set devServer options.
+The plugin will automatically generate the last update time of the page based on the Git timestamp of the page, and will also declare the alternative links of the page in other languages according to the locales' config.
+By default, all site links except 404 page will be added to the Sitemap.
+To add other pages to the Sitemap outside the VuePress project page, please turn them into an array and pass to the extraUrls plugin option.
If you don't want certain pages to appear in the sitemap, you can turn their paths into an array and pass to the excludePaths plugin option, or set sitemap to false in the frontmatter of the corresponding page.
You can also control the output link through the sitemapFilename option of the plugin, the link is relative to output directory. By default, the plugin will use sitemap.xml.
The default update cycle of the page is daily (every day). To modify the entire page cycle, please set changefreq in the plugin options. You can also set sitemap.changefreq in the frontmatter of the page. Note that page has a higher priority.
The legal frequencies are:
+"always""hourly""daily""weekly""monthly""yearly""never"You can set priority in the plugin to provide a default value. At the same time you can set the priority for each page through sitemap.priority in frontmatter. Acceptable values are floating point numbers from 0 to 1.
You can use option modifyTimeGetter to return a time in ISO string format, which is generated by the Git plugin by default.
The following is an example based on the last modification time of a file.
+// Based on file last modified time
+({
+ modifyTimeGetter: (page, app) =>
+ fs.statSync(app.dir.source(page.filePathRelative)).mtime.toISOString();
+})
+Sitemaps provide SEO (Search Engine Optimization):
+A sitemap enhances SEO by making all pages findable.
+Most search engines only follow a limited number of links within a page, so when the site is very large, a sitemap becomes essential to make everything on the site accessible to search engines and visitors.
+Sitemaps is a protocol for site administrators to publish pages that can be crawled on a site to search engine spiders. The content of sitemap files must follow the definition in XML format. Each URL can contain the update period and last update time, the priority of the URL across the site. This allows search engines to crawl site content better and more efficiently.
+Together with robots.txt
+Sitemap is basically used by search engines, when using this plugin, you'd better ensure that you have a valid robots.txt in the .vuepress/public directory to allow search engines spiders to visit your site. The simplest robots.txt is as follows (allow all search engines to access all paths)
User-agent: *
+
+Allow: /
+Check whether a component is registered globally.
+TIP
+setup scope, you need to pass the app instance as the second parameter.export const hasGlobalComponent: (name: string, app?: App) => boolean
+// if you globally register `<my-component>`
+hasGlobalComponent('MyComponent') // true
+hasGlobalComponent('my-component') // true
+
+hasGlobalComponent('MyComponent2') // false
+Get current locale config from locales settings.
+export const useLocaleConfig: <T extends LocaleData>(
+ localesConfig: RequiredLocaleConfig<T>,
+) => ComputedRef<T>
+const localesCOnfig = {
+ '/': 'Title',
+ '/zh/': '标题',
+}
+
+const locale = useLocaleConfig(localesConfig)
+
+// under `/page`
+locale.value // 'Title'
+
+// under `/zh/page`
+locale.value // '标题'
+Encode/decode and zip/unzip data.
+This is useful in markdown plugins when you want to encode string content and pass it to the component through props.
+You may simply achieve this with encodeURIComponent and decodeURIComponent, but it can be very large if the content contains lots of special characters.
So we provide encodeData and decodeData to zip and encode content.
export const encodeData: (
+ data: string,
+ level: DeflateOptions['level'] = 6,
+) => string
+
+export const decodeData: (compressed: string) => string
+const content = `
+{
+ "type": "bar",
+ "data": {
+ "labels": ["Red", "Blue", "Yellow", "Green", "Purple", "Orange"],
+ "datasets": [
+ {
+ "label": "# of Votes",
+ "data": [12, 19, 3, 5, 2, 3],
+ "backgroundColor": [
+ "rgba(255, 99, 132, 0.2)",
+ "rgba(54, 162, 235, 0.2)",
+ "rgba(255, 206, 86, 0.2)",
+ "rgba(75, 192, 192, 0.2)",
+ "rgba(153, 102, 255, 0.2)",
+ "rgba(255, 159, 64, 0.2)"
+ ],
+ "borderColor": [
+ "rgba(255, 99, 132, 1)",
+ "rgba(54, 162, 235, 1)",
+ "rgba(255, 206, 86, 1)",
+ "rgba(75, 192, 192, 1)",
+ "rgba(153, 102, 255, 1)",
+ "rgba(255, 159, 64, 1)"
+ ],
+ "borderWidth": 1
+ }
+ ]
+ },
+ "options": {
+ "scales": {
+ "y": {
+ "beginAtZero": true
+ }
+ }
+ }
+}
+`
+
+const prop = encodeData(content) // "eJyNUsFOwzAMve8rrHABKZqWlg5WxAE4cARxAMHEIV1NmQhNlaaCCe3fcdKtW0sLWGpjxy/v+UV512mlcIyfhTa2hHP4GgHYVYExsEQaxqlMpZWxbwAomaAqY5izO0wZB3apKnTrIyqlP1x2bRBzl9xWplC+eWNkniF7dmw1X4nWsfgaNtwNP2kfgH6Be22x9CPUUQ8yFwEHMeMQcog4UBFuiF0kcvGWGV3l6ZVW2uw0XDCTJfIwiOjYjAhESIcn4+BoT2MLio6pP6V+EBJ6AOSZgsmUwyl9A6ATwoiZn3lYTkTkRkycnuP8TU9ENPqUxuuA9i9BmxTNPy9A/G2/F9I23wtpW++FdIwPKzW2W5Afph+WqX2NQWz313XicT7XhV3qnB5f/ejKhVTYVACrXUqUmC3zC/uERsdgTYUdVr/Qb302+gZxe7S/"
+
+decodeData(prop) // will be the original content
+
+// if you use `encodeURIComponent`, it will be much longer
+encodeURIComponent(content) // '%0A%7B%0A%20%20%22type%22%3A%20%22bar%22%2C%0A%20%20%22data%22%3A%20%7B%0A%20%20%20%20%22labels%22%3A%20%5B%22Red%22%2C%20%22Blue%22%2C%20%22Yellow%22%2C%20%22Green%22%2C%20%22Purple%22%2C%20%22Orange%22%5D%2C%0A%20%20%20%20%22datasets%22%3A%20%5B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%22label%22%3A%20%22%23%20of%20Votes%22%2C%0A%20%20%20%20%20%20%20%20%22data%22%3A%20%5B12%2C%2019%2C%203%2C%205%2C%202%2C%203%5D%2C%0A%20%20%20%20%20%20%20%20%22backgroundColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%200.2)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%201)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderWidth%22%3A%201%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%0A%20%20%7D%2C%0A%20%20%22options%22%3A%20%7B%0A%20%20%20%20%22scales%22%3A%20%7B%0A%20%20%20%20%20%20%22y%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22beginAtZero%22%3A%20true%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A'
+isDef(x): Check if x is defined.isBoolean(x): Check if x is a boolean.isString(x): Check if x is a string.isNumber(x): Check if x is a number.isPlainObject(x): Check if x is a plain object.isArray(x): Check if x is an array.isFunction(x): Check if x is a function.isRegExp(x): Check if x is a regular expression.startsWith(a, b): Check if string a starts with string b.endsWith(a, b): Check if string a ends with string b.Return false if a is not a string.
keys(x): Return an array of keys of object x.
values(x): Return an array of values of object x.
entries(x): Convert object x to an array of key-value pairs.
fromEntries(x): Convert an array of key-value pairs x to an object.
deepAssign(x, y, ...): A deep version of Object.assign.
// or @vuepress/helper/client
+import { deepAssign } from '@vuepress/helper'
+
+const defaultOptions = {
+ optionA: {
+ optionA1: 'defaultOptionA1',
+ optionA2: 'defaultOptionA2',
+ optionA3: 'defaultOptionA3',
+ },
+ optionB: true,
+ optionC: 'optionC',
+}
+
+const userOptions = {
+ optionA: {
+ optionA1: 'optionA1',
+ optionA2: 'optionA2',
+ },
+ optionB: false,
+}
+
+deepAssign(defaultOptions, userOptions)
+// {
+// optionA: {
+// optionA1: "optionA1",
+// optionA2: "optionA2",
+// optionA3: "defaultOptionA3",
+// },
+// optionB: false,
+// optionC: "optionC",
+// }
+getDate(x): Convert input x to a date. It can support Date, timestamp, and date string. The support degree of date string depends on the Date.parse support degree of the environment. Return null when it cannot be converted to a date.
getDate('2021-01-01') // a Date object represents 2021-01-01
+getDate(1609459200000) // a Date object represents 2021-01-01
+getDate('2021-01-01T00:00:00.000Z') // a Date object represents 2021-01-01
+getDate('2021/01/01') // a Date object represents 2021-01-01 (might be null in some browsers)
+getDate('invalid date') // null
+getDate(undefined) // null
+getDate(-32) // null
+dateSorter: Sort the values that can be converted to dates from new to old, and the values that cannot be converted to dates will be at the end.
const arr = [
+ '2020-01-01',
+ 1609459200000,
+ '2022-01-01T00:00:00.000Z',
+ '2023/01/01',
+ 'invalid date',
+ undefined,
+ -32,
+]
+
+arr.sort(dateSorter)
+// [
+// '2023/01/01',
+// '2022-01-01T00:00:00.000Z',
+// 1609459200000,
+// '2020-01-01',
+// 'invalid date',
+// undefined,
+// -32,
+// ]
+isLinkHttp(x): Check if x is a valid HTTP URL.isLinkWithProtocol(x): Check if x is a valid URL with protocol.isLinkExternal(x): Check if x is a valid external URL.isLinkAbsolute(x): Check if x is a valid absolute URL.ensureEndingSlash(x): Ensure x ends with a slash.ensureLeadingSlash(x): Ensure x starts with a slash.removeEndingSlash(x): Ensure x does not end with a slash.removeLeadingSlash(x): Ensure x does not start with a slash.Come to your blog, or anywhere, place the Artalk comment box, so that the page has rich social functions.
+ +npm i -D artalk
+See the Artalk documentation.
+Please set provider: "Artalk" and pass your server link to server in the plugin options.
For other configuration items, see Artalk Config.
+TIP
+The plugin retains the el option and inserts Artalk itself on the page. At the same time, the plugin will automatically set the pageTitle, pageKey and site options for you according to the VuePress information.
To let Artalk apply the correct theme, you need to pass a boolean value to <CommentService /> through darkmode prop, representing whether the dark mode is currently enabled.
See Artalk Configuration for details.
+The el pageTitle, pageKey and site options are reserved for plugins, they will be inferred from VuePress config.
Two function options imgUploader and avatarURLBuilder can only be set on client side.
You can directly configure serializable options in the plugin options:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineArtalkConfig function to customize Artalk:
import { defineClientConfig } from 'vuepress/client'
+import { defineArtalkConfig } from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // Artalk config
+})
+
+export default defineClientConfig({
+ // ...
+})
+Create a public repository and open discussion panel as a place to store comments.
+Install the Giscus App to have permission to access the corresponding repository.
+After completing the above steps, please go to the Giscus page to get your settings.
+You just need to fill in the repository and Discussion categories, then scroll to the "Enable giscus" section at the bottom of the page and obtain four attributes: data-repo, data-repo-id, data-category and data-category-id.
Please set provider: "Giscus" and pass data-repo, data-repo-id, data-category and data-category-id as plugin options as repo, repoId, category categoryId.
For other options, see Giscus Config.
+By default, the theme of Giscus is light or dark (based on darkmode status).
Darkmode
+To let Giscus apply the correct theme, you need to pass a boolean value to <CommentService /> via darkmode property, indicating whether darkmode is currently enabled.
If you want to customize theme in lightmode and darkmode, you can set lightTheme and darkTheme option with a built-in theme keyword or a custom CSS link starting with https://.
stringstringstringstringstring"pathname"booleantruebooleantruebooleantrue"top" | "bottom""top"Type: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+Default: "light"
Details:
+Giscus theme used in lightmode
+Should be a built-in theme keyword or a css link starting with https://.
Type: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+Default: "dark"
Details:
+Giscus theme used in darkmode
+Should be a built-in theme keyword or a css link starting with https://.
You can directly configure serializable options in the plugin options:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Giscus',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineGiscusConfig function to customize Giscus:
import { defineClientConfig } from 'vuepress/client'
+import { defineGiscusConfig } from 'vuepress-plugin-comment2/client'
+
+defineGiscusConfig({
+ // Giscus config
+})
+
+export default defineClientConfig({
+ // ...
+})
+npm i -D twikoo
+Apply for MongoDB account
+Create a free MongoDB database, the recommended region is AWS / N. Virginia (us-east-1)
Click CONNECT on the Clusters page, follow the steps to allow connections from all IP addresses (Why?), create Database user, and record the database connection string, please change the <password> in the connection string to the database password
Sign up for a Vercel account
+Click the button below to deploy Twikoo to Vercel in one click
+Go to Settings - Environment Variables, add the environment variable MONGODB_URI, the value is the database connection string in step 3
Go to Overview, click the link under Domains, if the environment configuration is correct, you can see the prompt "Twikoo cloud function is running normally"
+Vercel Domains (with https:// prefix, e.g. https://xxx.vercel.app) is your environment ID
Please set provider: "Twikoo" and set envId in the plugin options.
For other configuration items, see Twikoo Config.
+]]>stringYou can directly configure serializable options in the plugin options:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Twikoo',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineTwikooConfig function to customize Twikoo:
import { defineClientConfig } from 'vuepress/client'
+import { defineTwikooConfig } from 'vuepress-plugin-comment2/client'
+
+defineTwikooConfig({
+ // Twikoo config
+})
+
+export default defineClientConfig({
+ // ...
+})
+npm i -D @waline/client
+Click Create app button to create a new app and enter a name you like:
+ +Enter the app, then select Settings > App Keys at the left bottom corner. You will see APP ID, APP Key and Master Key of your app. We will use them later
Click the dark button above, it will redirect you to vercel to deploy with waline template.
+TIP
+If you haven't logged in, we recommend you to sign in with GitHub.
+Input your Vercel project name then click Create.
Repo which named you input before will be created and initialized automatically base on waline example template by Vercel.
+
After one minute or two, vercel should finish the deployment. Click Go to Dashboard button to redirect to your application dashboard.
Click Settings menu on the top, and Environment Variables button on the side to go to environment variables setting page. Then set LEAN_ID, LEAN_KEY and LEAN_MASTER_KEY. The variables' value should be the ones you got in the previous step. APP ID is the value of LEAN_ID, and APP Key to LEAN_KEY, Master Key to LEAN_MASTER_KEY.
To let your environment variables setting active, you need redeploy your application. Click Deployments menu on the top and find the latest deployment at the top of list, click Redeploy button in the right dropdown menu.
If everything is ok, vercel will redirect to Overview page to start redeployment. Wait a moment the STATUS will change to Ready. Now you can click Visit to visit the site. This link is your server address.
Click Settings - Domains to go to domain setting page.
Input domain you want to assign and click Add button.
Add a new CNAME record in your domain service server.
| Type | Name | Value | +|
+stringType: (string | WalineEmojiInfo)[] | false
type WalineEmojiPresets = `http://${string}` | `https://${string}`
+
+interface WalineEmojiInfo {
+ /**
+ * Emoji name show on tab
+ */
+ name: string
+ /**
+ * Current folder link
+ */
+ folder?: string
+ /**
+ * Common prefix of Emoji icons
+ */
+ prefix?: string
+ /**
+ * Type of Emoji icons, will be regarded as file extension
+ */
+ type?: string
+ /**
+ * Emoji icon show on tab
+ */
+ icon: string
+ /**
+ * Emoji image list
+ */
+ items: string[]
+}
+Default: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
Reference:
+ +Details: Emoji settings.
+Type: string | boolean
Default: false
Reference:
+Details:
+Darkmode support
+'auto' will display darkmode due to device settings.Type: WalineCommentSorting
Default: 'latest'
Details:
+Comment list sorting methods.
+Optional values: 'latest', 'oldest', 'hottest'
Type: string[]
Default: ['nick','mail','link']
Details:
+Reviewer attributes.
+Optional values: 'nick', 'mail', 'link'
Type: string[]
Default: []
Details:
+Set required fields, optional values:
+[]['nick']['nick','mail']Type: string
Default value: 'enable'
Details:
+Login mode status, optional values:
+'enable': enable login (default)'disable': Login is disabled, users should fill in information to comment'force': Forced login, users must login to commentType: number | [number, number]
Default: 0
Details:
+Comment words limit. When a single number is filled in, it 's the maximum number of comment words. No limit when set to 0.
Type: number
Default: 10
Details:
+Number of comments per page.
+Type: WalineImageUploader | false
type WalineImageUploader = (image: File) => Promise<string>
+Reference:
+ +Details:
+Custom image upload method. The default behavior is to embed images Base 64 encoded, you can set this to false to disable image uploading.
The function should receive an image object and return a Promise that provides the image address.
+Type: WalineHighlighter | false
type WalineHighlighter = (code: string, lang: string) => string
+Reference:
+ +Details:
+Code highlighting, use hanabi by default. The function passes in original content of code block and language of the code block. You should return a string directly.
You can pass in a code highlighter of your own, or set to false to disable code highlighting.
Type: WalineTexRenderer | false
type WalineTexRenderer = (blockMode: boolean, tex: string) => string
+Reference:
+ +Details:
+Customize TeX rendering, the default behavior is to prompt that the preview mode does not support TeX. The function provides two parameters, the first parameter indicates whether it should be rendered in block level, and the second parameter is the string of the TeX content, and return a HTML string as render result.
+You can import TeX renderer to provide preview feature. We recommend you to use Katex or MathJax, or you can set to false to disable parsing TeX.
Type: WalineSearchOptions | false
interface WalineSearchImageData extends Record<string, unknown> {
+ /**
+ * Image link
+ */
+ src: string
+
+ /**
+ * Image title
+ *
+ * @description Used for alt attribute of image
+ */
+ title?: string
+
+ /**
+ * Image preview link
+ *
+ * @description For better loading performance, we will use this thumbnail first in the list
+ *
+ * @default src
+ */
+ preview?: string
+}
+
+type WalineSearchResult = WalineSearchImageData[]
+
+interface WalineSearchOptions {
+ /**
+ * Search action
+ */
+ search: (word: string) => Promise<WalineSearchResult>
+
+ /**
+ * Default result when opening list
+ *
+ * @default () => search('')
+ */
+ default?: () => Promise<WalineSearchResult>
+
+ /**
+ * Fetch more action
+ *
+ * @description It will be triggered when the list scrolls to the bottom. If your search service supports paging, you should set this to achieve infinite scrolling
+ *
+ * @default (word) => search(word)
+ */
+ more?: (word: string, currentCount: number) => Promise<WalineSearchResult>
+}
+Details: Customize search features, you can disable search function by setting it to false.
Type: string
Details:
+reCAPTCHA V3 is a captcha service provided by Google. You can add reCAPTCHA V3 site key with recaptchaV3Key to enable it.
You should also set environment variable RECAPTCHA_V3_SECRET for server.
Type: boolean | string[]
Default: false
Details:
+Add emoji interaction function to the article, set it to true to provide the default emoji, you can also customize the emoji image by setting the emoji url array, and supports a maximum of 8 emojis.
booleantrueType: WalineLocales
interface WalineLocales {
+ [localePath: string]: WalineLocale
+}
+Reference:
+ +Details: +Waline locales.
+You can directly configure serializable options in the plugin options:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Waline',
+ // other options
+ // ...
+ }),
+ ],
+})
+You can use the defineWalineConfig function to customize Waline:
import { defineClientConfig } from 'vuepress/client'
+import { defineWalineConfig } from 'vuepress-plugin-comment2/client'
+
+defineWalineConfig({
+ // Waline config
+})
+
+export default defineClientConfig({
+ // ...
+})
+All functions should be called in extendsBundlerOptions lifecycle hook.
TIP
+We are omitting that in examples. The actual code should be like this:
+// import functions you need
+import { addCustomElement } from '@vuepress/helper'
+
+export const yourPlugin = {
+ // ...
+ extendsBundlerOptions: (bundlerOptions, app) => {
+ // add them here
+ addCustomElement(bundlerOptions, app, 'my-custom-element')
+ },
+}
+Get current bundler name.
+export const getBundlerName: (app: App) => string
+// @vuepress/bundler-vite
+getBundleName(app) === 'vite' // true
+// @vuepress/bundler-webpack
+getBundleName(app) === 'webpack' // true
+Add a custom element declaration to the current bundler.
+/**
+ * Add tags as customElement
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param customElements tags recognized as custom element
+ */
+export const addCustomElement = (
+ bundlerOptions: unknown,
+ app: App,
+ customElement: string[] | string | RegExp
+) => void;
+import { addCustomElement } from '@vuepress/helper'
+
+addCustomElement(bundlerConfig, app, 'my-custom-element')
+addCustomElement(bundlerOptions, app, [
+ 'custom-element1',
+ 'custom-element2',
+ // all tags start with `math-`
+ /^math-/,
+])
+Provides contents for specific path in dev server.
+export interface DevServerOptions {
+ /**
+ * Path to be responded
+ */
+ path: string;
+ /**
+ * Respond function
+ */
+ response: (request?: IncomingMessage) => Promise<string | Buffer>;
+
+ /**
+ * error msg
+ */
+ errMsg?: string;
+}
+
+/**
+ * Handle specific path when running VuePress Dev Server
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param path Path to be responded
+ * @param response respond function
+ * @param errMsg error msg
+ */
+export const customizeDevServer: (
+ bundlerOptions: unknown,
+ app: App,
+ {
+ errMsg:"The server encountered an error",
+ response: responseHandler,
+ path,
+ }: CustomServerOptions
+) => void;
+import { useCustomDevServer } from '@vuepress/helper'
+
+// handle `/api/` path
+useCustomDevServer(bundlerOptions, app, {
+ path: '/api/',
+ response: async () => getData(),
+ errMsg: 'Unexpected api error',
+})
+addViteOptimizeDepsInclude
+Add modules to Vite optimizeDeps.include list
TIP
+If a package meets one of the following conditions, you should consider adding it here.
+import()addViteOptimizeDepsExclude
+Add modules to Vite optimizeDeps.exclude list
If a package and its dependencies are all pure ESM packages, you should consider adding it here.
+addViteSsrExternal
+Add modules to Vite ssr.external list
If a package is a pure ESM package and does not use aliases or define variables, you should consider adding it here.
+addViteSsrNoExternal
+Add modules to Vite ssr.noExternal list
If an alias or define is used within a package, you must add it here.
+/**
+ * Add modules to Vite `optimizeDeps.include` list
+ */
+export const addViteOptimizeDepsInclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `optimizeDeps.exclude` list
+ */
+export const addViteOptimizeDepsExclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.external` list
+ */
+export const addViteSsrExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.noExternal` list
+ */
+export const addViteSsrNoExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+import {
+ addViteOptimizeDepsInclude,
+ addViteOptimizeDepsExclude,
+ addViteSsrExternal,
+ addViteSsrNoExternal,
+} from '@vuepress/helper'
+
+addViteOptimizeDepsInclude(bundlerOptions, app, ['vue', 'vue-router'])
+addViteOptimizeDepsExclude(bundlerOptions, app, 'packageA')
+addViteSsrNoExternal(bundlerOptions, app, ['vue', 'vue-router'])
+addViteSsrExternal(bundlerOptions, app, 'packageA')
+addViteConfig
+A function for you to add vite config
+export const addViteConfig: (
+ bundlerOptions: unknown,
+ app: App,
+ config: Record<string, unknown>,
+) => void
+import { addViteConfig } from '@vuepress/helper'
+
+addViteConfig(bundlerOptions, app, {
+ build: {
+ charset: 'utf8',
+ },
+})
+mergeViteConfig
+A function for you to merge vite config.
+WARNING
+Your users may choose to use other bundler so it's pretty bad to declare vite as deps!
+export const mergeViteConfig: (
+ defaults: Record<string, any>,
+ overrides: Record<string, any>,
+) => Record<string, any>
+import { mergeViteConfig } from '@vuepress/helper'
+
+config.viteOptions = mergeViteConfig(config.viteOptions, {
+ build: {
+ charset: 'utf8',
+ },
+})
+chainWebpack
+Chain webpack config.
+export const chainWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ chainWebpack: (
+ config: WebpackChainConfig,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { chainWebpack } from '@vuepress/helper'
+
+chainWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+configWebpack
+Config Webpack
+export const configWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ configureWebpack: (
+ config: WebpackConfiguration,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { configWebpack } from '@vuepress/helper'
+
+configWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+Get the excerpt of the page.
+export interface PageExcerptOptions {
+ /**
+ * Excerpt separator
+ *
+ * @default "<!-- more -->"
+ */
+ separator?: string
+
+ /**
+ * Length of excerpt
+ *
+ * @description Excerpt length will be the minimal possible length reaching this value
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * Tags which is considered as custom elements
+ *
+ * @description This is used to determine whether a tag is a custom element since all unknown tags are removed in excerpt.
+ */
+ isCustomElement?: (tagName: string) => boolean
+
+ /**
+ * Whether keep page title (first h1) in excerpt
+ *
+ * @default false
+ */
+ keepPageTitle?: boolean
+
+ /**
+ * Whether preserve tags like line numbers and highlight lines for code blocks
+ *
+ * @default false
+ */
+ keepFenceDom?: boolean
+}
+
+export const getPageExcerpt: (
+ app: App,
+ page: Page,
+ options?: PageExcerptOptions,
+) => string
+Get plain text of the page.
+export interface PageTextOptions {
+ /**
+ * Whether convert text to single line content
+ *
+ * @default false
+ */
+ singleLine?: boolean
+
+ /**
+ * Length of text
+ *
+ * @description Text length will be the minimal possible length reaching this value
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * Tags to be removed
+ *
+ * @description Table and code blocks are removed by default.
+ *
+ * @default ['table', 'pre']
+ */
+ removedTags?: string[]
+}
+
+export const getPageText: (
+ app: App,
+ page: Page,
+ options?: PageTextOptions,
+) => string
+
+ | Language: | +
+ |
+
| Published Date: | +
+ |
+
| Last Build Date: | +
+ |
+
| Copyright: | +
+ |
+
| + Catetory: + | +
+ |
+
|
+ |
+ Priority | +Change Frequency | +Last Updated Time | +
|---|---|---|---|
|
+ |
+
+ |
+
+ |
+
+ |
+
Props:
'tip' | 'warning' | 'danger''tip'string'''top' | 'middle' | 'bottom' | undefinedundefinedExample:
Input
- VuePress - <Badge type="tip" text="v2" vertical="top" />
+- VuePress - <Badge type="warning" text="v2" vertical="middle" />
+- VuePress - <Badge type="danger" text="v2" vertical="bottom" />
+Output
Details:
Wrapper of the CodeGroupItem components.
Props:
stringtruebooleanfalseDetails:
This component must be placed inside a CodeGroup component.
Use the active prop to set the initial active item, or the first item will be activated by default.
Example:
Input
<CodeGroup>
+ <CodeGroupItem title="pnpm">
+
+```bash:no-line-numbers
+pnpm install
+```
+
+ </CodeGroupItem>
+
+ <CodeGroupItem title="yarn">
+
+```bash:no-line-numbers
+yarn install
+```
+
+ </CodeGroupItem>
+
+ <CodeGroupItem title="npm" active>
+
+```bash:no-line-numbers
+npm install
+```
+
+ </CodeGroupItem>
+</CodeGroup>
+Output
pnpm install
+yarn install
+npm install
+WARNING
You must add an empty line between the starting tag of <CodeGroupItem> and the code fence, otherwise the code fence will not be parsed correctly by Markdown.
All content must be valid Markdown first, and then a Vue SFC.
Learn more: Cookbook > Markdown and Vue SFC
Alternatively, you can use the custom containers.
Type: string
Details:
Hostname to be deployed, e.g.: https://example.com
Type: { [path: string]: Partial<DefaultThemeLocaleData> }
Default: {}
Details:
Specify locales for i18n support.
All the options inside the Locale Config section can be used in locales.
This option will only take effect in default theme, so don't confuse with locales in Site Config.
Also see:
Config of this section can be used as normal config, and can also be used in the locales option.
Type: 'auto' | 'light' | 'dark'
Default: 'auto'
Details:
Default color mode.
If set to 'auto', the initial color mode will be automatically set according to prefers-color-scheme.
Also see:
Type: boolean
Default: true
Details:
Enable color mode switching or not.
If set to true, a button to switch color mode will be displayed in the navbar.
Also see:
Type: string
Default: /
Details:
Specify the path of the homepage.
This will be used for:
Type: false | (NavbarItem | NavbarGroup | string)[]
Default: []
Details:
Configuration of navbar.
Set to false to disable navbar.
To configure the navbar items, you can set it to a navbar array, each item of which could be a NavbarItem object, a NavbarGroup object, or a string:
NavbarItem object should have a text field and a link field, could have an optional activeMatch field.NavbarGroup object should have a text field and a children field. The children field should be a navbar array, too.NavbarItem object, using the page title as text, and the page route path as link.Example 1:
export default {
+ theme: defaultTheme({
+ navbar: [
+ // NavbarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ },
+ // NavbarGroup
+ {
+ text: 'Group',
+ children: ['/group/foo.md', '/group/bar.md'],
+ },
+ // string - page file path
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // nested group - max depth is 2
+ {
+ text: 'Group',
+ children: [
+ {
+ text: 'SubGroup',
+ children: ['/group/sub/foo.md', '/group/sub/bar.md'],
+ },
+ ],
+ },
+ // control when should the item be active
+ {
+ text: 'Group 2',
+ children: [
+ {
+ text: 'Always active',
+ link: '/',
+ // this item will always be active
+ activeMatch: '/',
+ },
+ {
+ text: 'Active on /foo/',
+ link: '/not-foo/',
+ // this item will be active when current route path starts with /foo/
+ // regular expression is supported
+ activeMatch: '^/foo/',
+ },
+ ],
+ },
+ ],
+ }),
+}
+Type: null | string
Details:
Specify the url of logo image.
The logo image will be displayed at the left end of the navbar.
Set to null to disable logo.
Example:
export default {
+ theme: defaultTheme({
+ // public file path
+ logo: '/hero.png',
+ // url
+ logo: 'https://vuejs.org/images/logo.png',
+ }),
+}
+Type: null | string
Details:
Specify the url of logo image to be used in dark mode.
You can make use of this option if you want to use different logo config in dark mode.
Set to null to disable logo in dark mode. Omit this option to use logo in dark mode.
Also see:
Type: null | string
Details:
Specify the alt text of the logo image.
If not specified, defaults to be the same as the site title.
Type: string
Details:
Specify the repository url of your project.
This will be used as the link of the repository link, which will be displayed as the last item of the navbar.
export default {
+ theme: defaultTheme({
+ // If you set it in the form of `organization/repository`
+ // we will take it as a GitHub repo
+ repo: 'vuejs/vuepress',
+ // You can also set it to a URL directly
+ repo: 'https://gitlab.com/foo/bar',
+ }),
+}
+Type: false | 'auto' | SidebarConfigArray | SidebarConfigObject
Default: 'auto'
Details:
Configuration of sidebar.
You can override this global option via sidebar frontmatter in your pages.
Set to false to disable sidebar.
If you set it to 'auto', the sidebar will be automatically generated from the page headers.
To configure the sidebar items manually, you can set this option to a sidebar array, each item of which could be a SidebarItem object or a string:
SidebarItem object should have a text field, could have an optional link field, an optional children field and an optional collapsible field. The children field should be a sidebar array. The collapsible field controls whether the item is collapsible.SidebarItem object, whose text is the page title, link is the page route path, and children is automatically generated from the page headers.If you want to set different sidebar for different sub paths, you can set this option to a sidebar object:
'heading' to automatically generate the sidebar from the page headers for just the corresponding path.Example 1:
export default {
+ theme: defaultTheme({
+ // sidebar array
+ // all pages will use the same sidebar
+ sidebar: [
+ // SidebarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ children: [
+ // SidebarItem
+ {
+ text: 'github',
+ link: 'https://github.com',
+ children: [],
+ },
+ // string - page file path
+ '/foo/bar.md',
+ ],
+ },
+ // string - page file path
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // sidebar object
+ // pages under different sub paths will use different sidebar
+ sidebar: {
+ '/guide/': [
+ {
+ text: 'Guide',
+ children: ['/guide/introduction.md', '/guide/getting-started.md'],
+ },
+ ],
+ '/reference/': 'heading',
+ },
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // collapsible sidebar
+ sidebar: {
+ '/reference/': [
+ {
+ text: 'VuePress Reference',
+ collapsible: true,
+ children: ['/reference/cli.md', '/reference/config.md'],
+ },
+ {
+ text: 'Bundlers Reference',
+ collapsible: true,
+ children: [
+ '/reference/bundler/vite.md',
+ '/reference/bundler/webpack.md',
+ ],
+ },
+ ],
+ },
+ }),
+}
+Type: number
Default: 2
Details:
Set the maximum depth of the sidebar children which are automatically generated from the page headers.
0 to disable all levels of headers.1 to include <h2> headers.2 to include <h2> and <h3> headers.The max value depends on which levels of headers you have extracted via markdown.headers.level.
The default value of markdown.headers.level is [2, 3], so the default max value of sidebarDepth is 2.
You can override this global option via sidebarDepth frontmatter in your pages.
Type: boolean
Default: true
Details:
Enable the edit this page link or not.
You can override this global option via editLink frontmatter in your pages.
Type: string
Details:
Specify the pattern of the edit this page link.
This will be used for generating the edit this page link.
If you don't set this option, the pattern will be inferred from the docsRepo option. But if your documentation repository is not hosted on a common platform, for example, GitHub, GitLab, Bitbucket, Gitee, etc., you have to set this option explicitly to make the edit this page link work.
Usage:
| Pattern | Description |
|---|---|
:repo | The docs repo url, i.e. docsRepo |
:branch | The docs repo branch, i.e. docsBranch |
:path | The path of the page source file, i.e. docsDir joins the relative path of the page file |
Example:
export default {
+ theme: defaultTheme({
+ docsRepo: 'https://gitlab.com/owner/name',
+ docsBranch: 'master',
+ docsDir: 'docs',
+ editLinkPattern: ':repo/-/edit/:branch/:path',
+ }),
+}
+The generated link will look like 'https://gitlab.com/owner/name/-/edit/master/docs/path/to/file.md'.
Type: string
Details:
Specify the repository url of your documentation source files.
This will be used for generating the edit this page link.
If you don't set this option, it will use the repo option by default. But if your documentation source files are in a different repository, you will need to set this option.
Type: string
Default: 'main'
Details:
Specify the repository branch of your documentation source files.
This will be used for generating the edit this page link.
Type: string
Default: ''
Details:
Specify the directory of your documentation source files in the repository.
This will be used for generating the edit this page link.
Type: boolean
Default: true
Details:
Enable the last updated timestamp or not.
You can override this global option via lastUpdated frontmatter in your pages. Notice that if you have already set this option to false, this feature will be disabled totally and could not be enabled in locales nor page frontmatter.
Type: boolean
Default: true
Details:
Enable the contributors list or not.
You can override this global option via contributors frontmatter in your pages. Notice that if you have already set this option to false, this feature will be disabled totally and could not be enabled in locales nor page frontmatter.
VuePress default theme is widely used by users, so it is designed to be extendable, allowing users to make their own customization with ease.
Default theme's Layout provides some slots:
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottomWith the help of them, you can add or replace content easily. Here comes an example to introduce how to extend default theme with layout slots.
Firstly, create a client config file .vuepress/client.ts:
import { defineClientConfig } from 'vuepress/client'
+import Layout from './layouts/Layout.vue'
+
+export default defineClientConfig({
+ layouts: {
+ Layout,
+ },
+})
+Next, create the .vuepress/layouts/Layout.vue, and make use of the slots that provided by the Layout of default theme:
<script setup>
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+</script>
+
+<template>
+ <ParentLayout>
+ <template #page-bottom>
+ <div class="my-footer">This is my custom page footer</div>
+ </template>
+ </ParentLayout>
+</template>
+
+<style lang="css">
+.my-footer {
+ text-align: center;
+}
+</style>
+Then the default Layout layout has been overridden by your own local layout, which will add a custom footer to every normal pages in default theme (excluding homepage):
The layout slots are useful, but sometimes you might find it's not flexible enough. Default theme also provides the ability to replace a single component.
Default theme has registered alias for every non-global components with a @theme prefix. For example, the alias of HomeFooter.vue is @theme/HomeFooter.vue.
Then, if you want to replace the HomeFooter.vue component, just override the alias in your config file .vuepress/config.ts:
import { defaultTheme } from '@vuepress/theme-default'
+import { getDirname, path } from 'vuepress/utils'
+import { defineUserConfig } from 'vuepress'
+
+const __dirname = getDirname(import.meta.url)
+
+export default defineUserConfig({
+ theme: defaultTheme(),
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+})
+Instead of extending the default theme directly in .vuepress/config.ts and .vuepress/client.ts, you can also develop your own theme extending the default theme:
import { defaultTheme, type DefaultThemeOptions } from '@vuepress/theme-default'
+import type { Theme } from 'vuepress/core'
+import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export const childTheme = (options: DefaultThemeOptions): Theme => {
+ return {
+ name: 'vuepress-theme-child',
+ extends: defaultTheme(options),
+
+ // override layouts in child theme's client config file
+ // notice that you would build ts to js before publishing to npm,
+ // so this should be the path to the js file
+ clientConfigFile: path.resolve(__dirname, './client.js'),
+
+ // override component alias
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+ }
+}
+Frontmatter in this section will take effect in all types of pages.
Type: boolean
Details:
Provided by @vuepress/plugin-external-link-icon.
Also see:
Type: boolean
Details:
Show navbar on this page or not.
If you disable navbar in theme config, this frontmatter will not take effect.
Also see:
Type: string
Details:
Add extra class name to this page.
Example:
---
+pageClass: custom-page-class
+---
+Then you can customize styles of this page in .vuepress/styles/index.scss file:
.theme-container.custom-page-class {
+ /* page styles */
+}
+Frontmatter in this section will only take effect in home pages.
Type: boolean
Details:
Specify whether the page is homepage or a normal page.
If you don't set this frontmatter or set it to false, the page would be a normal page.
Example:
---
+home: true
+---
+Type: string
Details:
Specify the url of the hero image.
Example:
---
+# public file path
+heroImage: /images/hero.png
+# url
+heroImage: https://vuejs.org/images/logo.png
+---
+Type: string
Details:
Specify the url of hero image to be used in dark mode.
You can make use of this option if you want to use different heroImage config in dark mode.
Also see:
Type: string
Details:
Specify the alt attribute of the hero image.
This will fallback to the heroText.
Type: number
Default: 280
Details:
Specify the height attribute of the hero <img> tag.
You may need to reduce this value if the height of your hero image is less than the default value.
Notice that the height is also constrained by CSS. This attribute is to reduce Cumulative Layout Shift (CLS) that caused by the loading of the hero image.
Type: string | null
Details:
Specify the the hero text.
This will fallback to the site title.
Set to null to disable hero text.
Type: string | null
Details:
Specify the the tagline.
This will fallback to the site description.
Set to null to disable tagline.
Array<{
+ text: string
+ link: string
+ type?: 'primary' | 'secondary'
+}>
+Details:
Configuration of the action buttons.
Example:
---
+actions:
+ - text: Get Started
+ link: /guide/getting-started.html
+ type: primary
+ - text: Introduction
+ link: /guide/introduction.html
+ type: secondary
+---
+Array<{
+ title: string
+ details: string
+}>
+Details:
Configuration of the features list.
Example:
---
+features:
+ - title: Simplicity First
+ details: Minimal setup with markdown-centered project structure helps you focus on writing.
+ - title: Vue-Powered
+ details: Enjoy the dev experience of Vue, use Vue components in markdown, and develop custom themes with Vue.
+ - title: Performant
+ details: VuePress generates pre-rendered static HTML for each page, and runs as an SPA once a page is loaded.
+---
+Type: string
Details:
Specify the content of the footer.
Type: boolean
Details:
Allow HTML in footer or not.
If you set it to true, the footer will be treated as HTML code.
Frontmatter in this section will only take effect in normal pages.
Type: boolean
Details:
Enable the edit this page link in this page or not.
Also see:
Type: string
Details:
Specify the pattern of the edit this page link of this page.
Also see:
Type: boolean
Details:
Enable the last updated timestamp in this page or not.
Also see:
Type: boolean
Details:
Enable the contributors list in this page or not.
Also see:
Type: false | 'auto' | SidebarConfigArray | SidebarConfigObject
Details:
Configure the sidebar of this page.
Also see:
Type: number
Details:
Configure the sidebar depth of this page.
Also see:
Type: NavLink | string
Details:
Specify the link of the previous page.
If you don't set this frontmatter, the link will be inferred from the sidebar config.
To configure the prev link manually, you can set this frontmatter to a NavLink object or a string:
NavLink object should have a text field and a link field.NavLink object, whose text is the page title, and link is the page route path.Example:
---
+# NavLink
+prev:
+ text: Get Started
+ link: /guide/getting-started.html
+
+# NavLink - external url
+prev:
+ text: GitHub
+ link: https://github.com
+
+# string - page file path
+prev: /guide/getting-started.md
+
+# string - page file relative path
+prev: ../../guide/getting-started.md
+---
+Type: NavLink | string
Details:
Specify the link of the next page.
If you don't set this frontmatter, the link will be inferred from the sidebar config.
The type is the same as prev frontmatter.
Install @vuepress/theme-default :
npm install @vuepress/theme-default@next
+import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ // set theme config here
+ }),
+}
+These options configure locale-related texts.
If your site is served in a different language besides English, you should set these options per locale to provide translations.
Type: string
Details:
Specify the repository label of your project.
This will be used as the text of the repository link, which will be displayed as the last item of the navbar.
If you don't set this option explicitly, it will be automatically inferred from the repo option.
Type: string
Details:
Specify the text of the select language menu.
The select language menu will appear next to the repository button in the navbar when you set multiple locales in your site config.
Type: string
Details:
Specify the aria-label attribute of the select language menu.
This is mainly for a11y purpose.
Type: string
Details:
Specify the name of the language of a locale.
This option will only take effect inside the locales of your theme config. It will be used as the language name of the locale, which will be displayed in the select language menu.
Example:
export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+ theme: defaultTheme({
+ locales: {
+ '/': {
+ selectLanguageName: 'English',
+ },
+ '/zh/': {
+ selectLanguageName: '简体中文',
+ },
+ },
+ }),
+}
+Type: null | string
Details:
aria-label value for main navigation in navbar.
Type: null | string
Details:
aria-label value for next/previous page navigation.
Type: string
Default: 'Edit this page'
Details:
Specify the text of the edit this page link.
Type: string
Default: 'Last Updated'
Details:
Specify the text of the last updated timestamp label.
Type: string
Default: 'Contributors'
Details:
Specify the text of the contributors list label.
Type: string
Default: 'TIP'
Details:
Specify the default title of the tip custom containers.
Type: string
Default: 'WARNING'
Details:
Specify the default title of the warning custom containers.
Type: string
Default: 'DANGER'
Details:
Specify the default title of the danger custom containers.
Type: string[]
Default: ['Not Found']
Details:
Specify the messages of the 404 page.
The message will be randomly picked from the array when users enter the 404 page.
Type: string
Default: 'Back to home'
Details:
Specify the text of the back to home link in the 404 page.
Type: string
Default: 'open in new window'
Details:
Specify the sr-only text of the ExternalLinkIcon.
This is mainly for a11y purpose.
Also see:
Type: string
Default: 'toggle color mode'
Details:
Title text for the color mode toggle button.
This is mainly for a11y purpose.
Also see:
Type: string
Default: 'toggle sidebar'
Details:
Title text for sidebar toggle button.
This is mainly for a11y purpose.
Type: string
Default: 'Prev'
Details:
Text for the previous page navigation button.
Type: string
Default: 'Next'
Details:
Text for the next page navigation button.
Usage:
::: <type> [title]
+[content]
+:::
+The type is required, and the title and content are optional.
Supported type :
tipwarningdangerdetailscode-groupcode-group-itemExample 1 (default title):
Input
::: tip
+This is a tip
+:::
+
+::: warning
+This is a warning
+:::
+
+::: danger
+This is a dangerous warning
+:::
+
+::: details
+This is a details block
+:::
+Output
TIP
This is a tip
WARNING
This is a warning
DANGER
This is a dangerous warning
This is a details block
Input
::: danger STOP
+Danger zone, do not proceed
+:::
+
+::: details Click me to view the code
+
+```ts
+console.log('Hello, VuePress!')
+```
+
+:::
+Output
STOP
Danger zone, do not proceed
console.log('Hello, VuePress!')
+Input
:::: code-group
+::: code-group-item FOO
+
+```ts
+const foo = 'foo'
+```
+
+:::
+
+::: code-group-item BAR
+
+```ts
+const bar = 'bar'
+```
+
+:::
+::::
+Output
const foo = 'foo'
+const bar = 'bar'
+You can configure the plugins that used by default theme with themePlugins.
Default theme is using some plugins by default. You can disable a plugin if you really do not want to use it. Make sure you understand what the plugin is for before disabling it.
import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ themePlugins: {
+ // customize theme plugins here
+ },
+ }),
+}
+Type: boolean
Default: true
Details:
Enable @vuepress/plugin-active-header-links or not.
Type: BackToTopPluginOptions | boolean
Default: true
Details:
Enable @vuepress/plugin-back-to-top or not.
Object value is supported as plugin options.
Type: Record<ContainerType, boolean>
Details:
Enable custom containers that powered by @vuepress/plugin-container or not.
ContainerType type is:
tipwarningdangerdetailscodeGroupcodeGroupItemAlso see:
Type: CopyCodePluginOptions | boolean
Default: true
Details:
Enable @vuepress/plugin-copy-code or not.
Object value is supported as plugin options.
Type: boolean
Default: true
Details:
Enable @vuepress/plugin-external-link-icon or not.
Type: boolean
Default: true
Details:
Enable @vuepress/plugin-git or not.
Type: LinksCheckPluginOptions | boolean
Default: true
Details:
Enable @vuepress/plugin-links-check or not.
Type: boolean
Default: true
Details:
Enable @vuepress/plugin-medium-zoom or not.
Type: boolean
Default: true
Details:
Enable @vuepress/plugin-nprogress or not.
Type: boolean
Default: true
Details:
Enable @vuepress/plugin-prismjs or not.
Type: SeoPluginOptions | boolean
Default: true
Details:
Enable @vuepress/plugin-seo or not.
Object value is supported as plugin options.
Type: SitemapPluginOptions | boolean
Default: true
Details:
Enable @vuepress/plugin-sitemap or not.
Object value is supported as plugin options.
The default theme uses SASS as the CSS pre-processor.
Users can customize style variables via a palette file, and add extra styles via a style file.
The path of the palette file is .vuepress/styles/palette.scss.
You can make use of it to override predefined SASS variables of the default theme.
// responsive breakpoints
+$MQNarrow: 959px !default;
+$MQMobile: 719px !default;
+$MQMobileNarrow: 419px !default;
+The path of the style file is .vuepress/styles/index.scss.
You can add extra styles here, or override the default styles:
:root {
+ scroll-behavior: smooth;
+}
+You can also make use of it to override predefined CSS variables of the default theme.
:root {
+ // brand colors
+ --c-brand: #3eaf7c;
+ --c-brand-light: #4abf8a;
+
+ // background colors
+ --c-bg: #ffffff;
+ --c-bg-light: #f3f4f5;
+ --c-bg-lighter: #eeeeee;
+ --c-bg-dark: #ebebec;
+ --c-bg-darker: #e6e6e6;
+ --c-bg-navbar: var(--c-bg);
+ --c-bg-sidebar: var(--c-bg);
+ --c-bg-arrow: #cccccc;
+
+ // text colors
+ --c-text: #2c3e50;
+ --c-text-accent: var(--c-brand);
+ --c-text-light: #3a5169;
+ --c-text-lighter: #4e6e8e;
+ --c-text-lightest: #6a8bad;
+ --c-text-quote: #999999;
+
+ // border colors
+ --c-border: #eaecef;
+ --c-border-dark: #dfe2e5;
+
+ // custom container colors
+ --c-tip: #42b983;
+ --c-tip-bg: var(--c-bg-light);
+ --c-tip-title: var(--c-text);
+ --c-tip-text: var(--c-text);
+ --c-tip-text-accent: var(--c-text-accent);
+ --c-warning: #ffc310;
+ --c-warning-bg: #fffae3;
+ --c-warning-bg-light: #fff3ba;
+ --c-warning-bg-lighter: #fff0b0;
+ --c-warning-border-dark: #f7dc91;
+ --c-warning-details-bg: #fff5ca;
+ --c-warning-title: #f1b300;
+ --c-warning-text: #746000;
+ --c-warning-text-accent: #edb100;
+ --c-warning-text-light: #c1971c;
+ --c-warning-text-quote: #ccab49;
+ --c-danger: #f11e37;
+ --c-danger-bg: #ffe0e0;
+ --c-danger-bg-light: #ffcfde;
+ --c-danger-bg-lighter: #ffc9c9;
+ --c-danger-border-dark: #f1abab;
+ --c-danger-details-bg: #ffd4d4;
+ --c-danger-title: #ed1e2c;
+ --c-danger-text: #660000;
+ --c-danger-text-accent: #bd1a1a;
+ --c-danger-text-light: #b5474d;
+ --c-danger-text-quote: #c15b5b;
+ --c-details-bg: #eeeeee;
+
+ // badge component colors
+ --c-badge-tip: var(--c-tip);
+ --c-badge-warning: #ecc808;
+ --c-badge-warning-text: var(--c-bg);
+ --c-badge-danger: #dc2626;
+ --c-badge-danger-text: var(--c-bg);
+
+ // code group colors
+ --c-code-group-tab-title: rgba(255, 255, 255, 0.9);
+ --c-code-group-tab-bg: var(--code-bg-color);
+ --c-code-group-tab-outline: var(var(--c-code-group-tab-title));
+ --c-code-group-tab-active-border: var(--c-brand);
+
+ // transition vars
+ --t-color: 0.3s ease;
+ --t-transform: 0.3s ease;
+
+ // code blocks vars
+ --code-bg-color: #282c34;
+ --code-hl-bg-color: rgba(0, 0, 0, 0.66);
+ --code-ln-color: #9e9e9e;
+ --code-ln-wrapper-width: 3.5rem;
+
+ // font vars
+ --font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen,
+ Ubuntu, Cantarell, 'Fira Sans', 'Droid Sans', 'Helvetica Neue', sans-serif;
+ --font-family-code: Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono', monospace;
+
+ // layout vars
+ --navbar-height: 3.6rem;
+ --navbar-padding-v: 0.7rem;
+ --navbar-padding-h: 1.5rem;
+ --sidebar-width: 20rem;
+ --sidebar-width-mobile: calc(var(--sidebar-width) * 0.82);
+ --content-width: 740px;
+ --homepage-width: 960px;
+}
+
+// plugin-back-to-top
+.vp-back-to-top-button {
+ --back-to-top-color: var(--c-brand);
+ --back-to-top-color-hover: var(--c-brand-light);
+ --back-to-top-bg-color: var(--c-bg);
+}
+
+// plugin-catalog
+.vp-catalog-wrapper {
+ --catalog-bg-color: var(--c-bg);
+ --catalog-bg-secondary-color: var(--c-bg-dark);
+ --catalog-border-color: var(--c-border);
+ --catalog-active-color: var(--c-brand);
+ --catalog-hover-color: var(--c-brand-light);
+}
+
+// plugin-comment
+.waline-wrapper {
+ --waline-bg-color: var(--c-bg);
+ --waline-bg-color-light: var(--c-bg-light);
+ --waline-text-color: var(--c-color);
+ --waline-border: 1px solid var(--c-border);
+ --waline-border-color: var(--c-border);
+ --waline-theme-color: var(--c-brand);
+ --waline-active-color: var(--c-brand-light);
+}
+
+// plugin-docsearch
+.DocSearch {
+ --docsearch-primary-color: var(--c-brand);
+ --docsearch-text-color: var(--c-text);
+ --docsearch-highlight-color: var(--c-brand);
+ --docsearch-muted-color: var(--c-text-quote);
+ --docsearch-container-background: rgba(9, 10, 17, 0.8);
+ --docsearch-modal-background: var(--c-bg-light);
+ --docsearch-searchbox-background: var(--c-bg-lighter);
+ --docsearch-searchbox-focus-background: var(--c-bg);
+ --docsearch-searchbox-shadow: inset 0 0 0 2px var(--c-brand);
+ --docsearch-hit-color: var(--c-text-light);
+ --docsearch-hit-active-color: var(--c-bg);
+ --docsearch-hit-background: var(--c-bg);
+ --docsearch-hit-shadow: 0 1px 3px 0 var(--c-border-dark);
+ --docsearch-footer-background: var(--c-bg);
+}
+
+// plugin-external-link-icon
+.external-link-icon {
+ --external-link-icon-color: var(--c-text-quote);
+}
+
+// plugin-medium-zoom
+.medium-zoom-overlay {
+ --medium-zoom-bg-color: var(--c-bg);
+}
+
+// plugin-nprogress
+#nprogress {
+ --nprogress-color: var(--c-brand);
+}
+
+// plugin-photo-swipe
+body {
+ --photo-swipe-bullet: var(--c-bg);
+ --photo-swipe-bullet-active: var(--c-brand);
+}
+
+// plugin-pwa-popup
+body {
+ --pwa-text-color: var(--c-text);
+ --pwa-bg-color: var(--c-bg);
+ --pwa-border-color: var(--c-brand);
+ --pwa-btn-text-color: var(--c-bg);
+ --pwa-btn-bg-color: var(--c-brand);
+ --pwa-btn-hover-bg-color: var(--c-brand-light);
+}
+
+// plugin-redirect
+.language-modal-mask {
+ --redirect-bg-color: var(--c-bg);
+ --redirect-bg-color-light: var(--c-bg-light);
+ --redirect-bg-color-lighter: var(--c-bg-lighter);
+ --redirect-text-color: var(--c-text);
+ --redirect-primary-color: var(--c-brand);
+ --redirect-primary-hover-color: var(--c-brand-light);
+ --redirect-primary-text-color: var(--c-bg);
+}
+
+// plugin-search
+.search-box {
+ --search-bg-color: var(--c-bg);
+ --search-accent-color: var(--c-brand);
+ --search-text-color: var(--c-text);
+ --search-border-color: var(--c-border);
+
+ --search-item-text-color: var(--c-text-lighter);
+ --search-item-focus-bg-color: var(--c-bg-light);
+}
+html.dark {
+ // brand colors
+ --c-brand: #3aa675;
+ --c-brand-light: #349469;
+
+ // background colors
+ --c-bg: #22272e;
+ --c-bg-light: #2b313a;
+ --c-bg-lighter: #262c34;
+ --c-bg-dark: #343b44;
+ --c-bg-darker: #37404c;
+
+ // text colors
+ --c-text: #adbac7;
+ --c-text-light: #96a7b7;
+ --c-text-lighter: #8b9eb0;
+ --c-text-lightest: #8094a8;
+
+ // border colors
+ --c-border: #3e4c5a;
+ --c-border-dark: #34404c;
+
+ // custom container colors
+ --c-tip: #318a62;
+ --c-warning: #e0ad15;
+ --c-warning-bg: #2d2f2d;
+ --c-warning-bg-light: #423e2a;
+ --c-warning-bg-lighter: #44442f;
+ --c-warning-border-dark: #957c35;
+ --c-warning-details-bg: #39392d;
+ --c-warning-title: #fdca31;
+ --c-warning-text: #d8d96d;
+ --c-warning-text-accent: #ffbf00;
+ --c-warning-text-light: #ddb84b;
+ --c-warning-text-quote: #ccab49;
+ --c-danger: #fc1e38;
+ --c-danger-bg: #39232c;
+ --c-danger-bg-light: #4b2b35;
+ --c-danger-bg-lighter: #553040;
+ --c-danger-border-dark: #a25151;
+ --c-danger-details-bg: #482936;
+ --c-danger-title: #fc2d3b;
+ --c-danger-text: #ea9ca0;
+ --c-danger-text-accent: #fd3636;
+ --c-danger-text-light: #d9777c;
+ --c-danger-text-quote: #d56b6b;
+ --c-details-bg: #323843;
+
+ // badge component colors
+ --c-badge-warning: var(--c-warning);
+ --c-badge-warning-text: #3c2e05;
+ --c-badge-danger: var(--c-danger);
+ --c-badge-danger-text: #401416;
+
+ // code blocks vars
+ --code-hl-bg-color: #363b46;
+}
+
+// plugin-docsearch
+html.dark .DocSearch {
+ --docsearch-logo-color: var(--c-text);
+ --docsearch-modal-shadow: inset 1px 1px 0 0 #2c2e40, 0 3px 8px 0 #000309;
+ --docsearch-key-shadow: inset 0 -2px 0 0 #282d55, inset 0 0 1px 1px #51577d,
+ 0 2px 2px 0 rgba(3, 4, 9, 0.3);
+ --docsearch-key-gradient: linear-gradient(-225deg, #444950, #1c1e21);
+ --docsearch-footer-shadow: inset 0 1px 0 0 rgba(73, 76, 106, 0.5),
+ 0 -4px 8px 0 rgba(0, 0, 0, 0.2);
+}
+
+// plugin-pwa
+html.dark body {
+ --pwa-shadow-color: rgb(0 0 0 / 30%);
+ --pwa-content-color: #ccc;
+ --pwa-content-light-color: #999;
+}
+Check whether a component is registered globally.
TIP
setup scope, you need to pass the app instance as the second parameter.export const hasGlobalComponent: (name: string, app?: App) => boolean
+// if you globally register `<my-component>`
+hasGlobalComponent('MyComponent') // true
+hasGlobalComponent('my-component') // true
+
+hasGlobalComponent('MyComponent2') // false
+Get current locale config from locales settings.
export const useLocaleConfig: <T extends LocaleData>(
+ localesConfig: RequiredLocaleConfig<T>,
+) => ComputedRef<T>
+const localesCOnfig = {
+ '/': 'Title',
+ '/zh/': '标题',
+}
+
+const locale = useLocaleConfig(localesConfig)
+
+// under `/page`
+locale.value // 'Title'
+
+// under `/zh/page`
+locale.value // '标题'
+This package is a helper utility for VuePress developers.
@vuepress/helper: Node.js side helper utilities.
@vuepress/helper/client: Client side helper utilities.
@vuepress/helper/shared: Utilities that are both available at Node.js side or Client.
Bundler function is for appending or modifying bundler options in theme and plugins.
All functions should be called in extendsBundlerOptions lifecycle hook.
TIP
We are omitting that in examples. The actual code should be like this:
// import functions you need
+import { addCustomElement } from '@vuepress/helper'
+
+export const yourPlugin = {
+ // ...
+ extendsBundlerOptions: (bundlerOptions, app) => {
+ // add them here
+ addCustomElement(bundlerOptions, app, 'my-custom-element')
+ },
+}
+Get current bundler name.
export const getBundlerName: (app: App) => string
+// @vuepress/bundler-vite
+getBundleName(app) === 'vite' // true
+// @vuepress/bundler-webpack
+getBundleName(app) === 'webpack' // true
+Add a custom element declaration to the current bundler.
/**
+ * Add tags as customElement
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param customElements tags recognized as custom element
+ */
+export const addCustomElement = (
+ bundlerOptions: unknown,
+ app: App,
+ customElement: string[] | string | RegExp
+) => void;
+import { addCustomElement } from '@vuepress/helper'
+
+addCustomElement(bundlerConfig, app, 'my-custom-element')
+addCustomElement(bundlerOptions, app, [
+ 'custom-element1',
+ 'custom-element2',
+ // all tags start with `math-`
+ /^math-/,
+])
+Provides contents for specific path in dev server.
export interface DevServerOptions {
+ /**
+ * Path to be responded
+ */
+ path: string;
+ /**
+ * Respond function
+ */
+ response: (request?: IncomingMessage) => Promise<string | Buffer>;
+
+ /**
+ * error msg
+ */
+ errMsg?: string;
+}
+
+/**
+ * Handle specific path when running VuePress Dev Server
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param path Path to be responded
+ * @param response respond function
+ * @param errMsg error msg
+ */
+export const customizeDevServer: (
+ bundlerOptions: unknown,
+ app: App,
+ {
+ errMsg:"The server encountered an error",
+ response: responseHandler,
+ path,
+ }: CustomServerOptions
+) => void;
+import { useCustomDevServer } from '@vuepress/helper'
+
+// handle `/api/` path
+useCustomDevServer(bundlerOptions, app, {
+ path: '/api/',
+ response: async () => getData(),
+ errMsg: 'Unexpected api error',
+})
+addViteOptimizeDepsInclude
Add modules to Vite optimizeDeps.include list
TIP
If a package meets one of the following conditions, you should consider adding it here.
import()addViteOptimizeDepsExclude
Add modules to Vite optimizeDeps.exclude list
If a package and its dependencies are all pure ESM packages, you should consider adding it here.
addViteSsrExternal
Add modules to Vite ssr.external list
If a package is a pure ESM package and does not use aliases or define variables, you should consider adding it here.
addViteSsrNoExternal
Add modules to Vite ssr.noExternal list
If an alias or define is used within a package, you must add it here.
/**
+ * Add modules to Vite `optimizeDeps.include` list
+ */
+export const addViteOptimizeDepsInclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `optimizeDeps.exclude` list
+ */
+export const addViteOptimizeDepsExclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.external` list
+ */
+export const addViteSsrExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.noExternal` list
+ */
+export const addViteSsrNoExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+import {
+ addViteOptimizeDepsInclude,
+ addViteOptimizeDepsExclude,
+ addViteSsrExternal,
+ addViteSsrNoExternal,
+} from '@vuepress/helper'
+
+addViteOptimizeDepsInclude(bundlerOptions, app, ['vue', 'vue-router'])
+addViteOptimizeDepsExclude(bundlerOptions, app, 'packageA')
+addViteSsrNoExternal(bundlerOptions, app, ['vue', 'vue-router'])
+addViteSsrExternal(bundlerOptions, app, 'packageA')
+addViteConfig
A function for you to add vite config
export const addViteConfig: (
+ bundlerOptions: unknown,
+ app: App,
+ config: Record<string, unknown>,
+) => void
+import { addViteConfig } from '@vuepress/helper'
+
+addViteConfig(bundlerOptions, app, {
+ build: {
+ charset: 'utf8',
+ },
+})
+mergeViteConfig
A function for you to merge vite config.
WARNING
Your users may choose to use other bundler so it's pretty bad to declare vite as deps!
export const mergeViteConfig: (
+ defaults: Record<string, any>,
+ overrides: Record<string, any>,
+) => Record<string, any>
+import { mergeViteConfig } from '@vuepress/helper'
+
+config.viteOptions = mergeViteConfig(config.viteOptions, {
+ build: {
+ charset: 'utf8',
+ },
+})
+chainWebpack
Chain webpack config.
export const chainWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ chainWebpack: (
+ config: WebpackChainConfig,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { chainWebpack } from '@vuepress/helper'
+
+chainWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+configWebpack
Config Webpack
export const configWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ configureWebpack: (
+ config: WebpackConfiguration,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { configWebpack } from '@vuepress/helper'
+
+configWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+These functions generate common information for your pages.
Get the excerpt of the page.
export interface PageExcerptOptions {
+ /**
+ * Excerpt separator
+ *
+ * @default "<!-- more -->"
+ */
+ separator?: string
+
+ /**
+ * Length of excerpt
+ *
+ * @description Excerpt length will be the minimal possible length reaching this value
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * Tags which is considered as custom elements
+ *
+ * @description This is used to determine whether a tag is a custom element since all unknown tags are removed in excerpt.
+ */
+ isCustomElement?: (tagName: string) => boolean
+
+ /**
+ * Whether keep page title (first h1) in excerpt
+ *
+ * @default false
+ */
+ keepPageTitle?: boolean
+
+ /**
+ * Whether preserve tags like line numbers and highlight lines for code blocks
+ *
+ * @default false
+ */
+ keepFenceDom?: boolean
+}
+
+export const getPageExcerpt: (
+ app: App,
+ page: Page,
+ options?: PageExcerptOptions,
+) => string
+Get plain text of the page.
export interface PageTextOptions {
+ /**
+ * Whether convert text to single line content
+ *
+ * @default false
+ */
+ singleLine?: boolean
+
+ /**
+ * Length of text
+ *
+ * @description Text length will be the minimal possible length reaching this value
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * Tags to be removed
+ *
+ * @description Table and code blocks are removed by default.
+ *
+ * @default ['table', 'pre']
+ */
+ removedTags?: string[]
+}
+
+export const getPageText: (
+ app: App,
+ page: Page,
+ options?: PageTextOptions,
+) => string
+The following functions are available on both Node.js and Client.
Encode/decode and zip/unzip data.
This is useful in markdown plugins when you want to encode string content and pass it to the component through props.
You may simply achieve this with encodeURIComponent and decodeURIComponent, but it can be very large if the content contains lots of special characters.
So we provide encodeData and decodeData to zip and encode content.
export const encodeData: (
+ data: string,
+ level: DeflateOptions['level'] = 6,
+) => string
+
+export const decodeData: (compressed: string) => string
+const content = `
+{
+ "type": "bar",
+ "data": {
+ "labels": ["Red", "Blue", "Yellow", "Green", "Purple", "Orange"],
+ "datasets": [
+ {
+ "label": "# of Votes",
+ "data": [12, 19, 3, 5, 2, 3],
+ "backgroundColor": [
+ "rgba(255, 99, 132, 0.2)",
+ "rgba(54, 162, 235, 0.2)",
+ "rgba(255, 206, 86, 0.2)",
+ "rgba(75, 192, 192, 0.2)",
+ "rgba(153, 102, 255, 0.2)",
+ "rgba(255, 159, 64, 0.2)"
+ ],
+ "borderColor": [
+ "rgba(255, 99, 132, 1)",
+ "rgba(54, 162, 235, 1)",
+ "rgba(255, 206, 86, 1)",
+ "rgba(75, 192, 192, 1)",
+ "rgba(153, 102, 255, 1)",
+ "rgba(255, 159, 64, 1)"
+ ],
+ "borderWidth": 1
+ }
+ ]
+ },
+ "options": {
+ "scales": {
+ "y": {
+ "beginAtZero": true
+ }
+ }
+ }
+}
+`
+
+const prop = encodeData(content) // "eJyNUsFOwzAMve8rrHABKZqWlg5WxAE4cARxAMHEIV1NmQhNlaaCCe3fcdKtW0sLWGpjxy/v+UV512mlcIyfhTa2hHP4GgHYVYExsEQaxqlMpZWxbwAomaAqY5izO0wZB3apKnTrIyqlP1x2bRBzl9xWplC+eWNkniF7dmw1X4nWsfgaNtwNP2kfgH6Be22x9CPUUQ8yFwEHMeMQcog4UBFuiF0kcvGWGV3l6ZVW2uw0XDCTJfIwiOjYjAhESIcn4+BoT2MLio6pP6V+EBJ6AOSZgsmUwyl9A6ATwoiZn3lYTkTkRkycnuP8TU9ENPqUxuuA9i9BmxTNPy9A/G2/F9I23wtpW++FdIwPKzW2W5Afph+WqX2NQWz313XicT7XhV3qnB5f/ejKhVTYVACrXUqUmC3zC/uERsdgTYUdVr/Qb302+gZxe7S/"
+
+decodeData(prop) // will be the original content
+
+// if you use `encodeURIComponent`, it will be much longer
+encodeURIComponent(content) // '%0A%7B%0A%20%20%22type%22%3A%20%22bar%22%2C%0A%20%20%22data%22%3A%20%7B%0A%20%20%20%20%22labels%22%3A%20%5B%22Red%22%2C%20%22Blue%22%2C%20%22Yellow%22%2C%20%22Green%22%2C%20%22Purple%22%2C%20%22Orange%22%5D%2C%0A%20%20%20%20%22datasets%22%3A%20%5B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%22label%22%3A%20%22%23%20of%20Votes%22%2C%0A%20%20%20%20%20%20%20%20%22data%22%3A%20%5B12%2C%2019%2C%203%2C%205%2C%202%2C%203%5D%2C%0A%20%20%20%20%20%20%20%20%22backgroundColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%200.2)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%201)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderWidth%22%3A%201%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%0A%20%20%7D%2C%0A%20%20%22options%22%3A%20%7B%0A%20%20%20%20%22scales%22%3A%20%7B%0A%20%20%20%20%20%20%22y%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22beginAtZero%22%3A%20true%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A'
+isDef(x): Check if x is defined.isBoolean(x): Check if x is a boolean.isString(x): Check if x is a string.isNumber(x): Check if x is a number.isPlainObject(x): Check if x is a plain object.isArray(x): Check if x is an array.isFunction(x): Check if x is a function.isRegExp(x): Check if x is a regular expression.startsWith(a, b): Check if string a starts with string b.endsWith(a, b): Check if string a ends with string b.Return false if a is not a string.
keys(x): Return an array of keys of object x.
values(x): Return an array of values of object x.
entries(x): Convert object x to an array of key-value pairs.
fromEntries(x): Convert an array of key-value pairs x to an object.
deepAssign(x, y, ...): A deep version of Object.assign.
// or @vuepress/helper/client
+import { deepAssign } from '@vuepress/helper'
+
+const defaultOptions = {
+ optionA: {
+ optionA1: 'defaultOptionA1',
+ optionA2: 'defaultOptionA2',
+ optionA3: 'defaultOptionA3',
+ },
+ optionB: true,
+ optionC: 'optionC',
+}
+
+const userOptions = {
+ optionA: {
+ optionA1: 'optionA1',
+ optionA2: 'optionA2',
+ },
+ optionB: false,
+}
+
+deepAssign(defaultOptions, userOptions)
+// {
+// optionA: {
+// optionA1: "optionA1",
+// optionA2: "optionA2",
+// optionA3: "defaultOptionA3",
+// },
+// optionB: false,
+// optionC: "optionC",
+// }
+getDate(x): Convert input x to a date. It can support Date, timestamp, and date string. The support degree of date string depends on the Date.parse support degree of the environment. Return null when it cannot be converted to a date.
getDate('2021-01-01') // a Date object represents 2021-01-01
+getDate(1609459200000) // a Date object represents 2021-01-01
+getDate('2021-01-01T00:00:00.000Z') // a Date object represents 2021-01-01
+getDate('2021/01/01') // a Date object represents 2021-01-01 (might be null in some browsers)
+getDate('invalid date') // null
+getDate(undefined) // null
+getDate(-32) // null
+dateSorter: Sort the values that can be converted to dates from new to old, and the values that cannot be converted to dates will be at the end.
const arr = [
+ '2020-01-01',
+ 1609459200000,
+ '2022-01-01T00:00:00.000Z',
+ '2023/01/01',
+ 'invalid date',
+ undefined,
+ -32,
+]
+
+arr.sort(dateSorter)
+// [
+// '2023/01/01',
+// '2022-01-01T00:00:00.000Z',
+// 1609459200000,
+// '2020-01-01',
+// 'invalid date',
+// undefined,
+// -32,
+// ]
+isLinkHttp(x): Check if x is a valid HTTP URL.isLinkWithProtocol(x): Check if x is a valid URL with protocol.isLinkExternal(x): Check if x is a valid external URL.isLinkAbsolute(x): Check if x is a valid absolute URL.ensureEndingSlash(x): Ensure x ends with a slash.ensureLeadingSlash(x): Ensure x starts with a slash.removeEndingSlash(x): Ensure x does not end with a slash.removeLeadingSlash(x): Ensure x does not start with a slash.类型: (page: Page) => Record<string, unknown>
必填: 否
+参考:
+ +详情：
+获取文章信息的函数。
+获取到的信息会被稍后注入至路由元数据，以便你可以在客户端中通过组合式 API 获取。
+类型: (page: Page) => boolean
默认值: (page) => Boolean(page.filePathRelative) && !page.frontmatter.home
参考:
+ +详情：
+页面过滤器，此函数用于鉴别页面是否作为文章。
+默认情况下，所有从 Markdown 源文件中生成的非主页页面，会被作为文章。
+类型: BlogCategoryOptions[]
必填: 否
+详情：
+ +详情：
+博客分类配置，详见 博客分类配置。
+类型: BlogTypeOptions[]
必填: 否
+参考：
+ +详情：
+博客分类配置，详见 博客类型配置。
+(name: string) => string(name) => name.replace(/ _/g, '-').replace(/[:?*|\\/<>]/g, "").toLowerCase()booleantruestring类型: (page: Page) => Record<string, unknown>
必填: 否
+参考:
+ +详情：
+获取文章信息的函数。
+获取到的信息会被稍后注入至路由元数据，以便你可以在客户端中通过组合式 API 获取。
+类型: (page: Page) => boolean
默认值: (page) => Boolean(page.filePathRelative) && !page.frontmatter.home
参考:
+ +详情：
+页面过滤器，此函数用于鉴别页面是否作为文章。
+默认情况下，所有从 Markdown 源文件中生成的非主页页面，会被作为文章。
+类型: BlogCategoryOptions[]
必填: 否
+详情：
+ +详情：
+博客分类配置，详见 博客分类配置。
+类型: BlogTypeOptions[]
必填: 否
+参考：
+ +详情：
+博客分类配置，详见 博客类型配置。
+(name: string) => string(name) => name.replace(/ _/g, '-').replace(/[:?*|\\/<>]/g, "").toLowerCase()booleantruestring<!-- more -->类型: number
默认值: 300
参考：
+详情：
+自动生成的摘要的长度。
+提示
+摘要的长度会尽可能的接近这个值。如果设置为 0，意味着不自动生成摘要。
类型: (page: Page) => boolean
默认值: filter 选项
参考：
+详情： +页面过滤器，此函数用于鉴别插件是否需要生成摘要。
+提示
+你可以使用此函数来跳过你不需要生成摘要的页面。例如：如果用户在 frontmatter 中设置了 excerpt 或 description，你可能希望直接使用它们。
类型: (tagName: string) => boolean
默认值: () => false
参考：
+详情： +被认为是自定义元素的标签。
+用于判断一个标签是否是自定义元素，因为在摘要中，所有的未知标签都会被移除。
+类型: string
默认值: "_blog"
详情： +注入文章信息至路由元数据时使用的键名。
+提示
+设置为空字符串会直接注入路由元数据 (而不是一个键下)。
+类型: boolean
默认值: 是否使用 --debug 标记
详情： +是否在开发服务器中启用实时热重载。
+致主题开发者
+默认情况下它是禁用的，因为它确实会对具有很多分类和类别的站点产生性能影响，并且在编辑 Markdown 时会减慢热重载的速度。
+如果用户正在添加或组织类别或标签，你可以告诉他们启用此功能，其余的时间最好禁用它。
+此外，你可以尝试检测用户项目中的页面数并决定是否启用它。
+博客分类配置应为一个数组，每一项控制一个分类规则。
+interface BlogCategoryOptions {
+ /**
+ * 唯一的分类名称
+ */
+ key: string
+
+ /**
+ * 从页面中获取分类的函数
+ */
+ getter: (page: Page) => string[]
+
+ /**
+ * 页面排序器
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * 待注册的页面路径图案
+ *
+ * @description `:key` 将会被替换为原 key 的 slugify 结果
+ *
+ * @default `/:key/`
+ */
+ path?: string | false
+
+ /**
+ * 页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Front Matter 配置
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+
+ /**
+ * 待注册的项目页面路径图案或自定义函数
+ *
+ * @description 当填入字符串的时候, `:key` 和 `:name` 会被自动替换为原始的 key、name 的 slugify 结果。
+ *
+ * @default `/:key/:name/`
+ */
+ itemPath?: string | ((name: string) => string) | false
+
+ /**
+ * 项目页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ itemLayout?: string
+
+ /**
+ * 项目 Front Matter 配置
+ */
+ itemFrontmatter?: (name: string, localePath: string) => Record<string, string>
+}
+博客类型配置应为一个数组，每一项控制一个类型规则。
+interface BlogTypeOptions {
+ /**
+ * 唯一的类型名称
+ */
+ key: string
+
+ /**
+ * 一个过滤函数来决定页面是否满足此类型
+ */
+ filter: (page: Page) => boolean
+
+ /**
+ * 页面排序器
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * 待注册的页面路径
+ *
+ * @default '/:key/'
+ */
+ path?: string | false
+
+ /**
+ * 页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Front Matter 配置
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+}
+你可以从 @vuepress/plugin-blog/client 导入下列 API:
博客分类
+const useBlogCategory: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogCategoryData<T>>
+参数 key 为需要获取的键名。如果未传入 key，会尝试使用与当前路径匹配的 key。
博客类型
+const useBlogType: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogTypeData<T>>
+参数 key 为需要获取的键名。如果未传入 key，会尝试使用与当前路径匹配的 key。
详细的返回值如下:
+interface Article<T extends Record<string, unknown> = Record<string, unknown>> {
+ /** 文章路径 */
+ path: string
+ /** 文章信息 */
+ info: T
+}
+
+interface BlogCategoryData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** 分类路径 */
+ path: string
+
+ /**
+ * 仅当当前路径和某个子项目匹配时可用
+ */
+ currentItems?: Article<T>[]
+
+ /** 分类映射 */
+ map: {
+ /** 当前分类下全局唯一的 key */
+ [key: string]: {
+ /** 对应键值的分类路径 */
+ path: string
+ /** 对应键值的项目 */
+ items: Article<T>[]
+ }
+ }
+}
+
+interface BlogTypeData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** 类别路径 */
+ path: string
+
+ /** 当前类别下的项目 */
+ items: Article<T>[]
+}
+@vuepress/plugin-blog，你可以轻松地将博客功能引入主题。
+起步时，插件会首选过滤并选择那些需要作为文章的页面。这将剔除你不想要的页面，并在后续处理中排除它们。
+默认情况下，所有从 Markdown 文件生成但不是主页的页面，都将被视作文章。
+你可能需要设置 filter 选项来完全自定义要收集的页面。 filter 接受一个形状为 (page: Page) => boolean 的函数。
接着，你应该设置 getInfo 选项为一个接受 Page 作为参数并返回包含所需信息的对象的函数。这样稍后，你可以从组合 API 中获取这些信息。
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ filter: ({ filePathRelative, frontmatter }) => {
+ // 舍弃那些不是从 Markdown 文件生成的页面
+ if (!filePathRelative) return false
+
+ // 舍弃 `archives` 文件夹的页面
+ if (filePathRelative.startsWith('archives/')) return false
+
+ // 舍弃那些没有使用默认布局的页面
+ if (frontmatter.home || frontmatter.layout) return false
+
+ return true
+ },
+
+ getInfo: ({ frontmatter, git = {}, data = {} }) => {
+ // 获取页面信息
+ const info: Record<string, any> = {
+ author: frontmatter.author || '',
+ categories: frontmatter.categories || [],
+ date: frontmatter.date || git.createdTime || null,
+ tags: frontmatter.tags || [],
+ excerpt: data.excerpt || '',
+ }
+
+ return info
+ },
+ }),
+ // 其他插件 ...
+ ],
+}
+基本上，你的博客中需要两种“类型”:
+类别:
+“类别”是用文章的标签 (或类别) 对它们进行分组。
+例如，每篇文章可能都有对应的“分类”和“标签”。
+类型:
+“类型”是过滤不同条件的文章。
+例如，你的帖子中可能有日记或笔记。当帖子带有写作日期信息时，它可以称为“时间线项目”。
+了解这两种类型的描述后，你可以设置 category 和 type 选项，它们都接受一个数组，每个元素代表一个配置。
让我们从此处 2 个例子开始。
+假设你想为每篇文章设置标签，并且你正在通过 frontmatter.tag 设置它们。同时，你想要在 /tag/ 中使用 TagMap 布局的标签页面，并在/tag/标签名称 中使用 TagList 布局对标签按名称进行分组，你可能需要这样的配置:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // 其他配置 ...
+ category: [
+ {
+ key: 'tag',
+ getter: ({ frontmatter }) => frontmatter.tag || [],
+ path: '/tag/',
+ layout: 'TagMap',
+ frontmatter: () => ({ title: '标签页' }),
+ itemPath: '/tag/:name/',
+ itemLayout: 'TagList',
+ itemFrontmatter: (name) => ({ title: `${name}标签` }),
+ },
+ ],
+ }),
+ // 其他插件 ...
+ ],
+}
+此外，你可能希望为你的一些文章加注星标，并将其展示给访问者。当你在 frontmatter 中设置 star: true 来标记它们时，你可能需要这样的配置来在 /star/ 路径中以 StarList 布局显示它们:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // 其他配置 ...
+ type: [
+ {
+ key: 'star',
+ filter: ({ frontmatter }) => frontmatter.star,
+ path: '/star/',
+ layout: 'StarList',
+ frontmatter: () => ({ title: '星标文章' }),
+ },
+ ],
+ }),
+ // 其他插件 ...
+ ],
+}
+看，设置这两种类型很容易。有关完整选项，请参阅 博客分类配置 和 博客分类配置。
+当生成每个页面时，插件将在 frontmatter.blog 中设置如下信息
interface BlogFrontmatterOptions {
+ /** 当前页面的类型 */
+ type: 'category' | 'type'
+ /** 在当前分类或类别下全局唯一的 key */
+ key: string
+ /**
+ * 当前的分类名称
+ *
+ * @description 仅在分类子项目页面中可用
+ */
+ name?: string
+}
+所以你可以直接调用 useBlogCategory() 和 useBlogType()，结果将是当前路由绑定的类别或类型。
此外，你可以通过传递所需的 key 作为参数，来将获得绑定到该 key 的信息。
对于上方的 Node 配置而言，你可以在客户端通过如下方式获取 tag 和 star 的信息:
+TagMap 布局:
<template>
+ <div>
+ <h1>Tag page</h1>
+ <ul>
+ <li v-for="({ items, path }, name) in categoryMap.map">
+ <RouteLink :key="name" :to="path" class="category">
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </li>
+ </ul>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+TagList 布局:
<template>
+ <div>
+ <h1>Tag page</h1>
+ <div class="category-wrapper">
+ <RouteLink
+ v-for="({ items, path }, name) in categoryMap.map"
+ :key="name"
+ :to="path"
+ class="category"
+ >
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </div>
+ <div class="article-wrapper" v-if="categoryMap.currentItems">
+ <div v-if="!categoryMap.currentItems.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in categoryMap.currentItems"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline
+ ? `${new Date(info.date).toLocaleDateString()}: `
+ : '') + info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author"
+ >Author: {{ info.author }}</span
+ >
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag"
+ >Tag: {{ info.tag.join(', ') }}</span
+ >
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+StarList 布局:
<template>
+ <div class="article-wrapper" v-if="stars.items">
+ <div v-if="!stars.items.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in stars.items"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline ? `${new Date(info.date).toLocaleDateString()}: ` : '') +
+ info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author">Author: {{ info.author }}</span>
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag">Tag: {{ info.tag.join(', ') }}</span>
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogType } from '@vuepress/plugin-blog/client'
+
+import ArticleList from '../components/ArticleList.vue'
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+
+const stars = useBlogType('star')
+</script>
+有关返回类型，请参阅 Composition API 返回类型。
+该插件添加了原生多语言支持，因此你的设置将自动应用于每种语言。
+例如，如果用户进行了以下 locales 配置，并且你正在设置上面的“star”示例:
+export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+}
+那么 /zh/star/ 和 /star/ 都将可用，并且只会显示对应语言下的文章。
这个插件提供了一个内置的摘要生成器，可以通过将 excerpt 选项设置为 true 来启用。
摘要介绍
+摘要是一个 HTML 片段，被用于在博客列表中显示文章的简短描述，所以摘要有如下限制:
+isCustomElement 选项。.vuepress/public 的绝对路径或完整路径以确保它们可以在其他地址被访问。摘要生成器将尝试从 Frontmatter 内容中找到有效的摘要分隔符，如果找到，它将使用分隔符之前的内容，分隔符默认为 `
+]]>@vuepress/plugin-blog，你可以轻松地将博客功能引入主题。
+起步时，插件会首选过滤并选择那些需要作为文章的页面。这将剔除你不想要的页面，并在后续处理中排除它们。
+默认情况下，所有从 Markdown 文件生成但不是主页的页面，都将被视作文章。
+你可能需要设置 filter 选项来完全自定义要收集的页面。 filter 接受一个形状为 (page: Page) => boolean 的函数。
接着，你应该设置 getInfo 选项为一个接受 Page 作为参数并返回包含所需信息的对象的函数。这样稍后，你可以从组合 API 中获取这些信息。
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ filter: ({ filePathRelative, frontmatter }) => {
+ // 舍弃那些不是从 Markdown 文件生成的页面
+ if (!filePathRelative) return false
+
+ // 舍弃 `archives` 文件夹的页面
+ if (filePathRelative.startsWith('archives/')) return false
+
+ // 舍弃那些没有使用默认布局的页面
+ if (frontmatter.home || frontmatter.layout) return false
+
+ return true
+ },
+
+ getInfo: ({ frontmatter, git = {}, data = {} }) => {
+ // 获取页面信息
+ const info: Record<string, any> = {
+ author: frontmatter.author || '',
+ categories: frontmatter.categories || [],
+ date: frontmatter.date || git.createdTime || null,
+ tags: frontmatter.tags || [],
+ excerpt: data.excerpt || '',
+ }
+
+ return info
+ },
+ }),
+ // 其他插件 ...
+ ],
+}
+基本上，你的博客中需要两种“类型”:
+类别:
+“类别”是用文章的标签 (或类别) 对它们进行分组。
+例如，每篇文章可能都有对应的“分类”和“标签”。
+类型:
+“类型”是过滤不同条件的文章。
+例如，你的帖子中可能有日记或笔记。当帖子带有写作日期信息时，它可以称为“时间线项目”。
+了解这两种类型的描述后，你可以设置 category 和 type 选项，它们都接受一个数组，每个元素代表一个配置。
让我们从此处 2 个例子开始。
+假设你想为每篇文章设置标签，并且你正在通过 frontmatter.tag 设置它们。同时，你想要在 /tag/ 中使用 TagMap 布局的标签页面，并在/tag/标签名称 中使用 TagList 布局对标签按名称进行分组，你可能需要这样的配置:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // 其他配置 ...
+ category: [
+ {
+ key: 'tag',
+ getter: ({ frontmatter }) => frontmatter.tag || [],
+ path: '/tag/',
+ layout: 'TagMap',
+ frontmatter: () => ({ title: '标签页' }),
+ itemPath: '/tag/:name/',
+ itemLayout: 'TagList',
+ itemFrontmatter: (name) => ({ title: `${name}标签` }),
+ },
+ ],
+ }),
+ // 其他插件 ...
+ ],
+}
+此外，你可能希望为你的一些文章加注星标，并将其展示给访问者。当你在 frontmatter 中设置 star: true 来标记它们时，你可能需要这样的配置来在 /star/ 路径中以 StarList 布局显示它们:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // 其他配置 ...
+ type: [
+ {
+ key: 'star',
+ filter: ({ frontmatter }) => frontmatter.star,
+ path: '/star/',
+ layout: 'StarList',
+ frontmatter: () => ({ title: '星标文章' }),
+ },
+ ],
+ }),
+ // 其他插件 ...
+ ],
+}
+看，设置这两种类型很容易。有关完整选项，请参阅 博客分类配置 和 博客分类配置。
+当生成每个页面时，插件将在 frontmatter.blog 中设置如下信息
interface BlogFrontmatterOptions {
+ /** 当前页面的类型 */
+ type: 'category' | 'type'
+ /** 在当前分类或类别下全局唯一的 key */
+ key: string
+ /**
+ * 当前的分类名称
+ *
+ * @description 仅在分类子项目页面中可用
+ */
+ name?: string
+}
+所以你可以直接调用 useBlogCategory() 和 useBlogType()，结果将是当前路由绑定的类别或类型。
此外，你可以通过传递所需的 key 作为参数，来将获得绑定到该 key 的信息。
对于上方的 Node 配置而言，你可以在客户端通过如下方式获取 tag 和 star 的信息:
+TagMap 布局:
<template>
+ <div>
+ <h1>Tag page</h1>
+ <ul>
+ <li v-for="({ items, path }, name) in categoryMap.map">
+ <RouteLink :key="name" :to="path" class="category">
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </li>
+ </ul>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+TagList 布局:
<template>
+ <div>
+ <h1>Tag page</h1>
+ <div class="category-wrapper">
+ <RouteLink
+ v-for="({ items, path }, name) in categoryMap.map"
+ :key="name"
+ :to="path"
+ class="category"
+ >
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </div>
+ <div class="article-wrapper" v-if="categoryMap.currentItems">
+ <div v-if="!categoryMap.currentItems.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in categoryMap.currentItems"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline
+ ? `${new Date(info.date).toLocaleDateString()}: `
+ : '') + info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author"
+ >Author: {{ info.author }}</span
+ >
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag"
+ >Tag: {{ info.tag.join(', ') }}</span
+ >
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+StarList 布局:
<template>
+ <div class="article-wrapper" v-if="stars.items">
+ <div v-if="!stars.items.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in stars.items"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline ? `${new Date(info.date).toLocaleDateString()}: ` : '') +
+ info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author">Author: {{ info.author }}</span>
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag">Tag: {{ info.tag.join(', ') }}</span>
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogType } from '@vuepress/plugin-blog/client'
+
+import ArticleList from '../components/ArticleList.vue'
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+
+const stars = useBlogType('star')
+</script>
+有关返回类型，请参阅 Composition API 返回类型。
+该插件添加了原生多语言支持，因此你的设置将自动应用于每种语言。
+例如，如果用户进行了以下 locales 配置，并且你正在设置上面的“star”示例:
+export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+}
+那么 /zh/star/ 和 /star/ 都将可用，并且只会显示对应语言下的文章。
这个插件提供了一个内置的摘要生成器，可以通过将 excerpt 选项设置为 true 来启用。
摘要介绍
+摘要是一个 HTML 片段，被用于在博客列表中显示文章的简短描述，所以摘要有如下限制:
+isCustomElement 选项。.vuepress/public 的绝对路径或完整路径以确保它们可以在其他地址被访问。摘要生成器将尝试从 Frontmatter 内容中找到有效的摘要分隔符，如果找到，它将使用分隔符之前的内容，分隔符默认为 <!-- more -->，并且你可以通过 excerptSeparator 选项来自定义它。
如果找不到有效的分隔符，它将从 Markdown 文件的开头开始解析内容，直到长度达到预设值时停止。该值默认为 300，你可以通过设置 excerptLength 选项来自定义它。
要选择哪个页面应该生成摘要，你可以使用 excerptFilter 选项。
示例
+通常，如果用户设置了 frontmatter.description，你可能希望使用它们，因此如果 frontmatter.description 不为空，你可以让过滤器函数返回 false。
你既可以在 Node.js 一侧使用插件选项设置选项，也可以通过客户端配置文件在浏览器一侧设置选项。
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+// .vuepress/config.ts
+export default {
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo
+
+ // 在这里放置其他选项
+ // ...
+ }),
+ ],
+}
+你既可以在 Node.js 一侧使用插件选项设置选项，也可以通过客户端配置文件在浏览器一侧设置选项。
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+// .vuepress/config.ts
+export default {
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo
+
+ // 在这里放置其他选项
+ // ...
+ }),
+ ],
+}
+import { defineClientConfig } from 'vuepress/client'
+import {
+ defineArtalkConfig,
+ // defineGiscusConfig,
+ // defineTwikooConfig,
+ // defineWalineConfig,
+} from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+有以下你需要注意的限制：
+provider、多语言设置和其他资源相关选项必须在插件选项中设置。
为确保 tree-shaking 有效，我们必须在 Node 一侧优化入口，以便打包器可以了解最终打包中应包含哪些资源。
+这些选项将在配置参考中用
+不能序列化为 JSON 的选项必须在客户端配置中设置。
+接收复杂值的选项（例如：函数）不能在插件选项中设置，因为插件运行在 Node.js 环境下，所以我们无法将这些值和它们的上下文传递给浏览器。
+这些选项将在配置参考中用
+该插件全局注册了一个组件 <CommentService />。
alias 和布局槽来插入组件。 我们建议你在 <PageNav /> 组件之后插入评论组件 (<CommentService />)，本页可作为一个 Demo 作为参考。默认情况下，<CommentService /> 组件是全局启用的，你可以在插件选项和页面 frontmatter 中使用 comment 选项来控制它。
comment: false 在本地禁用它。comment 设置为 false。 然后你可以在页面 frontmatter 中设置 comment: true 以在局部启用它。你可以在页面 frontmatter 中设置 commentID 选项来自定义评论 ID，该 ID 用于标识要用于页面的评论存储项。默认情况下，它将是页面的 path ，这意味着如果你将站点部署到多个位置，站点间具有相同内容的页面将共享相同的评论数据。
目前你可以选择 Giscus、Waline、Artalk 和 Twikoo。
+推荐的评论服务
+"Artalk" | "Giscus" | "Twikoo" | "Waline" | "None""None"booleantruechannel 插件选项用于配置 feed 的频道。
+stringSiteConfig.title频道的标题
+stringoptions.hostname 和 context.base 生成)channel 插件选项用于配置 feed 的频道。
+stringSiteConfig.title频道的标题
+stringoptions.hostname 和 context.base 生成)频道地址
+stringSiteConfig.description频道描述信息
+stringsiteConfig.locales['/'].locales"en-US"频道使用的语言
+stringauthor.name 生成 Copyright by $author频道版权信息
+string (需是合法的 Date ISOString)频道内容的发布时间
+string (需是合法的 Date ISOString)频道内容的上次更新时间
+number内容有效时间，即获取后保持缓存而不进行新获取的时间
+string这是一个会在频道中使用的图片，建议设置正方形图片、尺寸最好不小于 512×512。
+string一个代表频道的图标，建议设置正方形图片、尺寸最好不小于 128×128，背景色透明。
+FeedAuthor频道的作者。
+interface FeedAuthor {
+ /** 作者姓名 */
+ name: string
+ /** 作者电子邮箱 */
+ email?: string
+ /** 作者网站 */
+ url?: string
+ /**
+ * 作者头像地址
+ *
+ * 正方形，最好不小于 128×128，透明背景
+ */
+ avatar?: string
+}
+stringWebsub 的链接。Websub 需要服务器后端，与 VuePress 主旨不符，如无特殊需要忽略即可。
+WebSub
+有关信息，详见 Websub。
+string部署网站的域名。
+booleanfalse是否启用 Atom 格式输出。
+booleanfalse是否启用 JSON 格式输出。
]]>string部署网站的域名。
+booleanfalse是否启用 Atom 格式输出。
+booleanfalse是否启用 JSON 格式输出。
+booleanfalse是否启用 RSS 格式输出。
+string一个大的图片，用作 feed 展示。
+string一个小的图标，显示在订阅列表中。
+number100设置 feed 的最大项目数量。在所有页面排序好后，插件会截取前 count 个项目。
+如果你的站点文章很多，你应该考虑设置这个选项以减少 feed 文件大小。
+(RegExp | string)[] | (tagName：string) => boolean应在 Feed 中保留的自定义元素或组件。
+默认情况下，所有未知标签均会被移除。
+类型：(page: Page)=> boolean
默认值：
+;({ frontmatter, filePathRelative }: Page): boolean =>
+ !(
+ frontmatter.home ||
+ !filePathRelative ||
+ frontmatter.article === false ||
+ frontmatter.feed === false
+ )
+自定义的过滤函数，用于过滤哪些项目在 feed 中显示。
+类型： (pageA: Page, pageB: Page)=> number
默认值：
+// dateSorter 来源于 @vuepress/helper
+;(pageA, pageB): number =>
+ dateSorter(
+ pageA.data.git?.createdTime
+ ? new Date(pageA.data.git?.createdTime)
+ : pageA.frontmatter.date,
+ pageB.data.git?.createdTime
+ ? new Date(pageB.data.git?.createdTime)
+ : pageB.frontmatter.date,
+ )
+Feed 项目的排序器。
+默认的排序行为是通过 Git 的文件添加日期 (需要 @vuepress/plugin-git)。
提示
+你应该启用 @vuepress/plugin-git 来获取最新创建的页面作为 feed 项目。否则，feed 项目将按照 VuePress 中页面的默认顺序排序。
channel 选项用于配置 Feed 频道。
可用选项详见 配置 → 频道设置
+booleanfalse是否在开发服务器中启用
+提示
+由于性能原因，我们不提供热更新。重启开发服务器以同步你的变更。
+string"http://localhost:${port}"开发服务器使用的主机名
+string"atom.xml"Atom 格式输出路径，相对于输出路径。
+string@vuepress/plugin-feed/templates/atom.xsl 的内容Atom xsl 模板文件没人陪美国
+string"atom.xsl"Atom xsl 输出路径，相对于输出路径。
+string"feed.json"JSON 格式输出路径，相对于输出路径。
+string"rss.xml"RSS 格式输出路径，相对于输出路径。
+string@vuepress/plugin-feed/templates/rss.xsl 的内容RSS xsl 模板文件内容。
+string"rss.xsl"RSS xsl 输出路径，相对于输出路径。
+Feed 生成控制器，详见 Feed 生成器。
+此插件内置了生成器，只有当你想完全控制 feed 生成时才需要设置此选项。
+Record<string, BaseFeedOptions>你可以将它用于每个语言环境的特定选项。
+除 hostname 外，上述任何选项均受支持。
默认情况下，所有文章均会被添加至 feed 流。如果你想在 feed 中移除特定页面，你可以在 frontmatter 中设置 feed: false。
string由 VuePress 自动生成，默认为页面的 h1 内容
+默认情况下，所有文章均会被添加至 feed 流。如果你想在 feed 中移除特定页面，你可以在 frontmatter 中设置 feed: false。
string由 VuePress 自动生成，默认为页面的 h1 内容
+string页面描述
+Date页面的发布日期
+boolean该页面是否是文章
+++如果此项设置为
+false，则该页不会包含在最终的 feed 中。
string页面版权信息
+string页面的封面/分享图，需为完整链接或绝对链接。
+stringFeed 项目的标题
+stringFeed 项目的描述
+stringFeed 项目的内容
+FeedAuthor[] | FeedAuthorFeed 项目的作者
+interface FeedAuthor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+FeedContributor[] | FeedContributorFeed 项目的贡献者
+interface FeedContributor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+stringFeed 项目的标识符，用于标识 Feed 项目。
+你应该确保每个 Feed 项目有全局唯一的 guid。
+getter 来完全控制 Feed 项目的生成。
+(page: Page) => string项目标题获取器
+(page: Page) => string项目链接获取器
+(page: Page) => string | undefinedgetter 来完全控制 Feed 项目的生成。
+(page: Page) => string项目标题获取器
+(page: Page) => string项目链接获取器
+(page: Page) => string | undefined项目描述获取器
+提示
+因为 Atom 在摘要中支持 HTML，所以如果可能的话，你可以在这里返回 HTML 内容，但内容必须以标记 html: 开头。
(page: Page) => string项目内容获取器
+(page: Page) => FeedAuthor[]项目作者获取器。
+获取器应在作者信息缺失时返回空数组。
+interface FeedAuthor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => FeedCategory[] | undefined项目分类获取器。
+interface FeedCategory {
+ /**
+ * 分类名称
+ */
+ name: string
+
+ /**
+ * 标识分类法的字符串
+ *
+ * @description rss format only
+ */
+ domain?: string
+
+ /**
+ * URI 标识的分类 scheme
+ *
+ * @description atom format only
+ */
+ scheme?: string
+}
+(page: Page) => FeedEnclosure | undefined项目附件获取器。
+interface FeedEnclosure {
+ /**
+ * Enclosure 地址
+ */
+ url: string
+
+ /**
+ * 类型
+ *
+ * @description 应为一个标准的 MIME 类型，rss format only
+ */
+ type: string
+
+ /**
+ * 按照字节数计算的大小
+ *
+ * @description rss format only
+ */
+ length?: number
+}
+(page: Page) => Date | undefined项目发布日期获取器
+(page: Page) => Date项目最后更新日期获取器
+(page: Page) => string项目图片获取器
+确保返回一个完整的 URL。
+(page: Page) => FeedContributor[]项目贡献者获取器
+获取器应在贡献者信息缺失时返回空数组。
+interface FeedContributor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => string | undefined项目版权获取器
+]]>插件可为你生成以下三种格式的 feed 文件:
+请按照需要生成的格式，在插件选项中设置 atom, json 或 rss 为 true。
为了正确生成 Feed 链接，你需要在插件选项中设置 hostname。
当你在浏览器中打开 Feed 文件时，我们会通过 xsl 模板将 atom 和 rss feed xml 魔法般地转换为可读的 html。你可以查看本站的 atom 和 rss feed 作为案例！
]]>插件可为你生成以下三种格式的 feed 文件:
+请按照需要生成的格式，在插件选项中设置 atom, json 或 rss 为 true。
为了正确生成 Feed 链接，你需要在插件选项中设置 hostname。
当你在浏览器中打开 Feed 文件时，我们会通过 xsl 模板将 atom 和 rss feed xml 魔法般地转换为可读的 html。你可以查看本站的 atom 和 rss feed 作为案例！
+如果你想在开发服务器中预览 Feed，你需要在插件选项中设置 devServer: true。如果你没有使用默认的 http://localhost:{port}，你还需要设置 devHostname。
你可以通过设置 channel 选项来自自定义 Feed 频道的各项信息。
我们推荐进行如下设置:
+channel.pubDate 中channel.ttl 中设置内容的更新周期(单位: 分钟)channel.copyright 设置版权信息channel.author 设置频道作者。详细的选项及其默认值详见 配置 → 频道设置
+默认情况下，所有文章均会被添加至 feed 流。
+你可以在 frontmatter 中配置 feed 和其他选项控制每个页面的 Feed 项目内容，详见 Frontmatter 选项 了解它们如何被转换。
你可以通过配置插件选项中的 getter 完全控制 Feed 项目的生成逻辑。 详细的选项及其默认值详见 配置 → Feed 获取器
插件会针对每个语言生成单独的 Feed。
+你可以通过插件选项中的 locales 分别对不同语言提供不同的默认设置。
类型：boolean
默认值：false
详情：
+是否在 Service Worker 首次成功注册时显示 PWA 安装按钮
+类型：ManifestOption
详情：
+填充一个将被解析为 manifest.webmanifest 的对象。
+提示
+如果未设置某些选项，它们会回退到插件预设值。
+siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.description || siteConfig.locales['/'].description || "A site built with vuepress"siteConfig.locales['/'].lang || "en-US"context.basecontext.base"standalone""#46bd87""#ffffff""portrait-primary"false参考：
+ +类型：boolean
默认值：false
详情：
+是否在 Service Worker 首次成功注册时显示 PWA 安装按钮
+类型：ManifestOption
详情：
+填充一个将被解析为 manifest.webmanifest 的对象。
+提示
+如果未设置某些选项，它们会回退到插件预设值。
+siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.description || siteConfig.locales['/'].description || "A site built with vuepress"siteConfig.locales['/'].lang || "en-US"context.basecontext.base"standalone""#46bd87""#ffffff""portrait-primary"false参考：
+ +类型：string
详情：
+favicon.ico 地址，填入绝对路径。
注意
+我们建议你为你的站点生成 favicon。
+string"#46bd87"booleanfalsebooleanfalse类型：number
默认值：2048
详情：
+允许缓存的最大大小 (以 KB 为单位)
+注意
+此选项具有最高优先级，任何超过此值的文件都会被排除。
+所以你如果生成了很大的 HTML 或 JS 文件，请考虑调高此值，否则你的 PWA 可能无法在离线模式下正常运行。
+类型：number
默认值：1024
详情：
+图片允许缓存的最大大小 (以 KB 为单位)
+该选项不能大于 maxSize 选项
+类型："disabled" | "available" | "hint" | "force"
默认值："available"
详情：
+发现新内容时的控制逻辑。
+"disabled": 即使有新的 service worker 也不做任何事情，新的 service work 开始等待后，会在用户下次访问时接管页面，让用户获得新内容。
"available": 仅当新的 service worker 可用时才显示更新弹出窗口
"hint": 显示更新内容可用提示，并允许用户立即刷新。当新的 SW 成功注册后，将转为更新内容就绪弹窗。
当你希望用户立即查看新文档时，这很有帮助。
+提示
+如果用户在新 SW 就绪前选择刷新，当前的 Service Worker 将被注销，并且请求将开始向 Web 发出。新的 service worker 将开始安装并在安装后接管页面。
+"force": 立即注销当前 Service Worker 然后刷新以获取新内容
警告
+虽然这可以确保用户访问的是最新内容，但这可能会影响访问体验。
+提示
+文档的更新方式由以前的版本控制，因此当前选项仅影响此版本的下一次更新。
+更高支持苹果的特殊设置，忽略它们是安全的。
+string"black" | "white""black"string针对微软磁贴的特殊设置，忽略它们是安全的。
+stringstringthemeColorstring"PwaFoundPopup"string"PwaReadyPopup"booleanfalse详情：
+传递给 workbox-build 的选项，具体详情，请见 Workbox 文档
类型：PwaPluginLocaleConfig
interface PwaPluginLocaleData {
+ /**
+ * 安装按钮文字
+ */
+ install: string
+
+ /**
+ * iOS 安装文字
+ */
+ iOSInstall: string
+
+ /**
+ * 取消按钮文字
+ */
+ cancel: string
+
+ /**
+ * 关闭按钮文字
+ */
+ close: string
+
+ /**
+ * 上一张图片文字
+ */
+ prevImage: string
+
+ /**
+ * 下一张图片文字
+ */
+ nextImage: string
+
+ /**
+ * 安装解释
+ */
+ explain: string
+
+ /**
+ * 描述标签文字
+ */
+ desc: string
+
+ /**
+ * 特性标签文字
+ */
+ feature: string
+
+ /**
+ * 更新内容提示文字
+ */
+ hint: string
+
+ /**
+ * 更新内容可用文字
+ */
+ update: string
+}
+
+interface PwaPluginLocaleConfig {
+ [localePath: string]: PwaPluginLocaleData
+}
+详情：
+PWA 插件的国际化配置。
+详情：
+返回此插件的事件派发器。
+你可以添加监听器函数到 register-service-worker 提供的事件。
+示例：
+import { usePwaEvent } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+ event.on('ready', (registration) => {
+ console.log('Service worker is active.')
+ })
+ },
+}
+详情：
+当发现新内容时强制刷新页面。
+示例：
+import { forceUpdate } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ forceUpdate()
+ })
+ },
+}
+详情：
+手动注册 Service Worker。
+参数：
+| 参数 | 类型 | 描述 | +|
+]]>将你的 VuePress 站点变成渐进式网络应用程序 (PWA)[1]。
+此插件使用 workbox-build 生成 Service Worker 文件，并使用 register-service-worker 注册 Service Worker。
]]>将你的 VuePress 站点变成渐进式网络应用程序 (PWA)[1]。
+此插件使用 workbox-build 生成 Service Worker 文件，并使用 register-service-worker 注册 Service Worker。
+注意
+如果你启用过该插件，并想要禁用它，你可能需要 `@vuepress/plugin-remove-pwa 来移除现有的 Service Worker 。
+A PWA uses a Service Worker [2] (SW for short) to cache and proxy site content.
+一个 PWA 使用 Service Worker [2:1] (简称 SW) 来获取并托管网站内容。
+为了使你的网站符合 PWA 的要求，一个网络 App 清单[3]文件是必要的，并且你的 PWA 应满足可安装性[4]要求。
+你可以通过设置 manifest 选项来自定义 manifest 文件，或者在 public 文件夹中提供 manifest.webmanifest 或 manifest.json。前者优先级更高。
插件会自动为你生成 manifest.webmanifest，并在每个页面的 <head> 中添加清单链接声明，但是 你至少应该通过 manifest.icons 或 PWA 插件中的其他选项设置一个有效的图标。
注意
+可安装性[4:1]规范要求 manifest 中至少声明一个有效的图标。
+所以如果你不配置 manifest.icons，访问者只能享受到 Service Worker 缓存带来的离线可访问性，而并不能作为 PWA 进行安装。
此外，该插件默认不处理清单中的任何内容，而是按原样输出。 这意味着，如果你计划部署到子目录，则应自行将 URL 前缀附加到自己的清单 Urls 中。如果你需要的所有东西都在 base 文件夹下，你可以在插件选项中设置 appendBase: true 让插件将 base 自动附加到任何地址。
为了更好的控制 Service Worker 可以预缓存的内容，插件提供了相关的缓存控制选项。
+默认情况下插件会预缓存所有的 JS 和 CSS 文件，但仅缓存主页和 404 页面的 HTML。插件同时还会缓存字体文件 (woff, woff2, eot, ttf, otf) 和 SVG 图标。
+如果你的站点只有少量重要图片，并希望它们在离线模式下显示，你可以通过设置 cacheImage 选项为 true 来缓存站点图片。
我们通过文件后缀名识别图片，任何以 .png, .jpg, .jpeg, .gif, .bmp, .webp 结尾的文件都会视为图片。
当你网站体积不大，并且希望文档完全离线可用时，你可以通过设置 cacheHTML 为 true 来缓存所有 HTML 页面。
为什么默认不缓存非主页和 404 页面
+虽然说 VuePress 为所有的页面通过 SSG[5] 生成了 HTML 文件，但是这些文件主要用于 SEO[6]，并能够让你在后端不做 SPA[7] 配置的情况下能够直接访问任何链接。
+VuePress 本质上是一个 SPA。这意味着你只需要缓存主页并从主页进入即可正常访问所有页面。所以默认不缓存其他 HTML 能够有效减小缓存大小 (可以缩减大约 40% 的体积)，加快 SW 更新速度。
+但是这样做也有缺点，如果用户直接从非主页进入网站，首个页面的 HTML 文件仍需要从互联网加载。同时离线环境下，用户只能通过主页进入再自行导航到对应页面，直接访问某个链接会出现无法访问的提示。
+为了防止在预缓存列表中包含大文件，任何 > 2 MB 的文件或 > 1 MB 的图片都将被忽略。 你可以通过 maxSize 和 maxImageSize 来自定义大小限制 (单位为 KB)。
我们提供 update 选项控制用户如何接收更新。
update 选项的默认值是 "available"，这意味着当网站内容更新后，新的 SW 会在后台静默安装，并在安装结束后弹窗提示用户新内容就绪。用户可以自主选择是否立即刷新查看新内容。这意味在新 SW 就绪前用户会访问旧版本网站。
如果你的文档仍在建设期，希望尽早提示用户他可能在阅读已过时的内容，你可以将其设置为 "hint"。这样用户在进入文档后数秒内就可以收到新内容已发布的通知。但这样做的负面效果是如果用户在新 SW 就绪前选择更新，那么他将在新 SW 安装并接管页面前，需要从互联网获取页面的全部资源。
如果你的文档很稳定，或者你在托管博客，不太关心用户立即接收到最新版本，你可以将其设置为 "disabled"，这意味着新的 SW 将在后台完全静默安装并在安装后等待，当旧版本 SW 控制的页面全部关闭后，新 SW 将再下次访问接管并提供用户新内容。此设置可以避免用户在访中被弹窗打扰。
如果你希望通过 SW 来加速用户在弱网或无网条件下的访问，但同时希望用户时刻访问新内容，你可以将此选项设置为 "force"。这意味着检测到新 SW 后旧 SW 将会被立刻销毁并且页面会被刷新以确保用户浏览最新内容。最大的缺点就是致新 SW 发布后，用户在重新进入网站后的几秒内会遇到预期之外的突然刷新，并且他们将必须通过互联网访问文档并完全重新安装最新的 SW。
当检测到新内容 (检测到新的 SW) 时，更新提示弹窗将会出现；当新内容就绪时，更新就绪弹窗将会出现。
+如果你对默认的弹窗不满意，你可以自行编写组件更换。从 @vuepress/plugin-pwa/client 中导入 PwaFoundPopup 或 PwaReadyPopup 并使用其 slot 来自定义弹窗内容，然后将组件路径传递给 foundComponent 或 readyComponent 选项。
<script setup lang="ts">
+import { PwaFoundPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaFoundPopup v-slot="{ found, refresh }">
+ <div v-if="found">
+ 已找到新内容
+ <button @click="refresh">刷新</button>
+ </div>
+ </PwaFoundPopup>
+</template>
+<script setup lang="ts">
+import { PwaReadyPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaReadyPopup v-slot="{ isReady, reload }">
+ <div v-if="isReady">
+ 新内容已就绪
+ <button @click="reload">应用</button>
+ </div>
+ </PwaReadyPopup>
+</template>
+插件还提供了其他 PWA 相关选项，比如微软磁贴图标与颜色设置，苹果图标等。 如果你是一个高级用户，你也可以设置 generateSwConfig 来配置 workbox-build。查看 插件选项 了解更多细节。
更多内容，请详见:
+ +PWA 介绍
+PWA 全称 Progressive Web app，即渐进式网络应用程序，标准由 W3C 规定。
+它允许网站通过支持该特性的浏览器将网站作为 App 安装在对应平台上。
+访问 https://developer.mozilla.org/zh-CN/docs/Web/Progressive_web_apps 查看详情。 ↩︎
+Service Worker 简要介绍
+Service Worker 会在注册过程中获取注册在其中的所有文件并缓存它们。
+注册成功后，Service Worker 激活，并开始代理并控制你的全部请求。
+每当你想要通过浏览器发起访问请求后，Service Worker 将会查看其是否存在与自身缓存列表中，若存在则直接返回缓存好的结果，否则调用自身的 fetch 方法进行获取。你可以通过自定义 fetch 方法，来完全控制网页内资源获取请求的结果，比如在离线时提供一个 fallback 的网页。
+每次用户重新打开网站时，Service Worker 会向自身注册时的地址发出校验命令，如果检测到新版本的 Service Worker，则会更新自身，并开始缓存注册在新 Service Worker 中的资源列表。成功获取内容更新后，Service Worker 将会触发 update 事件。可以通过此事件提示用户，比如将在右下角显示一个弹出窗口，提示用户新内容可用并允许用户触发更新。
清单文件
+清单文件使用 JSON 格式，负责声明 PWA 各项信息，如名称、描述、图标、快捷动作等。
+为了使你的站点能够被注册为 PWA，你需要满足 manifest 基本的规范，才能使浏览器认为该网站为一个可安装的 PWA 并允许用户安装它。
+提示
+Manifest 的标准与规范，请详见 MDN 网络 App 清单 和 W3C Manifest
+可安装性
+想要让网站可以注册为 PWA，网站需要自行成功注册有效的 Service Worker，同时拥有合法的 manifest 清单文件并在网站中声明它。
+清单文件应至少包含 name(或 short_name) icons start_url。
SSG: Static Site Generating，静态站点生成。 ↩︎
+SEO: Search Engine Optimization，搜索引擎增强，
+ +SPA: Single Page Application, 单页应用
+大多只有主页，并使用 history mode 处理路由，而不是真的在页面之间导航。 ↩︎
+类型：string
必填：是
+详情：
+部署域名
+类型：Author
type AuthorName = string
+
+interface AuthorInfo {
+ /**
+ * 作者姓名
+ */
+ name: string
+
+ /**
+ * 作者网站
+ */
+ url?: string
+
+ /**
+ * 作者 Email
+ */
+ email?: string
+}
+
+type Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]
+详情：
+默认作者
+类型：string
必填：是
+详情：
+部署域名
+类型：Author
type AuthorName = string
+
+interface AuthorInfo {
+ /**
+ * 作者姓名
+ */
+ name: string
+
+ /**
+ * 作者网站
+ */
+ url?: string
+
+ /**
+ * 作者 Email
+ */
+ email?: string
+}
+
+type Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]
+详情：
+默认作者
+类型：boolean
默认值：true
详情：
+是否自动生成描述
+类型：string | ((page: Page) => string | null)
详情：
+首选链接
+类型：string
详情：
+当找不到图片时的回退图片链接
+类型：string
详情：
+内容的年龄分级，格式为 [int]+，如 "13+"
类型：string
详情：
+你的 twitter 用户名
+类型：(page: Page) => boolean
详情：
+你可以使用此选项判断一个页面是否是文章。
+类型：
+function ogp(
+ /** 插件推断的 OGP 信息 */
+ ogp: SeoContent,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+详情：
+自定义 OGP 生成器
+你可以使用此选项来注入新的或覆盖掉默认生成的 OGP 标签。
+类型：
+function jsonLd(
+ /** 由插件推断出的 JSON-LD 对象 */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+详情：
+自定义 JSON-LD 生成器
+你可以使用此选项来注入新的或覆盖掉默认生成的 JSON-LD 标签。
+类型：
+function customHead(
+ /** head 标签配置 */
+ head: HeadConfig[],
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+详情：
+你可以使用此选项来直接注入任意格式的标签到 <head>。
<head> 注入标签，让你的网站完全支持 开放内容协议 OGP 和 JSON-LD 1.1，以全面增强站点的搜索引擎优化性。
+]]><head> 注入标签，让你的网站完全支持 开放内容协议 OGP 和 JSON-LD 1.1，以全面增强站点的搜索引擎优化性。
+
+插件开箱即用，在不做任何配置的情况下，会尽可能通过页面内容，提取对应的信息补全 OGP 与 JSON-LD 所需的必要标签。
+默认情况下，插件会读取站点配置、主题配置与页面的 frontmatter 来尽可能自动生成。诸如站点名称，页面标题，页面类型，写作日期，最后更新日期，文章标签均会自动生成。
+| 属性名称 | 值 | +| :
+]]>类型：string
必填：是
+详情：
+当前网站部署到的域名，插件需要此选项才能工作。
+类型：string[]
详情：
+需要额外包含的网址。
+如果你有一些不包含在 VuePress 路由中的链接 (如: 存放在 public 文件夹下的页面或其他插件或工具直接生成的页面)，你可能需要设置此项。
+示例：['/about.html', '/api/']
类型：string
必填：是
+详情：
+当前网站部署到的域名，插件需要此选项才能工作。
+类型：string[]
详情：
+需要额外包含的网址。
+如果你有一些不包含在 VuePress 路由中的链接 (如: 存放在 public 文件夹下的页面或其他插件或工具直接生成的页面)，你可能需要设置此项。
+示例：['/about.html', '/api/']
类型：string[]
默认值：['/404.html']
详情：
+不需要收录的页面路径，请以绝对路径开头。
+默认情况下 VuePress 自动生成的所有路径 (除 404 页) 都会被添加进 Sitemap。
+类型：boolean
默认值：false
详情：
+是否在开发服务器中启用
+提示
+由于性能原因，我们不提供热更新。重启开发服务器以同步你的变更。
+类型：string
默认值："http://localhost:${port}"
详情：
+开发服务器使用的主机名
+类型：string
默认值："sitemap.xml"
详情：
+输出的文件名，相对于输出目录。
+类型：string
默认值："sitemap.xsl"
详情：
+输出的 xsl 文件名，相对于输出目录。
+类型：string
默认值："@vuepress-plugin/sitemap/templates/sitemap.xsl"
详情：
+用作模板的 XSL 文件内容
+类型："always" | "hourly" | "daily" | "weekly" | "monthly" | "yearly" | "never"
默认值："daily"
详情：
+页面默认更新频率，会被 Frontmatter 中的 changefreq 选项覆盖。
+类型：number
默认值：0.5
详情：
+页面优先级，范围 0 至 1。
类型：(page: Page, app: App) => string
详情：
+最后修改事件的获得器，需要返回一个 ISO 字符形式的时间，默认会自动通过 Git 插件生成。
+类型：SitemapFrontmatterOptions | false
详情：
+false 表示将页面排除在 sitemap 之外。
类型："always" | "hourly" | "daily" | "weekly" | "monthly" | "yearly" | "never"
默认值："daily"
详情：
+页面默认更新频率。它会覆盖插件选项中的 changefreq 选项。
+类型：SitemapFrontmatterOptions | false
详情：
+false 表示将页面排除在 sitemap 之外。
类型："always" | "hourly" | "daily" | "weekly" | "monthly" | "yearly" | "never"
默认值："daily"
详情：
+页面默认更新频率。它会覆盖插件选项中的 changefreq 选项。
+类型：number
默认值：0.5
详情：
+页面优先级，范围 0 至 1。
hostname 选项。如果你想在开发服务器中预览，请配置 devServer 选项。
+插件会自动根据页面的 Git 的时间戳生成页面的最后更新时间，同时会根据站点的多语言配置声明页面的其他语言版本替代地址。
+默认情况下，所有除 404 页面以外的网站链接均会被添加进 Sitemap。
+如果你希望在 VuePress 项目页面之外，添加其他页面链接到 Sitemap，请将它们变成数组传入插件的 extraUrls 选项。
hostname 选项。如果你想在开发服务器中预览，请配置 devServer 选项。
+插件会自动根据页面的 Git 的时间戳生成页面的最后更新时间，同时会根据站点的多语言配置声明页面的其他语言版本替代地址。
+默认情况下，所有除 404 页面以外的网站链接均会被添加进 Sitemap。
+如果你希望在 VuePress 项目页面之外，添加其他页面链接到 Sitemap，请将它们变成数组传入插件的 extraUrls 选项。
如果你需要排除一些页面路径，你可以将它们变成数组传入到插件的 excludePaths 选项。你也可以在对应页面的 frontmatter 中，设置 sitemap 为 false。
你还可以通过插件的 sitemapFilename 选项控制输出的地址，此地址相对于输出目录，默认为 sitemap.xml。
页面默认的更新周期是 daily (每天)，如果你希望修改全部的页面周期，请在插件选项中设置 changefreq 。你也可以在页面的 frontmatter 中设置 sitemap.changefreq，页面具有更高的优先级。
合法的频率有:
+"always""hourly""daily""weekly""monthly""yearly""never"你可以在插件中设置 priority 以提供一个默认值。同时你可以通过 frontmatter 中的 sitemap.priority 来为每个页面设置优先级。可接受的值为 0 到 1 的浮点数。
你可以通过插件的 modifyTimeGetter 来返回一个 ISO 字符串格式的时间，默认会通过 Git 插件生成。
以下是一个基于文件最后修改时间的例子。
+// 基于文件最后修改时间
+({
+ modifyTimeGetter: (page, app) =>
+ fs.statSync(app.dir.source(page.filePathRelative)).mtime.toISOString();
+})
+网站地图 (Sitemap) 提供搜索引擎优化 (SEO):
+网站地图通过使所有页面可被找到来增强搜索引擎优化的效果。
+大部分搜索引擎只跟踪页面内有限数量的链接，因此当网站非常大的时候，网站地图对于使搜索引擎和访问者可以访问网站中的所有内容就变得必不可少了。
+Sitemaps 是站点管理员向搜索引擎爬虫公布站点可被抓取页面的协议，sitemap 文件内容必须遵循 XML 格式的定义。每个 URL 可以包含更新的周期和时间、URL 在整个站点中的优先级。这样可以让搜索引擎更佳有效的抓取网站内容。
+同步配置 robots.txt
+由于 Sitemap 面向搜索引擎，配合此插件使用时，你最好保证你在 .vuepress/public 文件夹下放置了有效的 robots.txt，以允许搜索引擎收录。一个最简单的 robots.txt 如下 (允许所有搜索引擎访问所有路径)
User-agent: *
+
+Allow: /
+类型： string
详情：
+部署的域名，例如 https://example.com
类型： { [path: string]: Partial<DefaultThemeLocaleData> }
默认值： {}
详情：
+多语言支持的各个语言 locales 。
+所有在 Locale 配置 章节内的配置项都可以在 locales 中使用。
+该配置项仅能在默认主题内生效，注意不要和 站点配置 中的 locales 混淆。
参考：
+类型： string
详情：
+部署的域名，例如 https://example.com
类型： { [path: string]: Partial<DefaultThemeLocaleData> }
默认值： {}
详情：
+多语言支持的各个语言 locales 。
+所有在 Locale 配置 章节内的配置项都可以在 locales 中使用。
+该配置项仅能在默认主题内生效，注意不要和 站点配置 中的 locales 混淆。
参考：
+该章节内的配置项可以作为一般配置使用，也可以使用在 locales 内。
+类型： 'auto' | 'light' | 'dark'
默认值： 'auto'
详情：
+默认颜色模式。
+如果设置为 'auto' ，则会根据 prefers-color-scheme 自动设置初始颜色模式。
参考：
+ +类型： boolean
默认值： true
详情：
+是否启用切换颜色模式的功能。
+如果设置为 true ，将会在导航栏展示一个切换颜色模式的按钮。
参考：
+ +类型： string
默认值： /
详情：
+首页的路径。
+它将被用于：
+类型： false | (NavbarItem | NavbarGroup | string)[]
默认值： []
详情：
+导航栏配置。
+设置为 false 可以禁用导航栏。
为了配置导航栏元素，你可以将其设置为 导航栏数组 ，其中的每个元素是 NavbarItem 对象、 NavbarGroup 对象、或者字符串：
NavbarItem 对象应该有一个 text 字段和一个 link 字段，还有一个可选的 activeMatch 字段。NavbarGroup 对象应该有一个 text 字段和一个 children 字段。 children 字段同样是一个 导航栏数组 。NavbarItem 对象，将页面标题作为 text ，将页面路由路径作为 link 。示例 1：
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // NavbarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ },
+ // NavbarGroup
+ {
+ text: 'Group',
+ children: ['/group/foo.md', '/group/bar.md'],
+ },
+ // 字符串 - 页面文件路径
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // 嵌套 Group - 最大深度为 2
+ {
+ text: 'Group',
+ children: [
+ {
+ text: 'SubGroup',
+ children: ['/group/sub/foo.md', '/group/sub/bar.md'],
+ },
+ ],
+ },
+ // 控制元素何时被激活
+ {
+ text: 'Group 2',
+ children: [
+ {
+ text: 'Always active',
+ link: '/',
+ // 该元素将一直处于激活状态
+ activeMatch: '/',
+ },
+ {
+ text: 'Active on /foo/',
+ link: '/not-foo/',
+ // 该元素在当前路由路径是 /foo/ 开头时激活
+ // 支持正则表达式
+ activeMatch: '^/foo/',
+ },
+ ],
+ },
+ ],
+ }),
+}
+类型： null | string
详情：
+Logo 图片的 URL。
+Logo 图片将会显示在导航栏的左端。
+设置为 null 可以禁用 Logo 。
示例：
+export default {
+ theme: defaultTheme({
+ // Public 文件路径
+ logo: '/images/hero.png',
+ // URL
+ logo: 'https://vuejs.org/images/logo.png',
+ }),
+}
+类型： null | string
详情：
+在夜间模式中使用的 Logo 图片的 URL。
+如果你想在夜间模式中使用不同的 Logo 图片，就可以使用该配置项。
+设置为 null 可以在夜间模式下禁用 Logo 。忽略该配置项将会在夜间模式中使用 logo 配置。
参考：
+ +类型：null | string
详情：
+指定 Logo 图片的替代文字。
+当未指定时，将默认与站点标题相同。
+类型： string
详情：
+项目仓库的 URL。
+它将被用作 仓库链接 的链接。仓库链接 将会显示为导航栏的最后一个元素。
+export default {
+ theme: defaultTheme({
+ // 如果你按照 `organization/repository` 的格式设置它
+ // 我们会将它作为一个 GitHub 仓库
+ repo: 'vuejs/vuepress',
+ // 你也可以直接将它设置为一个 URL
+ repo: 'https://gitlab.com/foo/bar',
+ }),
+}
+类型： false | 'auto' | SidebarConfigArray | SidebarConfigObject
默认值： 'auto'
详情：
+侧边栏配置。
+你可以通过页面的 sidebar frontmatter 来覆盖这个全局配置。
+设置为 false 可以禁用侧边栏。
如果你设置为 'auto'，侧边栏会根据页面标题自动生成。
为了手动配置侧边栏元素，你可以将其设置为 侧边栏数组 ，其中的每个元素是一个 SidebarItem 对象或者一个字符串：
SidebarItem 对象应该有一个 text 字段，有一个可选的 link 字段、一个可选的 children 字段和一个可选的 collapsible 字段。 children 字段同样是一个 侧边栏数组 。 collapsible 字段来控制它是否可折叠。SidebarItem 对象，将页面标题作为 text ，将页面路由路径作为 link ，并根据页面小标题自动生成 children 。如果你想在不同子路径中使用不同的侧边栏，你可以将该配置项设置为 侧边栏对象 ：
+"heading" 以自动为相应路径生成基于标题的侧边栏。示例 1：
+export default {
+ theme: defaultTheme({
+ // 侧边栏数组
+ // 所有页面会使用相同的侧边栏
+ sidebar: [
+ // SidebarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ children: [
+ // SidebarItem
+ {
+ text: 'github',
+ link: 'https://github.com',
+ children: [],
+ },
+ // 字符串 - 页面文件路径
+ '/foo/bar.md',
+ ],
+ },
+ // 字符串 - 页面文件路径
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // 侧边栏对象
+ // 不同子路径下的页面会使用不同的侧边栏
+ sidebar: {
+ '/guide/': [
+ {
+ text: 'Guide',
+ children: ['/guide/introduction.md', '/guide/getting-started.md'],
+ },
+ ],
+ '/reference/': 'heading',
+ },
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // 可折叠的侧边栏
+ sidebar: {
+ '/reference/': [
+ {
+ text: 'VuePress Reference',
+ collapsible: true,
+ children: ['/reference/cli.md', '/reference/config.md'],
+ },
+ {
+ text: 'Bundlers Reference',
+ collapsible: true,
+ children: [
+ '/reference/bundler/vite.md',
+ '/reference/bundler/webpack.md',
+ ],
+ },
+ ],
+ },
+ }),
+}
+类型： number
默认值： 2
详情：
+设置根据页面标题自动生成的侧边栏的最大深度。
+0 来禁用所有级别的页面标题。1 来包含 <h2> 标题。2 来包含 <h2> 和 <h3> 标题。最大值取决于你通过 markdown.headers.level 提取了哪些级别的标题。
+由于 markdown.headers.level 的默认值是 [2, 3] ，因此 sidebarDepth 的默认最大值是 2 。
你可以通过页面的 sidebarDepth frontmatter 来覆盖这个全局配置。
+类型： boolean
默认值： true
详情：
+是否启用 编辑此页 链接。
+你可以通过页面的 editLink frontmatter 来覆盖这个全局配置。
+类型： string
详情：
+编辑此页 链接的 Pattern 。
+它将会用于生成 编辑此页 的链接。
+如果你不设置该选项，则会根据 docsRepo 配置项来推断 Pattern 。但是如果你的文档仓库没有托管在常用的平台上，比如 GitHub 、 GitLab 、 Bitbucket 、 Gitee 等，那么你必须设置该选项才能使 编辑此页 链接正常工作。
+用法：
+| Pattern | 描述 | +|
+默认主题的 Layout 布局提供了一些插槽：
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottom默认主题的 Layout 布局提供了一些插槽：
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottom在它们的帮助下，你可以很容易地添加或替换内容。下面通过一个示例来介绍一下如何使用布局插槽来继承默认主题。
+首先，创建一个客户端配置文件 .vuepress/client.ts ：
import { defineClientConfig } from 'vuepress/client'
+import Layout from './layouts/Layout.vue'
+
+export default defineClientConfig({
+ layouts: {
+ Layout,
+ },
+})
+接下来，创建 .vuepress/layouts/Layout.vue ，并使用由默认主题的 Layout 布局提供的插槽：
<script setup>
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+</script>
+
+<template>
+ <ParentLayout>
+ <template #page-bottom>
+ <div class="my-footer">This is my custom page footer</div>
+ </template>
+ </ParentLayout>
+</template>
+
+<style lang="css">
+.my-footer {
+ text-align: center;
+}
+</style>
+此时默认的 Layout 布局已经被你的本地布局覆盖，将会在除了首页外的所有页面添加一个自定义的页脚：
布局插槽十分实用，但有时候你可能会觉得它不够灵活。默认主题同样提供了替换单个组件的能力。
+默认主题将所有 非全局的组件 都注册了一个带 @theme 前缀的 alias 。例如，HomeFooter.vue 的别名是 @theme/HomeFooter.vue 。
接下来，如果你想要替换 HomeFooter.vue 组件，只需要在配置文件 .vuepress/config.ts 中覆盖这个别名即可：
import { defaultTheme } from '@vuepress/theme-default'
+import { getDirname, path } from 'vuepress/utils'
+import { defineUserConfig } from 'vuepress'
+
+const __dirname = getDirname(import.meta.url)
+
+export default defineUserConfig({
+ theme: defaultTheme(),
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+})
+除了在 .vuepress/config.ts 和 .vuepress/client.ts 中直接扩展默认主题以外，你可以通过继承默认主题来开发一个你自己的主题：
import { defaultTheme, type DefaultThemeOptions } from '@vuepress/theme-default'
+import type { Theme } from 'vuepress/core'
+import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export const childTheme = (options: DefaultThemeOptions): Theme => {
+ return {
+ name: 'vuepress-theme-child',
+ extends: defaultTheme(options),
+
+ // 在子主题的客户端配置文件中覆盖布局
+ // 注意，你在发布到 NPM 之前会将 TS 构建为 JS ，因此这里需要设置为 JS 文件的路径
+ clientConfigFile: path.resolve(__dirname, './client.js'),
+
+ // 覆盖组件别名
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+ }
+}
+如果你的站点是以英语以外的其他语言提供服务的，你应该为每个语言设置这些选项来提供翻译。
+类型： string
详情：
+项目仓库的标签。
+它将被用作 仓库链接 的文字。仓库链接 将会显示为导航栏的最后一个元素。
+如果你不明确指定该配置项，它将会根据 repo 配置项自动推断。
+如果你的站点是以英语以外的其他语言提供服务的，你应该为每个语言设置这些选项来提供翻译。
+类型： string
详情：
+项目仓库的标签。
+它将被用作 仓库链接 的文字。仓库链接 将会显示为导航栏的最后一个元素。
+如果你不明确指定该配置项，它将会根据 repo 配置项自动推断。
+类型： string
详情：
+选择语言菜单 的文字。
+如果你在站点配置中设置了多个 locales ，那么 选择语言菜单 就会显示在导航栏中仓库按钮的旁边。
+类型： string
详情：
+选择语言菜单 的 aria-label 属性。
它主要是为了站点的可访问性 (a11y) 。
+类型： string
详情：
+Locale 的语言名称。
+该配置项 仅能在主题配置的 locales 的内部生效 。它将被用作 locale 的语言名称，展示在 选择语言菜单 内。
+示例：
+export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+ theme: defaultTheme({
+ locales: {
+ '/': {
+ selectLanguageName: 'English',
+ },
+ '/zh/': {
+ selectLanguageName: '简体中文',
+ },
+ },
+ }),
+}
+类型：null | string
详情：
+导航栏中主导航 aria-label 属性的值。
类型：null | string
详情：
+下一页/上一页导航 aria-label 属性的值
类型： string
默认值： 'Edit this page'
详情：
+编辑此页 链接的文字。
+类型： string
默认值： 'Last Updated'
详情：
+最近更新时间戳 标签的文字。
+类型： string
默认值： 'Contributors'
详情：
+贡献者列表 标签的文字。
+类型： string
默认值： 'TIP'
详情：
+Tip 自定义容器 的默认标题。
+类型： string
默认值： 'WARNING'
详情：
+Warning 自定义容器 的默认标题。
+类型： string
默认值： 'DANGER'
详情：
+Danger 自定义容器 的默认标题。
+类型： string[]
默认值： ['Not Found']
详情：
+404 页面的提示信息。
+当用户进入 404 页面时，会从数组中随机选取一条信息进行展示。
+类型： string
默认值： 'Back to home'
详情：
+404 页面中 返回首页 链接的文字。
+类型： string
默认值： 'open in new window'
详情：
+ExternalLinkIcon. 链接内的 sr-only 文字。
它主要是为了站点的可访问性 (a11y) 。
+参考：
+ +类型： string
默认值： 'toggle color mode'
详情：
+切换颜色模式按钮的标题文字。
+它主要是为了站点的可访问性 (a11y) 。
+参考：
+ +类型： string
默认值： 'toggle sidebar'
详情：
+切换侧边栏按钮的标题文字。
+它主要是为了站点的可访问性 (a11y) 。
+类型： string
默认值： 'Prev'
详情：
+上一页按钮的文字。
+类型： string
默认值： 'Next'
详情：
+下一页按钮的文字。
+themePlugins 设置默认主题使用的插件。
+默认主题使用了一些插件，如果你确实不需要该插件，你可以选择禁用它。在禁用插件之前，请确保你已了解它的用途。
+import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ themePlugins: {
+ // 在这里自定义主题插件
+ },
+ }),
+}
+themePlugins 设置默认主题使用的插件。
+默认主题使用了一些插件，如果你确实不需要该插件，你可以选择禁用它。在禁用插件之前，请确保你已了解它的用途。
+import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ themePlugins: {
+ // 在这里自定义主题插件
+ },
+ }),
+}
+类型： boolean
默认值： true
详情：
+ +类型： BackToTopPluginOptions | boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-back-to-top 。
+支持对象格式以作为插件选项。
+类型： Record<ContainerType, boolean>
详情：
+是否启用由 @vuepress/plugin-container 支持的自定义容器。
+ContainerType 类型为：
tipwarningdangerdetailscodeGroupcodeGroupItem参考：
+ +类型： CopyCodePluginOptions | boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-copy-code 。
+支持对象格式以作为插件选项。
+类型： boolean
默认值： true
详情：
+ +类型： boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-git 。
+类型： boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-links-check 。
+类型： boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-medium-zoom 。
+类型： boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-nprogress 。
+类型： boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-prismjs 。
+类型： SeoPluginOptions | boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-seo 。
+支持对象格式以作为插件选项。
+类型： SitemapPluginOptions | boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-sitemap 。
+支持对象格式以作为插件选项。
+检查组件是否已全局注册。
+提示
+setup 之外调用时，你需要将 app 实例作为第二个参数传递。export const hasGlobalComponent: (name: string, app?: App) => boolean
+检查组件是否已全局注册。
+提示
+setup 之外调用时，你需要将 app 实例作为第二个参数传递。export const hasGlobalComponent: (name: string, app?: App) => boolean
+// 如果你全局注册了 `<my-component>`
+hasGlobalComponent('MyComponent') // true
+hasGlobalComponent('my-component') // true
+
+hasGlobalComponent('MyComponent2') // false
+从语言环境设置中获取当前语言环境配置。
+export const useLocaleConfig: <T extends LocaleData>(
+ localesConfig: RequiredLocaleConfig<T>,
+) => ComputedRef<T>
+const localesCOnfig = {
+ '/': 'Title',
+ '/zh/': '标题',
+}
+
+const locale = useLocaleConfig(localesConfig)
+
+// under `/page`
+locale.value // 'Title'
+
+// under `/zh/page`
+locale.value // '标题'
+此方法在 MarkdownIt 插件中很有用。有些时候你可能需要在 Markdown 插件中生成组件，并将复杂的数据写入到组件属性中，一个通常做法是使用 JSON.stringify + encodeURIComponent，并在客户端 decodeURIComponent + JSON.parse。但如果内容包含很多特殊字符，转换结果会很长。
所以我们提供 encodeData 和 decodeData 来压缩和编码内容。
此方法在 MarkdownIt 插件中很有用。有些时候你可能需要在 Markdown 插件中生成组件，并将复杂的数据写入到组件属性中，一个通常做法是使用 JSON.stringify + encodeURIComponent，并在客户端 decodeURIComponent + JSON.parse。但如果内容包含很多特殊字符，转换结果会很长。
所以我们提供 encodeData 和 decodeData 来压缩和编码内容。
export const encodeData: (
+ data: string,
+ level: DeflateOptions['level'] = 6,
+) => string
+
+export const decodeData: (compressed: string) => string
+const content = `
+{
+ "type": "bar",
+ "data": {
+ "labels": ["Red", "Blue", "Yellow", "Green", "Purple", "Orange"],
+ "datasets": [
+ {
+ "label": "# of Votes",
+ "data": [12, 19, 3, 5, 2, 3],
+ "backgroundColor": [
+ "rgba(255, 99, 132, 0.2)",
+ "rgba(54, 162, 235, 0.2)",
+ "rgba(255, 206, 86, 0.2)",
+ "rgba(75, 192, 192, 0.2)",
+ "rgba(153, 102, 255, 0.2)",
+ "rgba(255, 159, 64, 0.2)"
+ ],
+ "borderColor": [
+ "rgba(255, 99, 132, 1)",
+ "rgba(54, 162, 235, 1)",
+ "rgba(255, 206, 86, 1)",
+ "rgba(75, 192, 192, 1)",
+ "rgba(153, 102, 255, 1)",
+ "rgba(255, 159, 64, 1)"
+ ],
+ "borderWidth": 1
+ }
+ ]
+ },
+ "options": {
+ "scales": {
+ "y": {
+ "beginAtZero": true
+ }
+ }
+ }
+}
+`
+
+const prop = encodeData(content) // "eJyNUsFOwzAMve8rrHABKZqWlg5WxAE4cARxAMHEIV1NmQhNlaaCCe3fcdKtW0sLWGpjxy/v+UV512mlcIyfhTa2hHP4GgHYVYExsEQaxqlMpZWxbwAomaAqY5izO0wZB3apKnTrIyqlP1x2bRBzl9xWplC+eWNkniF7dmw1X4nWsfgaNtwNP2kfgH6Be22x9CPUUQ8yFwEHMeMQcog4UBFuiF0kcvGWGV3l6ZVW2uw0XDCTJfIwiOjYjAhESIcn4+BoT2MLio6pP6V+EBJ6AOSZgsmUwyl9A6ATwoiZn3lYTkTkRkycnuP8TU9ENPqUxuuA9i9BmxTNPy9A/G2/F9I23wtpW++FdIwPKzW2W5Afph+WqX2NQWz313XicT7XhV3qnB5f/ejKhVTYVACrXUqUmC3zC/uERsdgTYUdVr/Qb302+gZxe7S/"
+
+decodeData(prop) // will be the original content
+
+// if you use `encodeURIComponent`, it will be much longer
+encodeURIComponent(content) // '%0A%7B%0A%20%20%22type%22%3A%20%22bar%22%2C%0A%20%20%22data%22%3A%20%7B%0A%20%20%20%20%22labels%22%3A%20%5B%22Red%22%2C%20%22Blue%22%2C%20%22Yellow%22%2C%20%22Green%22%2C%20%22Purple%22%2C%20%22Orange%22%5D%2C%0A%20%20%20%20%22datasets%22%3A%20%5B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%22label%22%3A%20%22%23%20of%20Votes%22%2C%0A%20%20%20%20%20%20%20%20%22data%22%3A%20%5B12%2C%2019%2C%203%2C%205%2C%202%2C%203%5D%2C%0A%20%20%20%20%20%20%20%20%22backgroundColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%200.2)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%201)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderWidth%22%3A%201%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%0A%20%20%7D%2C%0A%20%20%22options%22%3A%20%7B%0A%20%20%20%20%22scales%22%3A%20%7B%0A%20%20%20%20%20%20%22y%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22beginAtZero%22%3A%20true%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A'
+isDef(x): 判断 x 是否定义。isBoolean(x): 判断 x 是否为布尔值。isString(x): 判断 x 是否为字符串。isNumber(x): 判断 x 是否为数字。isPlainObject(x): 判断值是否为纯对象。isArray(x): 判断 x 是否为数组isFunction(x): 判断 x 是否为函数。isRegExp(x): 判断 x 是否为正则表达式startsWith(a, b): 判断字符串 a 是否以指定字符串 b 开头endsWith(a, b): 判断字符串 a 是否以指定字符串 b 结尾当 a 不是字符串时返回 false
keys(x): 以数组形式返回对象 x 的键
values(x): 以数组形式返回对象 x 的值
entries(x): 将对象 x 转换为键值对数组。
fromEntries(x): 将键值对数组 x 转换为对象。
deepAssign(x, y, ...): Object.assign 的深度版本。
// or @vuepress/helper/client
+import { deepAssign } from '@vuepress/helper'
+
+const defaultOptions = {
+ optionA: {
+ optionA1: 'defaultOptionA1',
+ optionA2: 'defaultOptionA2',
+ optionA3: 'defaultOptionA3',
+ },
+ optionB: true,
+ optionC: 'optionC',
+}
+
+const userOptions = {
+ optionA: {
+ optionA1: 'optionA1',
+ optionA2: 'optionA2',
+ },
+ optionB: false,
+}
+
+deepAssign(defaultOptions, userOptions)
+// {
+// optionA: {
+// optionA1: "optionA1",
+// optionA2: "optionA2",
+// optionA3: "defaultOptionA3",
+// },
+// optionB: false,
+// optionC: "optionC",
+// }
+getDate(x): 将输入 x 转换为日期，可以支持 Date，时间戳，日期字符串。日期字符串的支持度以环境的 Date.parse 支持度为准。当不能转换为日期时返回 null
getDate('2021-01-01') // a Date object represents 2021-01-01
+getDate(1609459200000) // a Date object represents 2021-01-01
+getDate('2021-01-01T00:00:00.000Z') // a Date object represents 2021-01-01
+getDate('2021/01/01') // a Date object represents 2021-01-01 (might be null in some browsers)
+getDate('invalid date') // null
+getDate(undefined) // null
+getDate(-32) // null
+dateSorter: 将可转换为日期的值从新到旧排序，不能转换为日期的值会在最后。
const arr = [
+ '2020-01-01',
+ 1609459200000,
+ '2022-01-01T00:00:00.000Z',
+ '2023/01/01',
+ 'invalid date',
+ undefined,
+ -32,
+]
+
+arr.sort(dateSorter)
+// [
+// '2023/01/01',
+// '2022-01-01T00:00:00.000Z',
+// 1609459200000,
+// '2020-01-01',
+// 'invalid date',
+// undefined,
+// -32,
+// ]
+isLinkHttp(x): x 是否是有效的 HTTP URL。isLinkWithProtocol(x): x 是否是有效的带有协议的 URL。isLinkExternal(x): x 是否是有效的外部 URL。isLinkAbsolute(x): x 是否是有效的绝对 URL。ensureEndingSlash(x): 确保 x 以斜杠结尾。ensureLeadingSlash(x): 确保 x 以斜杠开头。removeEndingSlash(x): 确保 x 不以斜杠结尾。removeLeadingSlash(x): 确保 x 不以斜杠开头。来到你的博客，或是任意位置，放置 Artalk 评论框，让页面具备丰富的社会化功能。
+]]>来到你的博客，或是任意位置，放置 Artalk 评论框，让页面具备丰富的社会化功能。
+ +npm i -D artalk
+请参见 Artalk 文档。
+请配置 provider: "Artalk" 并将你的服务端地址传入插件选项中的 server。
其他的配置项详见 Artalk 配置。
+提示
+插件保留 el 选项在页面自行插入 Artalk。同时插件会自动根据 VuePress 信息为你自动设置 pageTitle, pageKey 和 site 选项。
为了能使 Artalk 应用正确的主题，你需要通过 darkmode 属性向 <CommentService /> 传入一个布尔值，代表当前是否开启夜间模式。
详见 Artalk 配置。
+el pageTitle, pageKey 和 site 选项为插件的保留选项，将从 VuePress 配置中自动推断，不可设置。
imgUploader 和 avatarURLBuilder 这两个函数选项只能在客户端配置。
详见 Artalk 配置。
+el pageTitle, pageKey 和 site 选项为插件的保留选项，将从 VuePress 配置中自动推断，不可设置。
imgUploader 和 avatarURLBuilder 这两个函数选项只能在客户端配置。
你可以直接在插件选项中配置可序列化的选项:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineArtalkConfig 函数来配置 Artalk。
import { defineClientConfig } from 'vuepress/client'
+import { defineArtalkConfig } from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // Artalk 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+你需要创建一个公开仓库，并开启评论区，以作为评论存放的地点
+你需要安装 Giscus App，使其有权限访问对应仓库。
+在完成以上步骤后，请前往 Giscus 页面 获得你的设置。
+你只需要填写仓库和 Discussion 分类，之后滚动到页面下部的 “启用 giscus” 部分，获取 data-repo, data-repo-id, data-category 和 data-category-id 这四个属性。
请配置 provider: "Giscus" 并将 data-repo, data-repo-id, data-category 和 data-category-id 作为插件选项传入 repo, repoId, category categoryId。
其他的配置项详见 Giscus 配置。
+默认情况下，Giscus 使用 light 或 dark 主题 (基于夜间模式状态)。
::: info 夜间模式
+为了能使 Giscus 应用正确的主题，你需要为 <CommentService /> 通过 darkmode 属性传入一个布尔值，代表当前是否开启夜间模式。
:::
+如果你想在日间模式和夜间模式下自定义主题，你可以设置 lightTheme 和 darkTheme 选项，使用内置主题关键字或以 https:// 开头的自定义 css 链接。
stringstringstringstringstringstringstringstring"pathname"booleantruebooleantruebooleantrue"top" | "bottom""top"类型: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+默认值: "light"
详情：
+Giscus 在日间模式下使用的主题
+应为一个内置主题关键词或者一个 CSS 链接。
+类型: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+默认值: "dark"
详情：
+Giscus 在夜间模式下使用的主题
+应为一个内置主题关键词或者一个 CSS 链接。
+你可以直接在插件选项中配置可序列化的选项:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Giscus',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineGiscusConfig 函数来配置 Giscus。
import { defineClientConfig } from 'vuepress/client'
+import { defineGiscusConfig } from 'vuepress-plugin-comment2/client'
+
+defineGiscusConfig({
+ // Giscus 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+npm i -D twikoo
+部署共有四种方式。
+| 部署方式 | 描述 | +|
+]]>stringstring"ap-shanghai"你可以直接在插件选项中配置可序列化的选项:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Twikoo',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+stringstring"ap-shanghai"你可以直接在插件选项中配置可序列化的选项:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Twikoo',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineTwikooConfig 函数来配置 Twikoo。
import { defineClientConfig } from 'vuepress/client'
+import { defineTwikooConfig } from 'vuepress-plugin-comment2/client'
+
+defineTwikooConfig({
+ // Twikoo 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+npm i -D @waline/client
+点击左上角 创建应用 并起一个你喜欢的名字 (请选择免费的开发版):
+ +进入应用，选择左下角的 设置 > 应用 Key。你可以看到你的 APP ID,APP Key 和 Master Key。请记录它们，以便后续使用。
国内版需要完成备案接入
+如果你正在使用 Leancloud 国内版 (leancloud.cn)，我们推荐你切换到国际版 (leancloud.app)。否则，你需要为应用额外绑定已备案的域名，同时购买独立 IP 并完成备案接入:
+设置 > 域名绑定 > API 访问域名 > 绑定新域名 > 输入域名 > 确定。点击上方按钮，跳转至 Vercel 进行 Server 端部署。
+::: note
+如果你未登录的话，Vercel 会让你注册或登录，请使用 GitHub 账户进行快捷登录。
+:::
+输入一个你喜欢的 Vercel 项目名称并点击 Create 继续:
此时 Vercel 会基于 Waline 模板帮助你新建并初始化仓库，仓库名为你之前输入的项目名。
+
一两分钟后，满屏的烟花会庆祝你部署成功。此时点击 Go to Dashboard 可以跳转到应用的控制台。
点击顶部的 Settings - Environment Variables 进入环境变量配置页，并配置三个环境变量 LEAN_ID, LEAN_KEY 和 LEAN_MASTER_KEY 。它们的值分别对应上一步在 LeanCloud 中获得的 APP ID, APP KEY, Master Key。
::: note
+如果你使用 LeanCloud 国内版，请额外配置 LEAN_SERVER 环境变量，值为你绑定好的域名。
:::
+环境变量配置完成之后点击顶部的 Deployments 点击顶部最新的一次部署右侧的 Redeploy 按钮进行重新部署。该步骤是为了让刚才设置的环境变量生效。
此时会跳转到 Overview 界面开始部署，等待片刻后 STATUS 会变成 Ready。此时请点击 Visit ，即可跳转到部署好的网站地址，此地址即为你的服务端地址。
点击顶部的 Settings - Domains 进入域名配置页
输入需要绑定的域名并点击 Add
在域名服务器商处添加新的 CNAME 解析记录
| Type | Name | Value | +|
+string类型: (WalineEmojiInfo | WalineEmojiPresets)[] | false
type WalineEmojiPresets = `http://${string}` | `https://${string}`
+
+interface WalineEmojiInfo {
+ /**
+ * 选项卡上的 Emoji 名称
+ */
+ name: string
+ /**
+ * 所在文件夹链接
+ */
+ folder?: string
+ /**
+ * Emoji 通用路径前缀
+ */
+ prefix?: string
+ /**
+ * Emoji 图片的类型，会作为文件扩展名使用
+ */
+ type?: string
+ /**
+ * 选项卡显示的 Emoji 图标
+ */
+ icon: string
+ /**
+ * Emoji 图片列表
+ */
+ items: string[]
+}
+默认值: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
参考：
+详情：表情设置
+string类型: (WalineEmojiInfo | WalineEmojiPresets)[] | false
type WalineEmojiPresets = `http://${string}` | `https://${string}`
+
+interface WalineEmojiInfo {
+ /**
+ * 选项卡上的 Emoji 名称
+ */
+ name: string
+ /**
+ * 所在文件夹链接
+ */
+ folder?: string
+ /**
+ * Emoji 通用路径前缀
+ */
+ prefix?: string
+ /**
+ * Emoji 图片的类型，会作为文件扩展名使用
+ */
+ type?: string
+ /**
+ * 选项卡显示的 Emoji 图标
+ */
+ icon: string
+ /**
+ * Emoji 图片列表
+ */
+ items: string[]
+}
+默认值: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
参考：
+详情：表情设置
+类型: string | boolean
默认值: false
参考：
+详情：
+暗黑模式适配。
+'auto' 会根据设备暗黑模式自适应。类型: WalineCommentSorting
默认值: 'latest'
详情：
+评论列表排序方式。可选值: 'latest', 'oldest', 'hottest'
类型: string[]
默认值: ['nick', 'mail', 'link']
详情：
+评论者相关属性。可选值: 'nick', 'mail', 'link'
类型: string[]
默认值: []
详情：
+设置必填项，默认匿名，可选值:
+[]['nick']['nick', 'mail']string'enable'登录模式状态，可选值:
+'enable': 启用登录 (默认)'disable': 禁用登录，用户只能填写信息评论'force': 强制登录，用户必须注册并登录才可发布评论类型: number | [number, number]
默认值: 0
详情：
+评论字数限制。填入单个数字时为最大字数限制。设置为 0 时无限制。
number10类型: WalineImageUploader | false
详情:
+type WalineImageUploader = (image: File) => Promise<string>
+参考:
+ +详情：
+自定义图片上传方法。默认行为是将图片 Base 64 编码嵌入，你可以设置为 false 以禁用图片上传功能。
函数应该接收图片对象，返回一个提供图片地址的 Promise。
+类型: WalineHighlighter | false
type WalineHighlighter = (code: string, lang: string) => string
+参考:
+ +详情：
+代码高亮，默认使用一个 < 1kb 的简单高亮器。函数传入代码块的原始字符和代码块的语言。你应该直接返回一个字符串。
+你可以传入一个自己的代码高亮器，也可以设置为 false 以禁用代码高亮功能。
类型: WalineTexRenderer | false
type WalineTexRenderer = (blockMode: boolean, tex: string) => string
+参考:
+ +详情：
+自定义 TeX 渲染，默认行为是提示预览模式不支持 TeX。函数提供两个参数，第一个参数表示渲染模式是否为块级，第二个参数是 TeX 的字符串，并返回一段 HTML 字符串作为渲染结果。
+你可以自行引入 TeX 渲染器并提供预览渲染，建议使用 Katex 或 MathJax，也可以设置为 false 以禁止渲染 TeX。
类型: WalineSearchOptions | false
interface WalineSearchImageData extends Record<string, unknown> {
+ /**
+ * 图片链接
+ */
+ src: string
+
+ /**
+ * 图片标题
+ *
+ * @description 用于图片的 alt 属性
+ */
+ title?: string
+
+ /**
+ * 图片缩略图
+ *
+ * @description 为了更好的加载性能，我们会优先在列表中使用此缩略图
+ *
+ * @default src
+ */
+ preview?: string
+}
+
+type WalineSearchResult = WalineSearchImageData[]
+
+interface WalineSearchOptions {
+ /**
+ * 搜索操作
+ */
+ search: (word: string) => Promise<WalineSearchResult>
+
+ /**
+ * 打开列表时展示的默认结果
+ *
+ * @default () => search('')
+ */
+ default?: () => Promise<WalineSearchResult>
+
+ /**
+ * 获取更多的操作
+ *
+ * @description 会在列表滚动到底部时触发，如果你的搜索服务支持分页功能，你应该设置此项实现无限滚动
+ *
+ * @default (word) => search(word)
+ */
+ more?: (word: string, currentCount: number) => Promise<WalineSearchResult>
+}
+详情：自定义搜索功能，设置 false 可禁用搜索。
类型: string
详情：
+reCAPTCHA V3 是 Google 提供的验证码服务，配置 reCAPTCHA V3 网站密钥即可开启该功能。
+服务端需要同步配置 RECAPTCHA_V3_SECRET 环境变量。
类型: boolean | string[]
默认值: false
详情：
+为文章增加表情互动功能，设置为 true 提供默认表情，也可以通过设置表情地址数组来自定义表情图片，最大支持 8 个表情。
类型: boolean
默认值: true
详情：
+是否导入 Meta 图标。
+类型: WalineLocales
interface WalineLocales {
+ [localePath: string]: WalineLocale
+}
+参考:
+详情：
+Waline 多语言配置
+你可以直接在插件选项中配置可序列化的选项:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Waline',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineWalineConfig 函数来配置 Waline。
import { defineClientConfig } from 'vuepress/client'
+import { defineWalineConfig } from 'vuepress-plugin-comment2/client'
+
+defineWalineConfig({
+ // Waline 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+所有函数都应在 extendsBundlerOptions 生命周期挂钩中调用。
提示
+我们在示例中省略了它。 实际代码应该是这样的：
+// 导入你需要的函数
+import { addCustomElement } from '@vuepress/helper'
+
+export const yourPlugin = {
+ // ...
+ extendsBundlerOptions: (bundlerOptions, app) => {
+ // 在此添加它们
+ addCustomElement(bundlerOptions, app, 'my-custom-element')
+ },
+}
+所有函数都应在 extendsBundlerOptions 生命周期挂钩中调用。
提示
+我们在示例中省略了它。 实际代码应该是这样的：
+// 导入你需要的函数
+import { addCustomElement } from '@vuepress/helper'
+
+export const yourPlugin = {
+ // ...
+ extendsBundlerOptions: (bundlerOptions, app) => {
+ // 在此添加它们
+ addCustomElement(bundlerOptions, app, 'my-custom-element')
+ },
+}
+获取当前打包器的名称。
+export const getBundlerName: (app: App) => string
+// @vuepress/bundler-vite
+getBundleName(app) === 'vite' // true
+// @vuepress/bundler-webpack
+getBundleName(app) === 'webpack' // true
+将自定义元素声明添加到当前的打包器。
+interface CustomElementCommonOptions {
+ app: App;
+ config: unknown;
+}
+/**
+ * Add tags as customElement
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param customElements tags recognized as custom element
+ */
+export const addCustomElement = (
+ bundlerOptions: unknown,
+ app: App,
+ customElement: string[] | string | RegExp
+) => void;
+import { addCustomElement } from '@vuepress/helper'
+
+addCustomElement(bundlerConfig, app, 'my-custom-element')
+addCustomElement(bundlerOptions, app, [
+ 'custom-element1',
+ 'custom-element2',
+ // all tags start with `math-`
+ /^math-/,
+])
+为开发服务器中的特定路径提供内容。
+export interface DevServerOptions {
+ /**
+ * Path to be responded
+ */
+ path: string;
+ /**
+ * Respond function
+ */
+ response: (request?: IncomingMessage) => Promise<string | Buffer>;
+
+ /**
+ * error msg
+ */
+ errMsg?: string;
+}
+
+/**
+ * Handle specific path when running VuePress Dev Server
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param path Path to be responded
+ * @param response respond function
+ * @param errMsg error msg
+ */
+export const customizeDevServer: (
+ bundlerOptions: unknown,
+ app: App,
+ {
+ errMsg:"The server encountered an error",
+ response: responseHandler,
+ path,
+ }: CustomServerOptions
+) => void;
+import { useCustomDevServer } from '@vuepress/helper'
+
+// handle `/api/` path
+useCustomDevServer(bundlerOptions, app, {
+ path: '/api/',
+ response: async () => getData(),
+ errMsg: 'Unexpected api error',
+})
+addViteOptimizeDepsInclude
+向 Vite optimizeDeps.include 列表中添加模块
提示
+如果一个包满足下列条件之一，你应该考虑将它添加至此。
+import() 动态导入addViteOptimizeDepsExclude
+向 Vite optimizeDeps.exclude 列表中添加模块
如果一个包和它的依赖都是纯 ESM 包，你应该考虑将它添加至此。
+addViteSsrExternal
+向 Vite ssr.external 列表中添加模块
如果一个包是纯 ESM 包，且未使用别名 (alias) 或定义变量 (define)，你应该考虑将它添加至此。
+addViteSsrNoExternal
+向 Vite ssr.noExternal 列表中添加模块
如果一个包内使用了别名 (alias) 或定义变量 (define)，你必须将它添加至此。
+/**
+ * Add modules to Vite `optimizeDeps.include` list
+ */
+export const addViteOptimizeDepsInclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `optimizeDeps.exclude` list
+ */
+export const addViteOptimizeDepsExclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.external` list
+ */
+export const addViteSsrExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.noExternal` list
+ */
+export const addViteSsrNoExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+import {
+ addViteOptimizeDepsInclude,
+ addViteOptimizeDepsExclude,
+ addViteSsrExternal,
+ addViteSsrNoExternal,
+} from '@vuepress/helper'
+
+addViteOptimizeDepsInclude(bundlerOptions, app, ['vue', 'vue-router'])
+addViteOptimizeDepsExclude(bundlerOptions, app, 'packageA')
+addViteSsrNoExternal(bundlerOptions, app, ['vue', 'vue-router'])
+addViteSsrExternal(bundlerOptions, app, 'packageA')
+addViteConfig
+A function for you to add vite config
+export const addViteConfig: (
+ bundlerOptions: unknown,
+ app: App,
+ config: Record<string, unknown>,
+) => void
+import { addViteConfig } from '@vuepress/helper'
+
+addViteConfig(bundlerOptions, app, {
+ build: {
+ charset: 'utf8',
+ },
+})
+mergeViteConfig
+无需导入 vite 即可合并 vite 配置的功能
+export const mergeViteConfig: (
+ defaults: Record<string, any>,
+ overrides: Record<string, any>,
+) => Record<string, any>
+注意
+你不应将 vite 作为依赖，因为你的的用户可能选择其他打包器！
+import { mergeViteConfig } from "@vuepress/helper";
+
+config.viteOptions mergeViteConfig(config.viteOptions, {
+ build: {
+ charset: "utf8",
+ },
+});
+chainWebpack
+链式修改 webpack 配置.
+export const chainWebpack: (
+ { app, config }: WebpackCommonOptions,
+ chainWebpack: (
+ config: WebpackChainConfig,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { chainWebpack } from '@vuepress/helper'
+
+chainWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+configWebpack
+配置 Webpack
+export const configWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ configureWebpack: (
+ config: WebpackConfiguration,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { configWebpack } from '@vuepress/helper'
+
+configWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+获取页面摘要。
+export interface PageExcerptOptions {
+ /**
+ * 摘要分隔符
+ *
+ * @default "获取页面摘要。
+export interface PageExcerptOptions {
+ /**
+ * 摘要分隔符
+ *
+ * @default "<!-- more -->"
+ */
+ separator?: string
+
+ /**
+ * 摘要的长度
+ *
+ * @description 摘要的长度会尽可能的接近这个值
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * 被认为是自定义元素的标签
+ *
+ * @description 用于判断一个标签是否是自定义元素，因为在摘要中，所有的未知标签都会被移除。
+ */
+ isCustomElement?: (tagName: string) => boolean
+
+ /**
+ * 是否保留页面标题 (第一个 h1)
+ *
+ * @default false
+ */
+ keepPageTitle?: boolean
+
+ /**
+ * 是否保留代码块的标签，诸如行号和高亮行
+ *
+ * @default false
+ */
+ keepFenceDom?: boolean
+}
+
+export const getPageExcerpt: (
+ app: App,
+ page: Page,
+ options?: PageExcerptOptions,
+) => string
+获取页面纯文本。
+export interface PageTextOptions {
+ /**
+ * 是否将文字转换成单行内容
+ *
+ * @default false
+ */
+ singleLine?: boolean
+
+ /**
+ * 文字的长度
+ *
+ * @description 文字的长度会尽可能的接近这个值
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * 需要移除的标签
+ *
+ * @description 默认情况下表格和代码块会被移除
+ *
+ * @default ['table', 'pre']
+ */
+ removedTags?: string[]
+}
+
+export const getPageText: (
+ app: App,
+ page: Page,
+ options?: PageTextOptions,
+) => string
+| Last update time: | +
+ |
+
| Author: | +
+ |
+
| Contributor: | +
+ |
+
| Categories: | +
+ |
+
| Copyright: | +
+ |
+
类型: (page: Page) => Record<string, unknown>
必填: 否
\n参考:
\n详情：
\n获取文章信息的函数。
\n获取到的信息会被稍后注入至路由元数据，以便你可以在客户端中通过组合式 API 获取。
\n类型: (page: Page) => boolean
默认值: (page) => Boolean(page.filePathRelative) && !page.frontmatter.home
参考:
\n详情：
\n页面过滤器，此函数用于鉴别页面是否作为文章。
\n默认情况下，所有从 Markdown 源文件中生成的非主页页面，会被作为文章。
\n类型: BlogCategoryOptions[]
必填: 否
\n详情：
\n详情：
\n博客分类配置，详见 博客分类配置。
\n类型: BlogTypeOptions[]
必填: 否
\n参考：
\n详情：
\n博客分类配置，详见 博客类型配置。
\n(name: string) => string(name) => name.replace(/ _/g, '-').replace(/[:?*|\\\\/<>]/g, \"\").toLowerCase()booleantruestring<!-- more -->类型: number
默认值: 300
参考：
\n详情：
\n自动生成的摘要的长度。
\n提示
\n摘要的长度会尽可能的接近这个值。如果设置为 0，意味着不自动生成摘要。
类型: (page: Page) => boolean
默认值: filter 选项
参考：
\n详情：\n页面过滤器，此函数用于鉴别插件是否需要生成摘要。
\n提示
\n你可以使用此函数来跳过你不需要生成摘要的页面。例如：如果用户在 frontmatter 中设置了 excerpt 或 description，你可能希望直接使用它们。
类型: (tagName: string) => boolean
默认值: () => false
参考：
\n详情：\n被认为是自定义元素的标签。
\n用于判断一个标签是否是自定义元素，因为在摘要中，所有的未知标签都会被移除。
\n类型: string
默认值: \"_blog\"
详情：\n注入文章信息至路由元数据时使用的键名。
\n提示
\n设置为空字符串会直接注入路由元数据 (而不是一个键下)。
\n类型: boolean
默认值: 是否使用 --debug 标记
详情：\n是否在开发服务器中启用实时热重载。
\n致主题开发者
\n默认情况下它是禁用的，因为它确实会对具有很多分类和类别的站点产生性能影响，并且在编辑 Markdown 时会减慢热重载的速度。
\n如果用户正在添加或组织类别或标签，你可以告诉他们启用此功能，其余的时间最好禁用它。
\n此外，你可以尝试检测用户项目中的页面数并决定是否启用它。
\n博客分类配置应为一个数组，每一项控制一个分类规则。
\ninterface BlogCategoryOptions {\n /**\n * 唯一的分类名称\n */\n key: string\n\n /**\n * 从页面中获取分类的函数\n */\n getter: (page: Page) => string[]\n\n /**\n * 页面排序器\n */\n sorter?: (pageA: Page, pageB: Page) => number\n\n /**\n * 待注册的页面路径图案\n *\n * @description `:key` 将会被替换为原 key 的 slugify 结果\n *\n * @default `/:key/`\n */\n path?: string | false\n\n /**\n * 页面布局组件名称\n *\n * @default 'Layout'\n */\n layout?: string\n\n /**\n * Front Matter 配置\n */\n frontmatter?: (localePath: string) => Record<string, string>\n\n /**\n * 待注册的项目页面路径图案或自定义函数\n *\n * @description 当填入字符串的时候, `:key` 和 `:name` 会被自动替换为原始的 key、name 的 slugify 结果。\n *\n * @default `/:key/:name/`\n */\n itemPath?: string | ((name: string) => string) | false\n\n /**\n * 项目页面布局组件名称\n *\n * @default 'Layout'\n */\n itemLayout?: string\n\n /**\n * 项目 Front Matter 配置\n */\n itemFrontmatter?: (name: string, localePath: string) => Record<string, string>\n}\n博客类型配置应为一个数组，每一项控制一个类型规则。
\ninterface BlogTypeOptions {\n /**\n * 唯一的类型名称\n */\n key: string\n\n /**\n * 一个过滤函数来决定页面是否满足此类型\n */\n filter: (page: Page) => boolean\n\n /**\n * 页面排序器\n */\n sorter?: (pageA: Page, pageB: Page) => number\n\n /**\n * 待注册的页面路径\n *\n * @default '/:key/'\n */\n path?: string | false\n\n /**\n * 页面布局组件名称\n *\n * @default 'Layout'\n */\n layout?: string\n\n /**\n * Front Matter 配置\n */\n frontmatter?: (localePath: string) => Record<string, string>\n}\n你可以从 @vuepress/plugin-blog/client 导入下列 API:
博客分类
\nconst useBlogCategory: <\n T extends Record<string, unknown> = Record<string, unknown>,\n>(\n key?: string,\n) => ComputedRef<BlogCategoryData<T>>\n参数 key 为需要获取的键名。如果未传入 key，会尝试使用与当前路径匹配的 key。
博客类型
\nconst useBlogType: <\n T extends Record<string, unknown> = Record<string, unknown>,\n>(\n key?: string,\n) => ComputedRef<BlogTypeData<T>>\n参数 key 为需要获取的键名。如果未传入 key，会尝试使用与当前路径匹配的 key。
详细的返回值如下:
\ninterface Article<T extends Record<string, unknown> = Record<string, unknown>> {\n /** 文章路径 */\n path: string\n /** 文章信息 */\n info: T\n}\n\ninterface BlogCategoryData<\n T extends Record<string, unknown> = Record<string, unknown>,\n> {\n /** 分类路径 */\n path: string\n\n /**\n * 仅当当前路径和某个子项目匹配时可用\n */\n currentItems?: Article<T>[]\n\n /** 分类映射 */\n map: {\n /** 当前分类下全局唯一的 key */\n [key: string]: {\n /** 对应键值的分类路径 */\n path: string\n /** 对应键值的项目 */\n items: Article<T>[]\n }\n }\n}\n\ninterface BlogTypeData<\n T extends Record<string, unknown> = Record<string, unknown>,\n> {\n /** 类别路径 */\n path: string\n\n /** 当前类别下的项目 */\n items: Article<T>[]\n}\n使用 @vuepress/plugin-blog，你可以轻松地将博客功能引入主题。
起步时，插件会首选过滤并选择那些需要作为文章的页面。这将剔除你不想要的页面，并在后续处理中排除它们。
\n默认情况下，所有从 Markdown 文件生成但不是主页的页面，都将被视作文章。
\n你可能需要设置 filter 选项来完全自定义要收集的页面。 filter 接受一个形状为 (page: Page) => boolean 的函数。
接着，你应该设置 getInfo 选项为一个接受 Page 作为参数并返回包含所需信息的对象的函数。这样稍后，你可以从组合 API 中获取这些信息。
import { blogPlugin } from '@vuepress/plugin-blog'\n\nexport default {\n name: 'vuepress-theme-xxx',\n plugins: [\n blogPlugin({\n filter: ({ filePathRelative, frontmatter }) => {\n // 舍弃那些不是从 Markdown 文件生成的页面\n if (!filePathRelative) return false\n\n // 舍弃 `archives` 文件夹的页面\n if (filePathRelative.startsWith('archives/')) return false\n\n // 舍弃那些没有使用默认布局的页面\n if (frontmatter.home || frontmatter.layout) return false\n\n return true\n },\n\n getInfo: ({ frontmatter, git = {}, data = {} }) => {\n // 获取页面信息\n const info: Record<string, any> = {\n author: frontmatter.author || '',\n categories: frontmatter.categories || [],\n date: frontmatter.date || git.createdTime || null,\n tags: frontmatter.tags || [],\n excerpt: data.excerpt || '',\n }\n\n return info\n },\n }),\n // 其他插件 ...\n ],\n}\n基本上，你的博客中需要两种“类型”:
\n类别:
\n“类别”是用文章的标签 (或类别) 对它们进行分组。
\n例如，每篇文章可能都有对应的“分类”和“标签”。
\n类型:
\n“类型”是过滤不同条件的文章。
\n例如，你的帖子中可能有日记或笔记。当帖子带有写作日期信息时，它可以称为“时间线项目”。
\n了解这两种类型的描述后，你可以设置 category 和 type 选项，它们都接受一个数组，每个元素代表一个配置。
让我们从此处 2 个例子开始。
\n假设你想为每篇文章设置标签，并且你正在通过 frontmatter.tag 设置它们。同时，你想要在 /tag/ 中使用 TagMap 布局的标签页面，并在/tag/标签名称 中使用 TagList 布局对标签按名称进行分组，你可能需要这样的配置:
import { blogPlugin } from '@vuepress/plugin-blog'\n\nexport default {\n name: 'vuepress-theme-xxx',\n plugins: [\n blogPlugin({\n // 其他配置 ...\n category: [\n {\n key: 'tag',\n getter: ({ frontmatter }) => frontmatter.tag || [],\n path: '/tag/',\n layout: 'TagMap',\n frontmatter: () => ({ title: '标签页' }),\n itemPath: '/tag/:name/',\n itemLayout: 'TagList',\n itemFrontmatter: (name) => ({ title: `${name}标签` }),\n },\n ],\n }),\n // 其他插件 ...\n ],\n}\n此外，你可能希望为你的一些文章加注星标，并将其展示给访问者。当你在 frontmatter 中设置 star: true 来标记它们时，你可能需要这样的配置来在 /star/ 路径中以 StarList 布局显示它们:
import { blogPlugin } from '@vuepress/plugin-blog'\n\nexport default {\n name: 'vuepress-theme-xxx',\n plugins: [\n blogPlugin({\n // 其他配置 ...\n type: [\n {\n key: 'star',\n filter: ({ frontmatter }) => frontmatter.star,\n path: '/star/',\n layout: 'StarList',\n frontmatter: () => ({ title: '星标文章' }),\n },\n ],\n }),\n // 其他插件 ...\n ],\n}\n看，设置这两种类型很容易。有关完整选项，请参阅 博客分类配置 和 博客分类配置。
\n当生成每个页面时，插件将在 frontmatter.blog 中设置如下信息
interface BlogFrontmatterOptions {\n /** 当前页面的类型 */\n type: 'category' | 'type'\n /** 在当前分类或类别下全局唯一的 key */\n key: string\n /**\n * 当前的分类名称\n *\n * @description 仅在分类子项目页面中可用\n */\n name?: string\n}\n所以你可以直接调用 useBlogCategory() 和 useBlogType()，结果将是当前路由绑定的类别或类型。
此外，你可以通过传递所需的 key 作为参数，来将获得绑定到该 key 的信息。
对于上方的 Node 配置而言，你可以在客户端通过如下方式获取 tag 和 star 的信息:
\nTagMap 布局:
<template>\n <div>\n <h1>Tag page</h1>\n <ul>\n <li v-for=\"({ items, path }, name) in categoryMap.map\">\n <RouteLink :key=\"name\" :to=\"path\" class=\"category\">\n {{ name }}\n <span class=\"category-num\">\n {{ items.length }}\n </span>\n </RouteLink>\n </li>\n </ul>\n </div>\n</template>\n<script setup lang=\"ts\">\nimport { useBlogCategory } from '@vuepress/plugin-blog'\nimport { RouteLink } from 'vuepress/client'\n\nconst categoryMap = useBlogCategory('tag')\n</script>\nTagList 布局:
<template>\n <div>\n <h1>Tag page</h1>\n <div class=\"category-wrapper\">\n <RouteLink\n v-for=\"({ items, path }, name) in categoryMap.map\"\n :key=\"name\"\n :to=\"path\"\n class=\"category\"\n >\n {{ name }}\n <span class=\"category-num\">\n {{ items.length }}\n </span>\n </RouteLink>\n </div>\n <div class=\"article-wrapper\" v-if=\"categoryMap.currentItems\">\n <div v-if=\"!categoryMap.currentItems.length\">Nothing in here.</div>\n <article\n v-for=\"{ info, path } in categoryMap.currentItems\"\n class=\"article\"\n @click=\"$router.push(path)\"\n >\n <header class=\"title\">\n {{\n (isTimeline\n ? `${new Date(info.date).toLocaleDateString()}: `\n : '') + info.title\n }}\n </header>\n <hr />\n <div class=\"article-info\">\n <span v-if=\"info.author\" class=\"author\"\n >Author: {{ info.author }}</span\n >\n <span v-if=\"info.date && !isTimeline\" class=\"date\"\n >Date: {{ new Date(info.date).toLocaleDateString() }}</span\n >\n <span v-if=\"info.category\" class=\"category\"\n >Category: {{ info.category.join(', ') }}</span\n >\n <span v-if=\"info.tag\" class=\"tag\"\n >Tag: {{ info.tag.join(', ') }}</span\n >\n </div>\n <div v-if=\"info.excerpt\" class=\"excerpt\" v-html=\"info.excerpt\" />\n </article>\n </div>\n </div>\n</template>\n<script setup lang=\"ts\">\nimport { useBlogCategory } from '@vuepress/plugin-blog'\nimport { RouteLink } from 'vuepress/client'\n\nconst categoryMap = useBlogCategory('tag')\n</script>\nStarList 布局:
<template>\n <div class=\"article-wrapper\" v-if=\"stars.items\">\n <div v-if=\"!stars.items.length\">Nothing in here.</div>\n <article\n v-for=\"{ info, path } in stars.items\"\n class=\"article\"\n @click=\"$router.push(path)\"\n >\n <header class=\"title\">\n {{\n (isTimeline ? `${new Date(info.date).toLocaleDateString()}: ` : '') +\n info.title\n }}\n </header>\n <hr />\n <div class=\"article-info\">\n <span v-if=\"info.author\" class=\"author\">Author: {{ info.author }}</span>\n <span v-if=\"info.date && !isTimeline\" class=\"date\"\n >Date: {{ new Date(info.date).toLocaleDateString() }}</span\n >\n <span v-if=\"info.category\" class=\"category\"\n >Category: {{ info.category.join(', ') }}</span\n >\n <span v-if=\"info.tag\" class=\"tag\">Tag: {{ info.tag.join(', ') }}</span>\n </div>\n <div v-if=\"info.excerpt\" class=\"excerpt\" v-html=\"info.excerpt\" />\n </article>\n </div>\n</template>\n<script setup lang=\"ts\">\nimport { useBlogType } from '@vuepress/plugin-blog/client'\n\nimport ArticleList from '../components/ArticleList.vue'\nimport ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'\n\nconst stars = useBlogType('star')\n</script>\n有关返回类型，请参阅 Composition API 返回类型。
\n该插件添加了原生多语言支持，因此你的设置将自动应用于每种语言。
\n例如，如果用户进行了以下 locales 配置，并且你正在设置上面的“star”示例:
\nexport default {\n locales: {\n '/': {\n lang: 'en-US',\n },\n '/zh/': {\n lang: 'zh-CN',\n },\n },\n}\n那么 /zh/star/ 和 /star/ 都将可用，并且只会显示对应语言下的文章。
这个插件提供了一个内置的摘要生成器，可以通过将 excerpt 选项设置为 true 来启用。
摘要介绍
\n摘要是一个 HTML 片段，被用于在博客列表中显示文章的简短描述，所以摘要有如下限制:
\nisCustomElement 选项。.vuepress/public 的绝对路径或完整路径以确保它们可以在其他地址被访问。摘要生成器将尝试从 Frontmatter 内容中找到有效的摘要分隔符，如果找到，它将使用分隔符之前的内容，分隔符默认为 <!-- more -->，并且你可以通过 excerptSeparator 选项来自定义它。
如果找不到有效的分隔符，它将从 Markdown 文件的开头开始解析内容，直到长度达到预设值时停止。该值默认为 300，你可以通过设置 excerptLength 选项来自定义它。
要选择哪个页面应该生成摘要，你可以使用 excerptFilter 选项。
示例
\n通常，如果用户设置了 frontmatter.description，你可能希望使用它们，因此如果 frontmatter.description 不为空，你可以让过滤器函数返回 false。
你既可以在 Node.js 一侧使用插件选项设置选项，也可以通过客户端配置文件在浏览器一侧设置选项。
\nimport { commentPlugin } from 'vuepress-plugin-comment2'\n\n// .vuepress/config.ts\nexport default {\n plugins: [\n commentPlugin({\n provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo\n\n // 在这里放置其他选项\n // ...\n }),\n ],\n}\nimport { defineClientConfig } from 'vuepress/client'\nimport {\n defineArtalkConfig,\n // defineGiscusConfig,\n // defineTwikooConfig,\n // defineWalineConfig,\n} from 'vuepress-plugin-comment2/client'\n\ndefineArtalkConfig({\n // 选项\n})\n\nexport default defineClientConfig({\n // ...\n})\n有以下你需要注意的限制：
\nprovider、多语言设置和其他资源相关选项必须在插件选项中设置。
为确保 tree-shaking 有效，我们必须在 Node 一侧优化入口，以便打包器可以了解最终打包中应包含哪些资源。
\n这些选项将在配置参考中用
\n不能序列化为 JSON 的选项必须在客户端配置中设置。
\n接收复杂值的选项（例如：函数）不能在插件选项中设置，因为插件运行在 Node.js 环境下，所以我们无法将这些值和它们的上下文传递给浏览器。
\n这些选项将在配置参考中用
\n该插件全局注册了一个组件 <CommentService />。
alias 和布局槽来插入组件。 我们建议你在 <PageNav /> 组件之后插入评论组件 (<CommentService />)，本页可作为一个 Demo 作为参考。默认情况下，<CommentService /> 组件是全局启用的，你可以在插件选项和页面 frontmatter 中使用 comment 选项来控制它。
comment: false 在本地禁用它。comment 设置为 false。 然后你可以在页面 frontmatter 中设置 comment: true 以在局部启用它。你可以在页面 frontmatter 中设置 commentID 选项来自定义评论 ID，该 ID 用于标识要用于页面的评论存储项。默认情况下，它将是页面的 path ，这意味着如果你将站点部署到多个位置，站点间具有相同内容的页面将共享相同的评论数据。
目前你可以选择 Giscus、Waline、Artalk 和 Twikoo。
\n推荐的评论服务
\n\"Artalk\" | \"Giscus\" | \"Twikoo\" | \"Waline\" | \"None\"\"None\"booleantruechannel 插件选项用于配置 feed 的频道。
stringSiteConfig.title频道的标题
\nstringoptions.hostname 和 context.base 生成)频道地址
\nstringSiteConfig.description频道描述信息
\nstringsiteConfig.locales['/'].locales\"en-US\"频道使用的语言
\nstringauthor.name 生成 Copyright by $author频道版权信息
\nstring (需是合法的 Date ISOString)频道内容的发布时间
\nstring (需是合法的 Date ISOString)频道内容的上次更新时间
\nnumber内容有效时间，即获取后保持缓存而不进行新获取的时间
\nstring这是一个会在频道中使用的图片，建议设置正方形图片、尺寸最好不小于 512×512。
\nstring一个代表频道的图标，建议设置正方形图片、尺寸最好不小于 128×128，背景色透明。
\nFeedAuthor频道的作者。
\ninterface FeedAuthor {\n /** 作者姓名 */\n name: string\n /** 作者电子邮箱 */\n email?: string\n /** 作者网站 */\n url?: string\n /**\n * 作者头像地址\n *\n * 正方形，最好不小于 128×128，透明背景\n */\n avatar?: string\n}\nstringWebsub 的链接。Websub 需要服务器后端，与 VuePress 主旨不符，如无特殊需要忽略即可。
\nWebSub
\n有关信息，详见 Websub。
\nstring部署网站的域名。
\nbooleanfalse是否启用 Atom 格式输出。
\nbooleanfalse是否启用 JSON 格式输出。
\nbooleanfalse是否启用 RSS 格式输出。
\nstring一个大的图片，用作 feed 展示。
\nstring一个小的图标，显示在订阅列表中。
\nnumber100设置 feed 的最大项目数量。在所有页面排序好后，插件会截取前 count 个项目。
\n如果你的站点文章很多，你应该考虑设置这个选项以减少 feed 文件大小。
\n(RegExp | string)[] | (tagName：string) => boolean应在 Feed 中保留的自定义元素或组件。
\n默认情况下，所有未知标签均会被移除。
\n类型：(page: Page)=> boolean
默认值：
\n;({ frontmatter, filePathRelative }: Page): boolean =>\n !(\n frontmatter.home ||\n !filePathRelative ||\n frontmatter.article === false ||\n frontmatter.feed === false\n )\n自定义的过滤函数，用于过滤哪些项目在 feed 中显示。
\n类型： (pageA: Page, pageB: Page)=> number
默认值：
\n// dateSorter 来源于 @vuepress/helper\n;(pageA, pageB): number =>\n dateSorter(\n pageA.data.git?.createdTime\n ? new Date(pageA.data.git?.createdTime)\n : pageA.frontmatter.date,\n pageB.data.git?.createdTime\n ? new Date(pageB.data.git?.createdTime)\n : pageB.frontmatter.date,\n )\nFeed 项目的排序器。
\n默认的排序行为是通过 Git 的文件添加日期 (需要 @vuepress/plugin-git)。
提示
\n你应该启用 @vuepress/plugin-git 来获取最新创建的页面作为 feed 项目。否则，feed 项目将按照 VuePress 中页面的默认顺序排序。
channel 选项用于配置 Feed 频道。
可用选项详见 配置 → 频道设置
\nbooleanfalse是否在开发服务器中启用
\n提示
\n由于性能原因，我们不提供热更新。重启开发服务器以同步你的变更。
\nstring\"http://localhost:${port}\"开发服务器使用的主机名
\nstring\"atom.xml\"Atom 格式输出路径，相对于输出路径。
\nstring@vuepress/plugin-feed/templates/atom.xsl 的内容Atom xsl 模板文件没人陪美国
\nstring\"atom.xsl\"Atom xsl 输出路径，相对于输出路径。
\nstring\"feed.json\"JSON 格式输出路径，相对于输出路径。
\nstring\"rss.xml\"RSS 格式输出路径，相对于输出路径。
\nstring@vuepress/plugin-feed/templates/rss.xsl 的内容RSS xsl 模板文件内容。
\nstring\"rss.xsl\"RSS xsl 输出路径，相对于输出路径。
\nFeed 生成控制器，详见 Feed 生成器。
\n此插件内置了生成器，只有当你想完全控制 feed 生成时才需要设置此选项。
\nRecord<string, BaseFeedOptions>你可以将它用于每个语言环境的特定选项。
\n除 hostname 外，上述任何选项均受支持。
你可以通过配置每个页面的 Frontmatter，来对每个 Feed 项目生成进行单独的控制。
\n默认情况下，所有文章均会被添加至 feed 流。如果你想在 feed 中移除特定页面，你可以在 frontmatter 中设置 feed: false。
string由 VuePress 自动生成，默认为页面的 h1 内容
\nstring页面描述
\nDate页面的发布日期
\nboolean该页面是否是文章
\n\n\n如果此项设置为
\nfalse，则该页不会包含在最终的 feed 中。
string页面版权信息
\nstring页面的封面/分享图，需为完整链接或绝对链接。
\nstringFeed 项目的标题
\nstringFeed 项目的描述
\nstringFeed 项目的内容
\nFeedAuthor[] | FeedAuthorFeed 项目的作者
\ninterface FeedAuthor {\n /**\n * 作者名字\n */\n name?: string\n\n /**\n * 作者邮件\n */\n email?: string\n\n /**\n * 作者网站\n *\n * @description json format only\n */\n url?: string\n\n /**\n * 作者头像\n *\n * @description json format only\n */\n avatar?: string\n}\nFeedContributor[] | FeedContributorFeed 项目的贡献者
\ninterface FeedContributor {\n /**\n * 作者名字\n */\n name?: string\n\n /**\n * 作者邮件\n */\n email?: string\n\n /**\n * 作者网站\n *\n * @description json format only\n */\n url?: string\n\n /**\n * 作者头像\n *\n * @description json format only\n */\n avatar?: string\n}\nstringFeed 项目的标识符，用于标识 Feed 项目。
\n你应该确保每个 Feed 项目有全局唯一的 guid。
\n你可以通过控制插件选项中的 getter 来完全控制 Feed 项目的生成。
(page: Page) => string项目标题获取器
\n(page: Page) => string项目链接获取器
\n(page: Page) => string | undefined项目描述获取器
\n提示
\n因为 Atom 在摘要中支持 HTML，所以如果可能的话，你可以在这里返回 HTML 内容，但内容必须以标记 html: 开头。
(page: Page) => string项目内容获取器
\n(page: Page) => FeedAuthor[]项目作者获取器。
\n获取器应在作者信息缺失时返回空数组。
\ninterface FeedAuthor {\n /**\n * 作者名字\n */\n name?: string\n\n /**\n * 作者邮件\n */\n email?: string\n\n /**\n * 作者网站\n *\n * @description json format only\n */\n url?: string\n\n /**\n * 作者头像\n *\n * @description json format only\n */\n avatar?: string\n}\n(page: Page) => FeedCategory[] | undefined项目分类获取器。
\ninterface FeedCategory {\n /**\n * 分类名称\n */\n name: string\n\n /**\n * 标识分类法的字符串\n *\n * @description rss format only\n */\n domain?: string\n\n /**\n * URI 标识的分类 scheme\n *\n * @description atom format only\n */\n scheme?: string\n}\n(page: Page) => FeedEnclosure | undefined项目附件获取器。
\ninterface FeedEnclosure {\n /**\n * Enclosure 地址\n */\n url: string\n\n /**\n * 类型\n *\n * @description 应为一个标准的 MIME 类型，rss format only\n */\n type: string\n\n /**\n * 按照字节数计算的大小\n *\n * @description rss format only\n */\n length?: number\n}\n(page: Page) => Date | undefined项目发布日期获取器
\n(page: Page) => Date项目最后更新日期获取器
\n(page: Page) => string项目图片获取器
\n确保返回一个完整的 URL。
\n(page: Page) => FeedContributor[]项目贡献者获取器
\n获取器应在贡献者信息缺失时返回空数组。
\ninterface FeedContributor {\n /**\n * 作者名字\n */\n name?: string\n\n /**\n * 作者邮件\n */\n email?: string\n\n /**\n * 作者网站\n *\n * @description json format only\n */\n url?: string\n\n /**\n * 作者头像\n *\n * @description json format only\n */\n avatar?: string\n}\n(page: Page) => string | undefined项目版权获取器
\n", + "date_modified": "2024-02-01T04:46:03.000Z", + "authors": [], + "tags": [] + }, + { + "title": "指南", + "url": "https://ecosystem.vuejs.press/ecosystem/zh/plugins/feed/guide.html", + "id": "https://ecosystem.vuejs.press/ecosystem/zh/plugins/feed/guide.html", + "summary": "指南 使用 插件可为你生成以下三种格式的 feed 文件: Atom 1.0 JSON 1.1 RSS 2.0 请按照需要生成的格式，在插件选项中设置 atom, json 或 rss 为 true。 为了正确生成 Feed 链接，你需要在插件选项中设置 hostname。 可读的预览 当你在浏览器中打开 Feed 文件时，我们会通过 xsl 模板将 ...", + "content_html": "\n插件可为你生成以下三种格式的 feed 文件:
\n请按照需要生成的格式，在插件选项中设置 atom, json 或 rss 为 true。
为了正确生成 Feed 链接，你需要在插件选项中设置 hostname。
当你在浏览器中打开 Feed 文件时，我们会通过 xsl 模板将 atom 和 rss feed xml 魔法般地转换为可读的 html。你可以查看本站的 atom 和 rss feed 作为案例！
\n如果你想在开发服务器中预览 Feed，你需要在插件选项中设置 devServer: true。如果你没有使用默认的 http://localhost:{port}，你还需要设置 devHostname。
你可以通过设置 channel 选项来自自定义 Feed 频道的各项信息。
我们推荐进行如下设置:
\nchannel.pubDate 中channel.ttl 中设置内容的更新周期(单位: 分钟)channel.copyright 设置版权信息channel.author 设置频道作者。详细的选项及其默认值详见 配置 → 频道设置
\n默认情况下，所有文章均会被添加至 feed 流。
\n你可以在 frontmatter 中配置 feed 和其他选项控制每个页面的 Feed 项目内容，详见 Frontmatter 选项 了解它们如何被转换。
你可以通过配置插件选项中的 getter 完全控制 Feed 项目的生成逻辑。 详细的选项及其默认值详见 配置 → Feed 获取器
插件会针对每个语言生成单独的 Feed。
\n你可以通过插件选项中的 locales 分别对不同语言提供不同的默认设置。
类型：boolean
默认值：false
详情：
\n是否在 Service Worker 首次成功注册时显示 PWA 安装按钮
\n类型：ManifestOption
详情：
\n填充一个将被解析为 manifest.webmanifest 的对象。
\n提示
\n如果未设置某些选项，它们会回退到插件预设值。
\nsiteConfig.title || siteConfig.locales['/'].title || \"Site\"siteConfig.title || siteConfig.locales['/'].title || \"Site\"siteConfig.description || siteConfig.locales['/'].description || \"A site built with vuepress\"siteConfig.locales['/'].lang || \"en-US\"context.basecontext.base\"standalone\"\"#46bd87\"\"#ffffff\"\"portrait-primary\"false参考：
\n\n类型：string
详情：
\nfavicon.ico 地址，填入绝对路径。
注意
\n我们建议你为你的站点生成 favicon。
\nstring\"#46bd87\"booleanfalsebooleanfalse类型：number
默认值：2048
详情：
\n允许缓存的最大大小 (以 KB 为单位)
\n注意
\n此选项具有最高优先级，任何超过此值的文件都会被排除。
\n所以你如果生成了很大的 HTML 或 JS 文件，请考虑调高此值，否则你的 PWA 可能无法在离线模式下正常运行。
\n类型：number
默认值：1024
详情：
\n图片允许缓存的最大大小 (以 KB 为单位)
\n该选项不能大于 maxSize 选项
\n类型：\"disabled\" | \"available\" | \"hint\" | \"force\"
默认值：\"available\"
详情：
\n发现新内容时的控制逻辑。
\n\"disabled\": 即使有新的 service worker 也不做任何事情，新的 service work 开始等待后，会在用户下次访问时接管页面，让用户获得新内容。
\"available\": 仅当新的 service worker 可用时才显示更新弹出窗口
\"hint\": 显示更新内容可用提示，并允许用户立即刷新。当新的 SW 成功注册后，将转为更新内容就绪弹窗。
当你希望用户立即查看新文档时，这很有帮助。
\n提示
\n如果用户在新 SW 就绪前选择刷新，当前的 Service Worker 将被注销，并且请求将开始向 Web 发出。新的 service worker 将开始安装并在安装后接管页面。
\n\"force\": 立即注销当前 Service Worker 然后刷新以获取新内容
警告
\n虽然这可以确保用户访问的是最新内容，但这可能会影响访问体验。
\n提示
\n文档的更新方式由以前的版本控制，因此当前选项仅影响此版本的下一次更新。
\n更高支持苹果的特殊设置，忽略它们是安全的。
\nstring\"black\" | \"white\"\"black\"string针对微软磁贴的特殊设置，忽略它们是安全的。
\nstringstringthemeColorstring\"PwaFoundPopup\"string\"PwaReadyPopup\"booleanfalse详情：
\n传递给 workbox-build 的选项，具体详情，请见 Workbox 文档
类型：PwaPluginLocaleConfig
interface PwaPluginLocaleData {\n /**\n * 安装按钮文字\n */\n install: string\n\n /**\n * iOS 安装文字\n */\n iOSInstall: string\n\n /**\n * 取消按钮文字\n */\n cancel: string\n\n /**\n * 关闭按钮文字\n */\n close: string\n\n /**\n * 上一张图片文字\n */\n prevImage: string\n\n /**\n * 下一张图片文字\n */\n nextImage: string\n\n /**\n * 安装解释\n */\n explain: string\n\n /**\n * 描述标签文字\n */\n desc: string\n\n /**\n * 特性标签文字\n */\n feature: string\n\n /**\n * 更新内容提示文字\n */\n hint: string\n\n /**\n * 更新内容可用文字\n */\n update: string\n}\n\ninterface PwaPluginLocaleConfig {\n [localePath: string]: PwaPluginLocaleData\n}\n详情：
\nPWA 插件的国际化配置。
\n详情：
\n返回此插件的事件派发器。
\n你可以添加监听器函数到 register-service-worker 提供的事件。
\n示例：
\nimport { usePwaEvent } from '@vuepress/plugin-pwa/client'\n\nexport default {\n setup() {\n const event = usePwaEvent()\n event.on('ready', (registration) => {\n console.log('Service worker is active.')\n })\n },\n}\n详情：
\n当发现新内容时强制刷新页面。
\n示例：
\nimport { forceUpdate } from '@vuepress/plugin-pwa/client'\nimport { onMounted } from 'vue'\n\nexport default {\n setup() {\n onMounted(() => {\n forceUpdate()\n })\n },\n}\n详情：
\n手动注册 Service Worker。
\n参数：
\n| 参数 | 类型 | 描述 |\n|
\n", + "date_modified": "2024-02-20T02:57:55.000Z", + "authors": [], + "tags": [] + }, + { + "title": "指南", + "url": "https://ecosystem.vuejs.press/ecosystem/zh/plugins/pwa/guide.html", + "id": "https://ecosystem.vuejs.press/ecosystem/zh/plugins/pwa/guide.html", + "summary": "指南 介绍 将你的 VuePress 站点变成渐进式网络应用程序 (PWA)[1]。 此插件使用 workbox-build 生成 Service Worker 文件，并使用 register-service-worker 注册 Service Worker。 注意 如果你启用过该插件，并想要禁用它，你可能需要 来移除现有的 Service Worke...", + "content_html": "\n将你的 VuePress 站点变成渐进式网络应用程序 (PWA)[1]。
\n此插件使用 workbox-build 生成 Service Worker 文件，并使用 register-service-worker 注册 Service Worker。
\n注意
\n如果你启用过该插件，并想要禁用它，你可能需要 `@vuepress/plugin-remove-pwa 来移除现有的 Service Worker 。
\nA PWA uses a Service Worker [2] (SW for short) to cache and proxy site content.
\n一个 PWA 使用 Service Worker [2:1] (简称 SW) 来获取并托管网站内容。
\n为了使你的网站符合 PWA 的要求，一个网络 App 清单[3]文件是必要的，并且你的 PWA 应满足可安装性[4]要求。
\n你可以通过设置 manifest 选项来自定义 manifest 文件，或者在 public 文件夹中提供 manifest.webmanifest 或 manifest.json。前者优先级更高。
插件会自动为你生成 manifest.webmanifest，并在每个页面的 <head> 中添加清单链接声明，但是 你至少应该通过 manifest.icons 或 PWA 插件中的其他选项设置一个有效的图标。
注意
\n可安装性[4:1]规范要求 manifest 中至少声明一个有效的图标。
\n所以如果你不配置 manifest.icons，访问者只能享受到 Service Worker 缓存带来的离线可访问性，而并不能作为 PWA 进行安装。
此外，该插件默认不处理清单中的任何内容，而是按原样输出。 这意味着，如果你计划部署到子目录，则应自行将 URL 前缀附加到自己的清单 Urls 中。如果你需要的所有东西都在 base 文件夹下，你可以在插件选项中设置 appendBase: true 让插件将 base 自动附加到任何地址。
为了更好的控制 Service Worker 可以预缓存的内容，插件提供了相关的缓存控制选项。
\n默认情况下插件会预缓存所有的 JS 和 CSS 文件，但仅缓存主页和 404 页面的 HTML。插件同时还会缓存字体文件 (woff, woff2, eot, ttf, otf) 和 SVG 图标。
\n如果你的站点只有少量重要图片，并希望它们在离线模式下显示，你可以通过设置 cacheImage 选项为 true 来缓存站点图片。
我们通过文件后缀名识别图片，任何以 .png, .jpg, .jpeg, .gif, .bmp, .webp 结尾的文件都会视为图片。
当你网站体积不大，并且希望文档完全离线可用时，你可以通过设置 cacheHTML 为 true 来缓存所有 HTML 页面。
为什么默认不缓存非主页和 404 页面
\n虽然说 VuePress 为所有的页面通过 SSG[5] 生成了 HTML 文件，但是这些文件主要用于 SEO[6]，并能够让你在后端不做 SPA[7] 配置的情况下能够直接访问任何链接。
\nVuePress 本质上是一个 SPA。这意味着你只需要缓存主页并从主页进入即可正常访问所有页面。所以默认不缓存其他 HTML 能够有效减小缓存大小 (可以缩减大约 40% 的体积)，加快 SW 更新速度。
\n但是这样做也有缺点，如果用户直接从非主页进入网站，首个页面的 HTML 文件仍需要从互联网加载。同时离线环境下，用户只能通过主页进入再自行导航到对应页面，直接访问某个链接会出现无法访问的提示。
\n为了防止在预缓存列表中包含大文件，任何 > 2 MB 的文件或 > 1 MB 的图片都将被忽略。 你可以通过 maxSize 和 maxImageSize 来自定义大小限制 (单位为 KB)。
我们提供 update 选项控制用户如何接收更新。
update 选项的默认值是 \"available\"，这意味着当网站内容更新后，新的 SW 会在后台静默安装，并在安装结束后弹窗提示用户新内容就绪。用户可以自主选择是否立即刷新查看新内容。这意味在新 SW 就绪前用户会访问旧版本网站。
如果你的文档仍在建设期，希望尽早提示用户他可能在阅读已过时的内容，你可以将其设置为 \"hint\"。这样用户在进入文档后数秒内就可以收到新内容已发布的通知。但这样做的负面效果是如果用户在新 SW 就绪前选择更新，那么他将在新 SW 安装并接管页面前，需要从互联网获取页面的全部资源。
如果你的文档很稳定，或者你在托管博客，不太关心用户立即接收到最新版本，你可以将其设置为 \"disabled\"，这意味着新的 SW 将在后台完全静默安装并在安装后等待，当旧版本 SW 控制的页面全部关闭后，新 SW 将再下次访问接管并提供用户新内容。此设置可以避免用户在访中被弹窗打扰。
如果你希望通过 SW 来加速用户在弱网或无网条件下的访问，但同时希望用户时刻访问新内容，你可以将此选项设置为 \"force\"。这意味着检测到新 SW 后旧 SW 将会被立刻销毁并且页面会被刷新以确保用户浏览最新内容。最大的缺点就是致新 SW 发布后，用户在重新进入网站后的几秒内会遇到预期之外的突然刷新，并且他们将必须通过互联网访问文档并完全重新安装最新的 SW。
当检测到新内容 (检测到新的 SW) 时，更新提示弹窗将会出现；当新内容就绪时，更新就绪弹窗将会出现。
\n如果你对默认的弹窗不满意，你可以自行编写组件更换。从 @vuepress/plugin-pwa/client 中导入 PwaFoundPopup 或 PwaReadyPopup 并使用其 slot 来自定义弹窗内容，然后将组件路径传递给 foundComponent 或 readyComponent 选项。
<script setup lang=\"ts\">\nimport { PwaFoundPopup } from '@vuepress/plugin-pwa/client'\n</script>\n<template>\n <PwaFoundPopup v-slot=\"{ found, refresh }\">\n <div v-if=\"found\">\n 已找到新内容\n <button @click=\"refresh\">刷新</button>\n </div>\n </PwaFoundPopup>\n</template>\n<script setup lang=\"ts\">\nimport { PwaReadyPopup } from '@vuepress/plugin-pwa/client'\n</script>\n<template>\n <PwaReadyPopup v-slot=\"{ isReady, reload }\">\n <div v-if=\"isReady\">\n 新内容已就绪\n <button @click=\"reload\">应用</button>\n </div>\n </PwaReadyPopup>\n</template>\n插件还提供了其他 PWA 相关选项，比如微软磁贴图标与颜色设置，苹果图标等。 如果你是一个高级用户，你也可以设置 generateSwConfig 来配置 workbox-build。查看 插件选项 了解更多细节。
更多内容，请详见:
\nPWA 介绍
\nPWA 全称 Progressive Web app，即渐进式网络应用程序，标准由 W3C 规定。
\n它允许网站通过支持该特性的浏览器将网站作为 App 安装在对应平台上。
\n访问 https://developer.mozilla.org/zh-CN/docs/Web/Progressive_web_apps 查看详情。 ↩︎
\nService Worker 简要介绍
\nService Worker 会在注册过程中获取注册在其中的所有文件并缓存它们。
\n注册成功后，Service Worker 激活，并开始代理并控制你的全部请求。
\n每当你想要通过浏览器发起访问请求后，Service Worker 将会查看其是否存在与自身缓存列表中，若存在则直接返回缓存好的结果，否则调用自身的 fetch 方法进行获取。你可以通过自定义 fetch 方法，来完全控制网页内资源获取请求的结果，比如在离线时提供一个 fallback 的网页。
\n每次用户重新打开网站时，Service Worker 会向自身注册时的地址发出校验命令，如果检测到新版本的 Service Worker，则会更新自身，并开始缓存注册在新 Service Worker 中的资源列表。成功获取内容更新后，Service Worker 将会触发 update 事件。可以通过此事件提示用户，比如将在右下角显示一个弹出窗口，提示用户新内容可用并允许用户触发更新。
清单文件
\n清单文件使用 JSON 格式，负责声明 PWA 各项信息，如名称、描述、图标、快捷动作等。
\n为了使你的站点能够被注册为 PWA，你需要满足 manifest 基本的规范，才能使浏览器认为该网站为一个可安装的 PWA 并允许用户安装它。
\n提示
\nManifest 的标准与规范，请详见 MDN 网络 App 清单 和 W3C Manifest
\n可安装性
\n想要让网站可以注册为 PWA，网站需要自行成功注册有效的 Service Worker，同时拥有合法的 manifest 清单文件并在网站中声明它。
\n清单文件应至少包含 name(或 short_name) icons start_url。
SSG: Static Site Generating，静态站点生成。 ↩︎
\nSEO: Search Engine Optimization，搜索引擎增强，
\n\nSPA: Single Page Application, 单页应用
\n大多只有主页，并使用 history mode 处理路由，而不是真的在页面之间导航。 ↩︎
\n类型：string
必填：是
\n详情：
\n部署域名
\n类型：Author
type AuthorName = string\n\ninterface AuthorInfo {\n /**\n * 作者姓名\n */\n name: string\n\n /**\n * 作者网站\n */\n url?: string\n\n /**\n * 作者 Email\n */\n email?: string\n}\n\ntype Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]\n详情：
\n默认作者
\n类型：boolean
默认值：true
详情：
\n是否自动生成描述
\n类型：string | ((page: Page) => string | null)
详情：
\n首选链接
\n类型：string
详情：
\n当找不到图片时的回退图片链接
\n类型：string
详情：
\n内容的年龄分级，格式为 [int]+，如 \"13+\"
类型：string
详情：
\n你的 twitter 用户名
\n类型：(page: Page) => boolean
详情：
\n你可以使用此选项判断一个页面是否是文章。
\n类型：
\nfunction ogp(\n /** 插件推断的 OGP 信息 */\n ogp: SeoContent,\n /** 页面对象 */\n page: Page,\n /** VuePress App */\n app: App,\n): SeoContent\n详情：
\n自定义 OGP 生成器
\n你可以使用此选项来注入新的或覆盖掉默认生成的 OGP 标签。
\n类型：
\nfunction jsonLd(\n /** 由插件推断出的 JSON-LD 对象 */\n jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,\n /** 页面对象 */\n page: Page,\n /** VuePress App */\n app: App,\n): ArticleSchema | BlogPostingSchema | WebPageSchema\n详情：
\n自定义 JSON-LD 生成器
\n你可以使用此选项来注入新的或覆盖掉默认生成的 JSON-LD 标签。
\n类型：
\nfunction customHead(\n /** head 标签配置 */\n head: HeadConfig[],\n /** 页面对象 */\n page: Page,\n /** VuePress App */\n app: App,\n): void\n详情：
\n你可以使用此选项来直接注入任意格式的标签到 <head>。
本插件会通过向网站 <head> 注入标签，让你的网站完全支持 开放内容协议 OGP 和 JSON-LD 1.1，以全面增强站点的搜索引擎优化性。
插件开箱即用，在不做任何配置的情况下，会尽可能通过页面内容，提取对应的信息补全 OGP 与 JSON-LD 所需的必要标签。
\n默认情况下，插件会读取站点配置、主题配置与页面的 frontmatter 来尽可能自动生成。诸如站点名称，页面标题，页面类型，写作日期，最后更新日期，文章标签均会自动生成。
\n| 属性名称 | 值 |\n| :
\n", + "date_modified": "2024-03-10T14:51:27.000Z", + "authors": [], + "tags": [] + }, + { + "title": "sitemap", + "url": "https://ecosystem.vuejs.press/ecosystem/zh/plugins/sitemap/", + "id": "https://ecosystem.vuejs.press/ecosystem/zh/plugins/sitemap/", + "summary": "sitemap", + "content_html": "\n", + "date_modified": "2024-02-01T04:46:03.000Z", + "authors": [], + "tags": [] + }, + { + "title": "配置", + "url": "https://ecosystem.vuejs.press/ecosystem/zh/plugins/sitemap/config.html", + "id": "https://ecosystem.vuejs.press/ecosystem/zh/plugins/sitemap/config.html", + "summary": "配置 hostname 类型：string 必填：是 详情： 当前网站部署到的域名，插件需要此选项才能工作。 extraUrls 类型：string[] 详情： 需要额外包含的网址。 如果你有一些不包含在 VuePress 路由中的链接 (如: 存放在 public 文件夹下的页面或其他插件或工具直接生成的页面)，你可能需要设置此项。 示例：['/ab...", + "content_html": "\n类型：string
必填：是
\n详情：
\n当前网站部署到的域名，插件需要此选项才能工作。
\n类型：string[]
详情：
\n需要额外包含的网址。
\n如果你有一些不包含在 VuePress 路由中的链接 (如: 存放在 public 文件夹下的页面或其他插件或工具直接生成的页面)，你可能需要设置此项。
\n示例：['/about.html', '/api/']
类型：string[]
默认值：['/404.html']
详情：
\n不需要收录的页面路径，请以绝对路径开头。
\n默认情况下 VuePress 自动生成的所有路径 (除 404 页) 都会被添加进 Sitemap。
\n类型：boolean
默认值：false
详情：
\n是否在开发服务器中启用
\n提示
\n由于性能原因，我们不提供热更新。重启开发服务器以同步你的变更。
\n类型：string
默认值：\"http://localhost:${port}\"
详情：
\n开发服务器使用的主机名
\n类型：string
默认值：\"sitemap.xml\"
详情：
\n输出的文件名，相对于输出目录。
\n类型：string
默认值：\"sitemap.xsl\"
详情：
\n输出的 xsl 文件名，相对于输出目录。
\n类型：string
默认值：\"@vuepress-plugin/sitemap/templates/sitemap.xsl\"
详情：
\n用作模板的 XSL 文件内容
\n类型：\"always\" | \"hourly\" | \"daily\" | \"weekly\" | \"monthly\" | \"yearly\" | \"never\"
默认值：\"daily\"
详情：
\n页面默认更新频率，会被 Frontmatter 中的 changefreq 选项覆盖。
\n类型：number
默认值：0.5
详情：
\n页面优先级，范围 0 至 1。
类型：(page: Page, app: App) => string
详情：
\n最后修改事件的获得器，需要返回一个 ISO 字符形式的时间，默认会自动通过 Git 插件生成。
\n类型：SitemapFrontmatterOptions | false
详情：
\nfalse 表示将页面排除在 sitemap 之外。
类型：\"always\" | \"hourly\" | \"daily\" | \"weekly\" | \"monthly\" | \"yearly\" | \"never\"
默认值：\"daily\"
详情：
\n页面默认更新频率。它会覆盖插件选项中的 changefreq 选项。
\n类型：number
默认值：0.5
详情：
\n页面优先级，范围 0 至 1。
本插件会为你的网站自动生成 Sitemap。为了使插件正常工作，你需要将部署的域名传递给插件的 hostname 选项。如果你想在开发服务器中预览，请配置 devServer 选项。
插件会自动根据页面的 Git 的时间戳生成页面的最后更新时间，同时会根据站点的多语言配置声明页面的其他语言版本替代地址。
\n默认情况下，所有除 404 页面以外的网站链接均会被添加进 Sitemap。
\n如果你希望在 VuePress 项目页面之外，添加其他页面链接到 Sitemap，请将它们变成数组传入插件的 extraUrls 选项。
如果你需要排除一些页面路径，你可以将它们变成数组传入到插件的 excludePaths 选项。你也可以在对应页面的 frontmatter 中，设置 sitemap 为 false。
你还可以通过插件的 sitemapFilename 选项控制输出的地址，此地址相对于输出目录，默认为 sitemap.xml。
页面默认的更新周期是 daily (每天)，如果你希望修改全部的页面周期，请在插件选项中设置 changefreq 。你也可以在页面的 frontmatter 中设置 sitemap.changefreq，页面具有更高的优先级。
合法的频率有:
\n\"always\"\"hourly\"\"daily\"\"weekly\"\"monthly\"\"yearly\"\"never\"你可以在插件中设置 priority 以提供一个默认值。同时你可以通过 frontmatter 中的 sitemap.priority 来为每个页面设置优先级。可接受的值为 0 到 1 的浮点数。
你可以通过插件的 modifyTimeGetter 来返回一个 ISO 字符串格式的时间，默认会通过 Git 插件生成。
以下是一个基于文件最后修改时间的例子。
\n// 基于文件最后修改时间\n({\n modifyTimeGetter: (page, app) =>\n fs.statSync(app.dir.source(page.filePathRelative)).mtime.toISOString();\n})\n网站地图 (Sitemap) 提供搜索引擎优化 (SEO):
\n网站地图通过使所有页面可被找到来增强搜索引擎优化的效果。
\n大部分搜索引擎只跟踪页面内有限数量的链接，因此当网站非常大的时候，网站地图对于使搜索引擎和访问者可以访问网站中的所有内容就变得必不可少了。
\nSitemaps 是站点管理员向搜索引擎爬虫公布站点可被抓取页面的协议，sitemap 文件内容必须遵循 XML 格式的定义。每个 URL 可以包含更新的周期和时间、URL 在整个站点中的优先级。这样可以让搜索引擎更佳有效的抓取网站内容。
\n同步配置 robots.txt
\n由于 Sitemap 面向搜索引擎，配合此插件使用时，你最好保证你在 .vuepress/public 文件夹下放置了有效的 robots.txt，以允许搜索引擎收录。一个最简单的 robots.txt 如下 (允许所有搜索引擎访问所有路径)
User-agent: *\n\nAllow: /\n类型： string
详情：
\n部署的域名，例如 https://example.com
类型： { [path: string]: Partial<DefaultThemeLocaleData> }
默认值： {}
详情：
\n多语言支持的各个语言 locales 。
\n所有在 Locale 配置 章节内的配置项都可以在 locales 中使用。
\n该配置项仅能在默认主题内生效，注意不要和 站点配置 中的 locales 混淆。
参考：
\n该章节内的配置项可以作为一般配置使用，也可以使用在 locales 内。
\n类型： 'auto' | 'light' | 'dark'
默认值： 'auto'
详情：
\n默认颜色模式。
\n如果设置为 'auto' ，则会根据 prefers-color-scheme 自动设置初始颜色模式。
参考：
\n\n类型： boolean
默认值： true
详情：
\n是否启用切换颜色模式的功能。
\n如果设置为 true ，将会在导航栏展示一个切换颜色模式的按钮。
参考：
\n\n类型： string
默认值： /
详情：
\n首页的路径。
\n它将被用于：
\n类型： false | (NavbarItem | NavbarGroup | string)[]
默认值： []
详情：
\n导航栏配置。
\n设置为 false 可以禁用导航栏。
为了配置导航栏元素，你可以将其设置为 导航栏数组 ，其中的每个元素是 NavbarItem 对象、 NavbarGroup 对象、或者字符串：
NavbarItem 对象应该有一个 text 字段和一个 link 字段，还有一个可选的 activeMatch 字段。NavbarGroup 对象应该有一个 text 字段和一个 children 字段。 children 字段同样是一个 导航栏数组 。NavbarItem 对象，将页面标题作为 text ，将页面路由路径作为 link 。示例 1：
\nexport default {\n theme: defaultTheme({\n navbar: [\n // NavbarItem\n {\n text: 'Foo',\n link: '/foo/',\n },\n // NavbarGroup\n {\n text: 'Group',\n children: ['/group/foo.md', '/group/bar.md'],\n },\n // 字符串 - 页面文件路径\n '/bar/README.md',\n ],\n }),\n}\nexport default {\n theme: defaultTheme({\n navbar: [\n // 嵌套 Group - 最大深度为 2\n {\n text: 'Group',\n children: [\n {\n text: 'SubGroup',\n children: ['/group/sub/foo.md', '/group/sub/bar.md'],\n },\n ],\n },\n // 控制元素何时被激活\n {\n text: 'Group 2',\n children: [\n {\n text: 'Always active',\n link: '/',\n // 该元素将一直处于激活状态\n activeMatch: '/',\n },\n {\n text: 'Active on /foo/',\n link: '/not-foo/',\n // 该元素在当前路由路径是 /foo/ 开头时激活\n // 支持正则表达式\n activeMatch: '^/foo/',\n },\n ],\n },\n ],\n }),\n}\n类型： null | string
详情：
\nLogo 图片的 URL。
\nLogo 图片将会显示在导航栏的左端。
\n设置为 null 可以禁用 Logo 。
示例：
\nexport default {\n theme: defaultTheme({\n // Public 文件路径\n logo: '/images/hero.png',\n // URL\n logo: 'https://vuejs.org/images/logo.png',\n }),\n}\n类型： null | string
详情：
\n在夜间模式中使用的 Logo 图片的 URL。
\n如果你想在夜间模式中使用不同的 Logo 图片，就可以使用该配置项。
\n设置为 null 可以在夜间模式下禁用 Logo 。忽略该配置项将会在夜间模式中使用 logo 配置。
参考：
\n\n类型：null | string
详情：
\n指定 Logo 图片的替代文字。
\n当未指定时，将默认与站点标题相同。
\n类型： string
详情：
\n项目仓库的 URL。
\n它将被用作 仓库链接 的链接。仓库链接 将会显示为导航栏的最后一个元素。
\nexport default {\n theme: defaultTheme({\n // 如果你按照 `organization/repository` 的格式设置它\n // 我们会将它作为一个 GitHub 仓库\n repo: 'vuejs/vuepress',\n // 你也可以直接将它设置为一个 URL\n repo: 'https://gitlab.com/foo/bar',\n }),\n}\n类型： false | 'auto' | SidebarConfigArray | SidebarConfigObject
默认值： 'auto'
详情：
\n侧边栏配置。
\n你可以通过页面的 sidebar frontmatter 来覆盖这个全局配置。
\n设置为 false 可以禁用侧边栏。
如果你设置为 'auto'，侧边栏会根据页面标题自动生成。
为了手动配置侧边栏元素，你可以将其设置为 侧边栏数组 ，其中的每个元素是一个 SidebarItem 对象或者一个字符串：
SidebarItem 对象应该有一个 text 字段，有一个可选的 link 字段、一个可选的 children 字段和一个可选的 collapsible 字段。 children 字段同样是一个 侧边栏数组 。 collapsible 字段来控制它是否可折叠。SidebarItem 对象，将页面标题作为 text ，将页面路由路径作为 link ，并根据页面小标题自动生成 children 。如果你想在不同子路径中使用不同的侧边栏，你可以将该配置项设置为 侧边栏对象 ：
\n\"heading\" 以自动为相应路径生成基于标题的侧边栏。示例 1：
\nexport default {\n theme: defaultTheme({\n // 侧边栏数组\n // 所有页面会使用相同的侧边栏\n sidebar: [\n // SidebarItem\n {\n text: 'Foo',\n link: '/foo/',\n children: [\n // SidebarItem\n {\n text: 'github',\n link: 'https://github.com',\n children: [],\n },\n // 字符串 - 页面文件路径\n '/foo/bar.md',\n ],\n },\n // 字符串 - 页面文件路径\n '/bar/README.md',\n ],\n }),\n}\nexport default {\n theme: defaultTheme({\n // 侧边栏对象\n // 不同子路径下的页面会使用不同的侧边栏\n sidebar: {\n '/guide/': [\n {\n text: 'Guide',\n children: ['/guide/introduction.md', '/guide/getting-started.md'],\n },\n ],\n '/reference/': 'heading',\n },\n }),\n}\nexport default {\n theme: defaultTheme({\n // 可折叠的侧边栏\n sidebar: {\n '/reference/': [\n {\n text: 'VuePress Reference',\n collapsible: true,\n children: ['/reference/cli.md', '/reference/config.md'],\n },\n {\n text: 'Bundlers Reference',\n collapsible: true,\n children: [\n '/reference/bundler/vite.md',\n '/reference/bundler/webpack.md',\n ],\n },\n ],\n },\n }),\n}\n类型： number
默认值： 2
详情：
\n设置根据页面标题自动生成的侧边栏的最大深度。
\n0 来禁用所有级别的页面标题。1 来包含 <h2> 标题。2 来包含 <h2> 和 <h3> 标题。最大值取决于你通过 markdown.headers.level 提取了哪些级别的标题。
\n由于 markdown.headers.level 的默认值是 [2, 3] ，因此 sidebarDepth 的默认最大值是 2 。
你可以通过页面的 sidebarDepth frontmatter 来覆盖这个全局配置。
\n类型： boolean
默认值： true
详情：
\n是否启用 编辑此页 链接。
\n你可以通过页面的 editLink frontmatter 来覆盖这个全局配置。
\n类型： string
详情：
\n编辑此页 链接的 Pattern 。
\n它将会用于生成 编辑此页 的链接。
\n如果你不设置该选项，则会根据 docsRepo 配置项来推断 Pattern 。但是如果你的文档仓库没有托管在常用的平台上，比如 GitHub 、 GitLab 、 Bitbucket 、 Gitee 等，那么你必须设置该选项才能使 编辑此页 链接正常工作。
\n用法：
\n| Pattern | 描述 |\n|
\nVuePress 默认主题有着大量的用户，因此我们对它进行了一些便于继承的设计，以便用户轻松进行定制化。
\n默认主题的 Layout 布局提供了一些插槽：
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottom在它们的帮助下，你可以很容易地添加或替换内容。下面通过一个示例来介绍一下如何使用布局插槽来继承默认主题。
\n首先，创建一个客户端配置文件 .vuepress/client.ts ：
import { defineClientConfig } from 'vuepress/client'\nimport Layout from './layouts/Layout.vue'\n\nexport default defineClientConfig({\n layouts: {\n Layout,\n },\n})\n接下来，创建 .vuepress/layouts/Layout.vue ，并使用由默认主题的 Layout 布局提供的插槽：
<script setup>\nimport ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'\n</script>\n\n<template>\n <ParentLayout>\n <template #page-bottom>\n <div class=\"my-footer\">This is my custom page footer</div>\n </template>\n </ParentLayout>\n</template>\n\n<style lang=\"css\">\n.my-footer {\n text-align: center;\n}\n</style>\n此时默认的 Layout 布局已经被你的本地布局覆盖，将会在除了首页外的所有页面添加一个自定义的页脚：
布局插槽十分实用，但有时候你可能会觉得它不够灵活。默认主题同样提供了替换单个组件的能力。
\n默认主题将所有 非全局的组件 都注册了一个带 @theme 前缀的 alias 。例如，HomeFooter.vue 的别名是 @theme/HomeFooter.vue 。
接下来，如果你想要替换 HomeFooter.vue 组件，只需要在配置文件 .vuepress/config.ts 中覆盖这个别名即可：
import { defaultTheme } from '@vuepress/theme-default'\nimport { getDirname, path } from 'vuepress/utils'\nimport { defineUserConfig } from 'vuepress'\n\nconst __dirname = getDirname(import.meta.url)\n\nexport default defineUserConfig({\n theme: defaultTheme(),\n alias: {\n '@theme/HomeFooter.vue': path.resolve(\n __dirname,\n './components/MyHomeFooter.vue',\n ),\n },\n})\n除了在 .vuepress/config.ts 和 .vuepress/client.ts 中直接扩展默认主题以外，你可以通过继承默认主题来开发一个你自己的主题：
import { defaultTheme, type DefaultThemeOptions } from '@vuepress/theme-default'\nimport type { Theme } from 'vuepress/core'\nimport { getDirname, path } from 'vuepress/utils'\n\nconst __dirname = getDirname(import.meta.url)\n\nexport const childTheme = (options: DefaultThemeOptions): Theme => {\n return {\n name: 'vuepress-theme-child',\n extends: defaultTheme(options),\n\n // 在子主题的客户端配置文件中覆盖布局\n // 注意，你在发布到 NPM 之前会将 TS 构建为 JS ，因此这里需要设置为 JS 文件的路径\n clientConfigFile: path.resolve(__dirname, './client.js'),\n\n // 覆盖组件别名\n alias: {\n '@theme/HomeFooter.vue': path.resolve(\n __dirname,\n './components/MyHomeFooter.vue',\n ),\n },\n }\n}\n这些选项用于配置与语言相关的文本。
\n如果你的站点是以英语以外的其他语言提供服务的，你应该为每个语言设置这些选项来提供翻译。
\n类型： string
详情：
\n项目仓库的标签。
\n它将被用作 仓库链接 的文字。仓库链接 将会显示为导航栏的最后一个元素。
\n如果你不明确指定该配置项，它将会根据 repo 配置项自动推断。
\n类型： string
详情：
\n选择语言菜单 的文字。
\n如果你在站点配置中设置了多个 locales ，那么 选择语言菜单 就会显示在导航栏中仓库按钮的旁边。
\n类型： string
详情：
\n选择语言菜单 的 aria-label 属性。
它主要是为了站点的可访问性 (a11y) 。
\n类型： string
详情：
\nLocale 的语言名称。
\n该配置项 仅能在主题配置的 locales 的内部生效 。它将被用作 locale 的语言名称，展示在 选择语言菜单 内。
\n示例：
\nexport default {\n locales: {\n '/': {\n lang: 'en-US',\n },\n '/zh/': {\n lang: 'zh-CN',\n },\n },\n theme: defaultTheme({\n locales: {\n '/': {\n selectLanguageName: 'English',\n },\n '/zh/': {\n selectLanguageName: '简体中文',\n },\n },\n }),\n}\n类型：null | string
详情：
\n导航栏中主导航 aria-label 属性的值。
类型：null | string
详情：
\n下一页/上一页导航 aria-label 属性的值
类型： string
默认值： 'Edit this page'
详情：
\n编辑此页 链接的文字。
\n类型： string
默认值： 'Last Updated'
详情：
\n最近更新时间戳 标签的文字。
\n类型： string
默认值： 'Contributors'
详情：
\n贡献者列表 标签的文字。
\n类型： string
默认值： 'TIP'
详情：
\nTip 自定义容器 的默认标题。
\n类型： string
默认值： 'WARNING'
详情：
\nWarning 自定义容器 的默认标题。
\n类型： string
默认值： 'DANGER'
详情：
\nDanger 自定义容器 的默认标题。
\n类型： string[]
默认值： ['Not Found']
详情：
\n404 页面的提示信息。
\n当用户进入 404 页面时，会从数组中随机选取一条信息进行展示。
\n类型： string
默认值： 'Back to home'
详情：
\n404 页面中 返回首页 链接的文字。
\n类型： string
默认值： 'open in new window'
详情：
\nExternalLinkIcon. 链接内的 sr-only 文字。
它主要是为了站点的可访问性 (a11y) 。
\n参考：
\n\n类型： string
默认值： 'toggle color mode'
详情：
\n切换颜色模式按钮的标题文字。
\n它主要是为了站点的可访问性 (a11y) 。
\n参考：
\n\n类型： string
默认值： 'toggle sidebar'
详情：
\n切换侧边栏按钮的标题文字。
\n它主要是为了站点的可访问性 (a11y) 。
\n类型： string
默认值： 'Prev'
详情：
\n上一页按钮的文字。
\n类型： string
默认值： 'Next'
详情：
\n下一页按钮的文字。
\n你可以通过 themePlugins 设置默认主题使用的插件。
默认主题使用了一些插件，如果你确实不需要该插件，你可以选择禁用它。在禁用插件之前，请确保你已了解它的用途。
\nimport { defaultTheme } from '@vuepress/theme-default'\n\nexport default {\n theme: defaultTheme({\n themePlugins: {\n // 在这里自定义主题插件\n },\n }),\n}\n类型： boolean
默认值： true
详情：
\n\n类型： BackToTopPluginOptions | boolean
默认值： true
详情：
\n是否启用 @vuepress/plugin-back-to-top 。
\n支持对象格式以作为插件选项。
\n类型： Record<ContainerType, boolean>
详情：
\n是否启用由 @vuepress/plugin-container 支持的自定义容器。
\nContainerType 类型为：
tipwarningdangerdetailscodeGroupcodeGroupItem参考：
\n\n类型： CopyCodePluginOptions | boolean
默认值： true
详情：
\n是否启用 @vuepress/plugin-copy-code 。
\n支持对象格式以作为插件选项。
\n类型： boolean
默认值： true
详情：
\n\n类型： boolean
默认值： true
详情：
\n是否启用 @vuepress/plugin-git 。
\n类型： boolean
默认值： true
详情：
\n是否启用 @vuepress/plugin-links-check 。
\n类型： boolean
默认值： true
详情：
\n是否启用 @vuepress/plugin-medium-zoom 。
\n类型： boolean
默认值： true
详情：
\n是否启用 @vuepress/plugin-nprogress 。
\n类型： boolean
默认值： true
详情：
\n是否启用 @vuepress/plugin-prismjs 。
\n类型： SeoPluginOptions | boolean
默认值： true
详情：
\n是否启用 @vuepress/plugin-seo 。
\n支持对象格式以作为插件选项。
\n类型： SitemapPluginOptions | boolean
默认值： true
详情：
\n是否启用 @vuepress/plugin-sitemap 。
\n支持对象格式以作为插件选项。
\n检查组件是否已全局注册。
\n提示
\nsetup 之外调用时，你需要将 app 实例作为第二个参数传递。export const hasGlobalComponent: (name: string, app?: App) => boolean\n// 如果你全局注册了 `<my-component>`\nhasGlobalComponent('MyComponent') // true\nhasGlobalComponent('my-component') // true\n\nhasGlobalComponent('MyComponent2') // false\n从语言环境设置中获取当前语言环境配置。
\nexport const useLocaleConfig: <T extends LocaleData>(\n localesConfig: RequiredLocaleConfig<T>,\n) => ComputedRef<T>\nconst localesCOnfig = {\n '/': 'Title',\n '/zh/': '标题',\n}\n\nconst locale = useLocaleConfig(localesConfig)\n\n// under `/page`\nlocale.value // 'Title'\n\n// under `/zh/page`\nlocale.value // '标题'\n以下函数在 Node.js 和客户端上均可用。
\n此方法在 MarkdownIt 插件中很有用。有些时候你可能需要在 Markdown 插件中生成组件，并将复杂的数据写入到组件属性中，一个通常做法是使用 JSON.stringify + encodeURIComponent，并在客户端 decodeURIComponent + JSON.parse。但如果内容包含很多特殊字符，转换结果会很长。
所以我们提供 encodeData 和 decodeData 来压缩和编码内容。
export const encodeData: (\n data: string,\n level: DeflateOptions['level'] = 6,\n) => string\n\nexport const decodeData: (compressed: string) => string\nconst content = `\n{\n \"type\": \"bar\",\n \"data\": {\n \"labels\": [\"Red\", \"Blue\", \"Yellow\", \"Green\", \"Purple\", \"Orange\"],\n \"datasets\": [\n {\n \"label\": \"# of Votes\",\n \"data\": [12, 19, 3, 5, 2, 3],\n \"backgroundColor\": [\n \"rgba(255, 99, 132, 0.2)\",\n \"rgba(54, 162, 235, 0.2)\",\n \"rgba(255, 206, 86, 0.2)\",\n \"rgba(75, 192, 192, 0.2)\",\n \"rgba(153, 102, 255, 0.2)\",\n \"rgba(255, 159, 64, 0.2)\"\n ],\n \"borderColor\": [\n \"rgba(255, 99, 132, 1)\",\n \"rgba(54, 162, 235, 1)\",\n \"rgba(255, 206, 86, 1)\",\n \"rgba(75, 192, 192, 1)\",\n \"rgba(153, 102, 255, 1)\",\n \"rgba(255, 159, 64, 1)\"\n ],\n \"borderWidth\": 1\n }\n ]\n },\n \"options\": {\n \"scales\": {\n \"y\": {\n \"beginAtZero\": true\n }\n }\n }\n}\n`\n\nconst prop = encodeData(content) // \"eJyNUsFOwzAMve8rrHABKZqWlg5WxAE4cARxAMHEIV1NmQhNlaaCCe3fcdKtW0sLWGpjxy/v+UV512mlcIyfhTa2hHP4GgHYVYExsEQaxqlMpZWxbwAomaAqY5izO0wZB3apKnTrIyqlP1x2bRBzl9xWplC+eWNkniF7dmw1X4nWsfgaNtwNP2kfgH6Be22x9CPUUQ8yFwEHMeMQcog4UBFuiF0kcvGWGV3l6ZVW2uw0XDCTJfIwiOjYjAhESIcn4+BoT2MLio6pP6V+EBJ6AOSZgsmUwyl9A6ATwoiZn3lYTkTkRkycnuP8TU9ENPqUxuuA9i9BmxTNPy9A/G2/F9I23wtpW++FdIwPKzW2W5Afph+WqX2NQWz313XicT7XhV3qnB5f/ejKhVTYVACrXUqUmC3zC/uERsdgTYUdVr/Qb302+gZxe7S/\"\n\ndecodeData(prop) // will be the original content\n\n// if you use `encodeURIComponent`, it will be much longer\nencodeURIComponent(content) // '%0A%7B%0A%20%20%22type%22%3A%20%22bar%22%2C%0A%20%20%22data%22%3A%20%7B%0A%20%20%20%20%22labels%22%3A%20%5B%22Red%22%2C%20%22Blue%22%2C%20%22Yellow%22%2C%20%22Green%22%2C%20%22Purple%22%2C%20%22Orange%22%5D%2C%0A%20%20%20%20%22datasets%22%3A%20%5B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%22label%22%3A%20%22%23%20of%20Votes%22%2C%0A%20%20%20%20%20%20%20%20%22data%22%3A%20%5B12%2C%2019%2C%203%2C%205%2C%202%2C%203%5D%2C%0A%20%20%20%20%20%20%20%20%22backgroundColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%200.2)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%201)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderWidth%22%3A%201%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%0A%20%20%7D%2C%0A%20%20%22options%22%3A%20%7B%0A%20%20%20%20%22scales%22%3A%20%7B%0A%20%20%20%20%20%20%22y%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22beginAtZero%22%3A%20true%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A'\nisDef(x): 判断 x 是否定义。isBoolean(x): 判断 x 是否为布尔值。isString(x): 判断 x 是否为字符串。isNumber(x): 判断 x 是否为数字。isPlainObject(x): 判断值是否为纯对象。isArray(x): 判断 x 是否为数组isFunction(x): 判断 x 是否为函数。isRegExp(x): 判断 x 是否为正则表达式startsWith(a, b): 判断字符串 a 是否以指定字符串 b 开头endsWith(a, b): 判断字符串 a 是否以指定字符串 b 结尾当 a 不是字符串时返回 false
keys(x): 以数组形式返回对象 x 的键
values(x): 以数组形式返回对象 x 的值
entries(x): 将对象 x 转换为键值对数组。
fromEntries(x): 将键值对数组 x 转换为对象。
deepAssign(x, y, ...): Object.assign 的深度版本。
// or @vuepress/helper/client\nimport { deepAssign } from '@vuepress/helper'\n\nconst defaultOptions = {\n optionA: {\n optionA1: 'defaultOptionA1',\n optionA2: 'defaultOptionA2',\n optionA3: 'defaultOptionA3',\n },\n optionB: true,\n optionC: 'optionC',\n}\n\nconst userOptions = {\n optionA: {\n optionA1: 'optionA1',\n optionA2: 'optionA2',\n },\n optionB: false,\n}\n\ndeepAssign(defaultOptions, userOptions)\n// {\n// optionA: {\n// optionA1: \"optionA1\",\n// optionA2: \"optionA2\",\n// optionA3: \"defaultOptionA3\",\n// },\n// optionB: false,\n// optionC: \"optionC\",\n// }\ngetDate(x): 将输入 x 转换为日期，可以支持 Date，时间戳，日期字符串。日期字符串的支持度以环境的 Date.parse 支持度为准。当不能转换为日期时返回 null
getDate('2021-01-01') // a Date object represents 2021-01-01\ngetDate(1609459200000) // a Date object represents 2021-01-01\ngetDate('2021-01-01T00:00:00.000Z') // a Date object represents 2021-01-01\ngetDate('2021/01/01') // a Date object represents 2021-01-01 (might be null in some browsers)\ngetDate('invalid date') // null\ngetDate(undefined) // null\ngetDate(-32) // null\ndateSorter: 将可转换为日期的值从新到旧排序，不能转换为日期的值会在最后。
const arr = [\n '2020-01-01',\n 1609459200000,\n '2022-01-01T00:00:00.000Z',\n '2023/01/01',\n 'invalid date',\n undefined,\n -32,\n]\n\narr.sort(dateSorter)\n// [\n// '2023/01/01',\n// '2022-01-01T00:00:00.000Z',\n// 1609459200000,\n// '2020-01-01',\n// 'invalid date',\n// undefined,\n// -32,\n// ]\nisLinkHttp(x): x 是否是有效的 HTTP URL。isLinkWithProtocol(x): x 是否是有效的带有协议的 URL。isLinkExternal(x): x 是否是有效的外部 URL。isLinkAbsolute(x): x 是否是有效的绝对 URL。ensureEndingSlash(x): 确保 x 以斜杠结尾。ensureLeadingSlash(x): 确保 x 以斜杠开头。removeEndingSlash(x): 确保 x 不以斜杠结尾。removeLeadingSlash(x): 确保 x 不以斜杠开头。Artalk 是一款简洁的自托管评论系统，你可以在服务器上轻松部署并置入前端页面中。
\n来到你的博客，或是任意位置，放置 Artalk 评论框，让页面具备丰富的社会化功能。
\n\nnpm i -D artalk\n请参见 Artalk 文档。
\n请配置 provider: \"Artalk\" 并将你的服务端地址传入插件选项中的 server。
其他的配置项详见 Artalk 配置。
\n提示
\n插件保留 el 选项在页面自行插入 Artalk。同时插件会自动根据 VuePress 信息为你自动设置 pageTitle, pageKey 和 site 选项。
为了能使 Artalk 应用正确的主题，你需要通过 darkmode 属性向 <CommentService /> 传入一个布尔值，代表当前是否开启夜间模式。
详见 Artalk 配置。
\nel pageTitle, pageKey 和 site 选项为插件的保留选项，将从 VuePress 配置中自动推断，不可设置。
imgUploader 和 avatarURLBuilder 这两个函数选项只能在客户端配置。
你可以直接在插件选项中配置可序列化的选项:
\nimport { defineUserConfig } from 'vuepress'\nimport { commentPlugin } from 'vuepress-plugin-comment2'\n\nexport default defineUserConfig({\n plugins: [\n commentPlugin({\n provider: 'Artalk',\n // 其他选项\n // ...\n }),\n ],\n})\n你可以使用 defineArtalkConfig 函数来配置 Artalk。
import { defineClientConfig } from 'vuepress/client'\nimport { defineArtalkConfig } from 'vuepress-plugin-comment2/client'\n\ndefineArtalkConfig({\n // Artalk 选项\n})\n\nexport default defineClientConfig({\n // ...\n})\nGiscus 是一个基于 GitHub Discussion 的评论系统，启用简便。
\n\n你需要创建一个公开仓库，并开启评论区，以作为评论存放的地点
\n你需要安装 Giscus App，使其有权限访问对应仓库。
\n在完成以上步骤后，请前往 Giscus 页面 获得你的设置。
\n你只需要填写仓库和 Discussion 分类，之后滚动到页面下部的 “启用 giscus” 部分，获取 data-repo, data-repo-id, data-category 和 data-category-id 这四个属性。
请配置 provider: \"Giscus\" 并将 data-repo, data-repo-id, data-category 和 data-category-id 作为插件选项传入 repo, repoId, category categoryId。
其他的配置项详见 Giscus 配置。
\n默认情况下，Giscus 使用 light 或 dark 主题 (基于夜间模式状态)。
::: info 夜间模式
\n为了能使 Giscus 应用正确的主题，你需要为 <CommentService /> 通过 darkmode 属性传入一个布尔值，代表当前是否开启夜间模式。
:::
\n如果你想在日间模式和夜间模式下自定义主题，你可以设置 lightTheme 和 darkTheme 选项，使用内置主题关键字或以 https:// 开头的自定义 css 链接。
stringstringstringstringstring\"pathname\"booleantruebooleantruebooleantrue\"top\" | \"bottom\"\"top\"类型: GiscusTheme
type GiscusTheme =\n | 'light'\n | 'light_high_contrast'\n | 'light_protanopia'\n | 'dark'\n | 'dark_high_contrast'\n | 'dark_protanopia'\n | 'dark_dimmed'\n | 'transparent_dark'\n | 'preferred_color_scheme'\n | `https://${string}`\n默认值: \"light\"
详情：
\nGiscus 在日间模式下使用的主题
\n应为一个内置主题关键词或者一个 CSS 链接。
\n类型: GiscusTheme
type GiscusTheme =\n | 'light'\n | 'light_high_contrast'\n | 'light_protanopia'\n | 'dark'\n | 'dark_high_contrast'\n | 'dark_protanopia'\n | 'dark_dimmed'\n | 'transparent_dark'\n | 'preferred_color_scheme'\n | `https://${string}`\n默认值: \"dark\"
详情：
\nGiscus 在夜间模式下使用的主题
\n应为一个内置主题关键词或者一个 CSS 链接。
\n你可以直接在插件选项中配置可序列化的选项:
\nimport { defineUserConfig } from 'vuepress'\nimport { commentPlugin } from 'vuepress-plugin-comment2'\n\nexport default defineUserConfig({\n plugins: [\n commentPlugin({\n provider: 'Giscus',\n // 其他选项\n // ...\n }),\n ],\n})\n你可以使用 defineGiscusConfig 函数来配置 Giscus。
import { defineClientConfig } from 'vuepress/client'\nimport { defineGiscusConfig } from 'vuepress-plugin-comment2/client'\n\ndefineGiscusConfig({\n // Giscus 选项\n})\n\nexport default defineClientConfig({\n // ...\n})\n一个简洁、安全、免费的静态网站评论系统，基于 腾讯云开发。
\n\nnpm i -D twikoo\n部署共有四种方式。
\n| 部署方式 | 描述 |\n|
\n", + "image": "https://main.qcloudimg.com/raw/67f5a389f1ac6f3b4d04c7256438e44f.svg", + "date_modified": "2024-03-11T08:20:01.000Z", + "authors": [], + "tags": [] + }, + { + "title": "Twikoo 选项", + "url": "https://ecosystem.vuejs.press/ecosystem/zh/plugins/comment/twikoo/config.html", + "id": "https://ecosystem.vuejs.press/ecosystem/zh/plugins/comment/twikoo/config.html", + "summary": "Twikoo 选项 配置 envId 类型: string 必填: 是 详情：腾讯云环境 ID 或 Vercel 地址。 repoId 类型: string 默认值: \"ap-shanghai\" 详情：腾讯云区域。 插件配置 你可以直接在插件选项中配置可序列化的选项: 客户端配置 你可以使用 defineTwikooConfig 函数来配置 Twikoo。", + "content_html": "\nstringstring\"ap-shanghai\"你可以直接在插件选项中配置可序列化的选项:
\nimport { defineUserConfig } from 'vuepress'\nimport { commentPlugin } from 'vuepress-plugin-comment2'\n\nexport default defineUserConfig({\n plugins: [\n commentPlugin({\n provider: 'Twikoo',\n // 其他选项\n // ...\n }),\n ],\n})\n你可以使用 defineTwikooConfig 函数来配置 Twikoo。
import { defineClientConfig } from 'vuepress/client'\nimport { defineTwikooConfig } from 'vuepress-plugin-comment2/client'\n\ndefineTwikooConfig({\n // Twikoo 选项\n})\n\nexport default defineClientConfig({\n // ...\n})\n一个有后端的安全评论系统。
\n\nnpm i -D @waline/client\n点击左上角 创建应用 并起一个你喜欢的名字 (请选择免费的开发版):
\n\n进入应用，选择左下角的 设置 > 应用 Key。你可以看到你的 APP ID,APP Key 和 Master Key。请记录它们，以便后续使用。
国内版需要完成备案接入
\n如果你正在使用 Leancloud 国内版 (leancloud.cn)，我们推荐你切换到国际版 (leancloud.app)。否则，你需要为应用额外绑定已备案的域名，同时购买独立 IP 并完成备案接入:
\n设置 > 域名绑定 > API 访问域名 > 绑定新域名 > 输入域名 > 确定。点击上方按钮，跳转至 Vercel 进行 Server 端部署。
\n::: note
\n如果你未登录的话，Vercel 会让你注册或登录，请使用 GitHub 账户进行快捷登录。
\n:::
\n输入一个你喜欢的 Vercel 项目名称并点击 Create 继续:
![\"创建项目\"](\"/images/comment/vercel-1.png\")
此时 Vercel 会基于 Waline 模板帮助你新建并初始化仓库，仓库名为你之前输入的项目名。
\n
一两分钟后，满屏的烟花会庆祝你部署成功。此时点击 Go to Dashboard 可以跳转到应用的控制台。
点击顶部的 Settings - Environment Variables 进入环境变量配置页，并配置三个环境变量 LEAN_ID, LEAN_KEY 和 LEAN_MASTER_KEY 。它们的值分别对应上一步在 LeanCloud 中获得的 APP ID, APP KEY, Master Key。
::: note
\n如果你使用 LeanCloud 国内版，请额外配置 LEAN_SERVER 环境变量，值为你绑定好的域名。
:::
\n环境变量配置完成之后点击顶部的 Deployments 点击顶部最新的一次部署右侧的 Redeploy 按钮进行重新部署。该步骤是为了让刚才设置的环境变量生效。
此时会跳转到 Overview 界面开始部署，等待片刻后 STATUS 会变成 Ready。此时请点击 Visit ，即可跳转到部署好的网站地址，此地址即为你的服务端地址。
点击顶部的 Settings - Domains 进入域名配置页
输入需要绑定的域名并点击 Add
在域名服务器商处添加新的 CNAME 解析记录
| Type | Name | Value |\n|
\nstring类型: (WalineEmojiInfo | WalineEmojiPresets)[] | false
type WalineEmojiPresets = `http://${string}` | `https://${string}`\n\ninterface WalineEmojiInfo {\n /**\n * 选项卡上的 Emoji 名称\n */\n name: string\n /**\n * 所在文件夹链接\n */\n folder?: string\n /**\n * Emoji 通用路径前缀\n */\n prefix?: string\n /**\n * Emoji 图片的类型，会作为文件扩展名使用\n */\n type?: string\n /**\n * 选项卡显示的 Emoji 图标\n */\n icon: string\n /**\n * Emoji 图片列表\n */\n items: string[]\n}\n默认值: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
参考：
\n详情：表情设置
\n类型: string | boolean
默认值: false
参考：
\n详情：
\n暗黑模式适配。
\n'auto' 会根据设备暗黑模式自适应。类型: WalineCommentSorting
默认值: 'latest'
详情：
\n评论列表排序方式。可选值: 'latest', 'oldest', 'hottest'
类型: string[]
默认值: ['nick', 'mail', 'link']
详情：
\n评论者相关属性。可选值: 'nick', 'mail', 'link'
类型: string[]
默认值: []
详情：
\n设置必填项，默认匿名，可选值:
\n[]['nick']['nick', 'mail']string'enable'登录模式状态，可选值:
\n'enable': 启用登录 (默认)'disable': 禁用登录，用户只能填写信息评论'force': 强制登录，用户必须注册并登录才可发布评论类型: number | [number, number]
默认值: 0
详情：
\n评论字数限制。填入单个数字时为最大字数限制。设置为 0 时无限制。
number10类型: WalineImageUploader | false
详情:
\ntype WalineImageUploader = (image: File) => Promise<string>\n参考:
\n\n详情：
\n自定义图片上传方法。默认行为是将图片 Base 64 编码嵌入，你可以设置为 false 以禁用图片上传功能。
函数应该接收图片对象，返回一个提供图片地址的 Promise。
\n类型: WalineHighlighter | false
type WalineHighlighter = (code: string, lang: string) => string\n参考:
\n\n详情：
\n代码高亮，默认使用一个 < 1kb 的简单高亮器。函数传入代码块的原始字符和代码块的语言。你应该直接返回一个字符串。
\n你可以传入一个自己的代码高亮器，也可以设置为 false 以禁用代码高亮功能。
类型: WalineTexRenderer | false
type WalineTexRenderer = (blockMode: boolean, tex: string) => string\n参考:
\n\n详情：
\n自定义 TeX 渲染，默认行为是提示预览模式不支持 TeX。函数提供两个参数，第一个参数表示渲染模式是否为块级，第二个参数是 TeX 的字符串，并返回一段 HTML 字符串作为渲染结果。
\n你可以自行引入 TeX 渲染器并提供预览渲染，建议使用 Katex 或 MathJax，也可以设置为 false 以禁止渲染 TeX。
类型: WalineSearchOptions | false
interface WalineSearchImageData extends Record<string, unknown> {\n /**\n * 图片链接\n */\n src: string\n\n /**\n * 图片标题\n *\n * @description 用于图片的 alt 属性\n */\n title?: string\n\n /**\n * 图片缩略图\n *\n * @description 为了更好的加载性能，我们会优先在列表中使用此缩略图\n *\n * @default src\n */\n preview?: string\n}\n\ntype WalineSearchResult = WalineSearchImageData[]\n\ninterface WalineSearchOptions {\n /**\n * 搜索操作\n */\n search: (word: string) => Promise<WalineSearchResult>\n\n /**\n * 打开列表时展示的默认结果\n *\n * @default () => search('')\n */\n default?: () => Promise<WalineSearchResult>\n\n /**\n * 获取更多的操作\n *\n * @description 会在列表滚动到底部时触发，如果你的搜索服务支持分页功能，你应该设置此项实现无限滚动\n *\n * @default (word) => search(word)\n */\n more?: (word: string, currentCount: number) => Promise<WalineSearchResult>\n}\n详情：自定义搜索功能，设置 false 可禁用搜索。
类型: string
详情：
\nreCAPTCHA V3 是 Google 提供的验证码服务，配置 reCAPTCHA V3 网站密钥即可开启该功能。
\n服务端需要同步配置 RECAPTCHA_V3_SECRET 环境变量。
类型: boolean | string[]
默认值: false
详情：
\n为文章增加表情互动功能，设置为 true 提供默认表情，也可以通过设置表情地址数组来自定义表情图片，最大支持 8 个表情。
类型: boolean
默认值: true
详情：
\n是否导入 Meta 图标。
\n类型: WalineLocales
interface WalineLocales {\n [localePath: string]: WalineLocale\n}\n参考:
\n详情：
\nWaline 多语言配置
\n你可以直接在插件选项中配置可序列化的选项:
\nimport { defineUserConfig } from 'vuepress'\nimport { commentPlugin } from 'vuepress-plugin-comment2'\n\nexport default defineUserConfig({\n plugins: [\n commentPlugin({\n provider: 'Waline',\n // 其他选项\n // ...\n }),\n ],\n})\n你可以使用 defineWalineConfig 函数来配置 Waline。
import { defineClientConfig } from 'vuepress/client'\nimport { defineWalineConfig } from 'vuepress-plugin-comment2/client'\n\ndefineWalineConfig({\n // Waline 选项\n})\n\nexport default defineClientConfig({\n // ...\n})\n打包器函数用于在主题和插件中追加或修改打包器选项。
\n所有函数都应在 extendsBundlerOptions 生命周期挂钩中调用。
提示
\n我们在示例中省略了它。 实际代码应该是这样的：
\n// 导入你需要的函数\nimport { addCustomElement } from '@vuepress/helper'\n\nexport const yourPlugin = {\n // ...\n extendsBundlerOptions: (bundlerOptions, app) => {\n // 在此添加它们\n addCustomElement(bundlerOptions, app, 'my-custom-element')\n },\n}\n获取当前打包器的名称。
\nexport const getBundlerName: (app: App) => string\n// @vuepress/bundler-vite\ngetBundleName(app) === 'vite' // true\n// @vuepress/bundler-webpack\ngetBundleName(app) === 'webpack' // true\n将自定义元素声明添加到当前的打包器。
\ninterface CustomElementCommonOptions {\n app: App;\n config: unknown;\n}\n/**\n * Add tags as customElement\n *\n * @param bundlerOptions VuePress Bundler config\n * @param app VuePress Node App\n * @param customElements tags recognized as custom element\n */\nexport const addCustomElement = (\n bundlerOptions: unknown,\n app: App,\n customElement: string[] | string | RegExp\n) => void;\nimport { addCustomElement } from '@vuepress/helper'\n\naddCustomElement(bundlerConfig, app, 'my-custom-element')\naddCustomElement(bundlerOptions, app, [\n 'custom-element1',\n 'custom-element2',\n // all tags start with `math-`\n /^math-/,\n])\n为开发服务器中的特定路径提供内容。
\nexport interface DevServerOptions {\n /**\n * Path to be responded\n */\n path: string;\n /**\n * Respond function\n */\n response: (request?: IncomingMessage) => Promise<string | Buffer>;\n\n /**\n * error msg\n */\n errMsg?: string;\n}\n\n/**\n * Handle specific path when running VuePress Dev Server\n *\n * @param bundlerOptions VuePress Bundler config\n * @param app VuePress Node App\n * @param path Path to be responded\n * @param response respond function\n * @param errMsg error msg\n */\nexport const customizeDevServer: (\n bundlerOptions: unknown,\n app: App,\n {\n errMsg:\"The server encountered an error\",\n response: responseHandler,\n path,\n }: CustomServerOptions\n) => void;\nimport { useCustomDevServer } from '@vuepress/helper'\n\n// handle `/api/` path\nuseCustomDevServer(bundlerOptions, app, {\n path: '/api/',\n response: async () => getData(),\n errMsg: 'Unexpected api error',\n})\naddViteOptimizeDepsInclude
\n向 Vite optimizeDeps.include 列表中添加模块
提示
\n如果一个包满足下列条件之一，你应该考虑将它添加至此。
\nimport() 动态导入addViteOptimizeDepsExclude
\n向 Vite optimizeDeps.exclude 列表中添加模块
如果一个包和它的依赖都是纯 ESM 包，你应该考虑将它添加至此。
\naddViteSsrExternal
\n向 Vite ssr.external 列表中添加模块
如果一个包是纯 ESM 包，且未使用别名 (alias) 或定义变量 (define)，你应该考虑将它添加至此。
\naddViteSsrNoExternal
\n向 Vite ssr.noExternal 列表中添加模块
如果一个包内使用了别名 (alias) 或定义变量 (define)，你必须将它添加至此。
\n/**\n * Add modules to Vite `optimizeDeps.include` list\n */\nexport const addViteOptimizeDepsInclude: (\n bundlerOptions: unknown,\n app: App,\n module: string | string[],\n) => void\n\n/**\n * Add modules to Vite `optimizeDeps.exclude` list\n */\nexport const addViteOptimizeDepsExclude: (\n bundlerOptions: unknown,\n app: App,\n module: string | string[],\n) => void\n\n/**\n * Add modules to Vite `ssr.external` list\n */\nexport const addViteSsrExternal: (\n bundlerOptions: unknown,\n app: App,\n module: string | string[],\n) => void\n\n/**\n * Add modules to Vite `ssr.noExternal` list\n */\nexport const addViteSsrNoExternal: (\n bundlerOptions: unknown,\n app: App,\n module: string | string[],\n) => void\nimport {\n addViteOptimizeDepsInclude,\n addViteOptimizeDepsExclude,\n addViteSsrExternal,\n addViteSsrNoExternal,\n} from '@vuepress/helper'\n\naddViteOptimizeDepsInclude(bundlerOptions, app, ['vue', 'vue-router'])\naddViteOptimizeDepsExclude(bundlerOptions, app, 'packageA')\naddViteSsrNoExternal(bundlerOptions, app, ['vue', 'vue-router'])\naddViteSsrExternal(bundlerOptions, app, 'packageA')\naddViteConfig
\nA function for you to add vite config
\nexport const addViteConfig: (\n bundlerOptions: unknown,\n app: App,\n config: Record<string, unknown>,\n) => void\nimport { addViteConfig } from '@vuepress/helper'\n\naddViteConfig(bundlerOptions, app, {\n build: {\n charset: 'utf8',\n },\n})\nmergeViteConfig
\n无需导入 vite 即可合并 vite 配置的功能
\nexport const mergeViteConfig: (\n defaults: Record<string, any>,\n overrides: Record<string, any>,\n) => Record<string, any>\n注意
\n你不应将 vite 作为依赖，因为你的的用户可能选择其他打包器！
\nimport { mergeViteConfig } from \"@vuepress/helper\";\n\nconfig.viteOptions mergeViteConfig(config.viteOptions, {\n build: {\n charset: \"utf8\",\n },\n});\nchainWebpack
\n链式修改 webpack 配置.
\nexport const chainWebpack: (\n { app, config }: WebpackCommonOptions,\n chainWebpack: (\n config: WebpackChainConfig,\n isServer: boolean,\n isBuild: boolean,\n ) => void,\n) => void\nimport { chainWebpack } from '@vuepress/helper'\n\nchainWebpack(bundlerOptions, app, (config, isServer, isBuild) => {\n // do some customize here\n})\nconfigWebpack
\n配置 Webpack
\nexport const configWebpack: (\n bundlerOptions: unknown,\n app: App,\n configureWebpack: (\n config: WebpackConfiguration,\n isServer: boolean,\n isBuild: boolean,\n ) => void,\n) => void\nimport { configWebpack } from '@vuepress/helper'\n\nconfigWebpack(bundlerOptions, app, (config, isServer, isBuild) => {\n // do some customize here\n})\n这些函数为你的页面生成常见信息。
\n获取页面摘要。
\nexport interface PageExcerptOptions {\n /**\n * 摘要分隔符\n *\n * @default \"<!-- more -->\"\n */\n separator?: string\n\n /**\n * 摘要的长度\n *\n * @description 摘要的长度会尽可能的接近这个值\n *\n * @default 300\n */\n length?: number\n\n /**\n * 被认为是自定义元素的标签\n *\n * @description 用于判断一个标签是否是自定义元素，因为在摘要中，所有的未知标签都会被移除。\n */\n isCustomElement?: (tagName: string) => boolean\n\n /**\n * 是否保留页面标题 (第一个 h1)\n *\n * @default false\n */\n keepPageTitle?: boolean\n\n /**\n * 是否保留代码块的标签，诸如行号和高亮行\n *\n * @default false\n */\n keepFenceDom?: boolean\n}\n\nexport const getPageExcerpt: (\n app: App,\n page: Page,\n options?: PageExcerptOptions,\n) => string\n获取页面纯文本。
\nexport interface PageTextOptions {\n /**\n * 是否将文字转换成单行内容\n *\n * @default false\n */\n singleLine?: boolean\n\n /**\n * 文字的长度\n *\n * @description 文字的长度会尽可能的接近这个值\n *\n * @default 300\n */\n length?: number\n\n /**\n * 需要移除的标签\n *\n * @description 默认情况下表格和代码块会被移除\n *\n * @default ['table', 'pre']\n */\n removedTags?: string[]\n}\n\nexport const getPageText: (\n app: App,\n page: Page,\n options?: PageTextOptions,\n) => string\n该插件会监听页面滚动事件。当页面滚动至某个 标题锚点 后，如果存在对应的 标题链接 ，那么该插件会将路由 Hash 更改为该 标题锚点 。
该插件主要用于开发主题，并且已经集成到默认主题中。大部分情况下你不需要直接使用它。
npm i -D @vuepress/plugin-active-header-links@next
+import { activeHeaderLinksPlugin } from '@vuepress/plugin-active-header-links'
+
+export default {
+ plugins: [
+ activeHeaderLinksPlugin({
+ // 配置项
+ }),
+ ],
+}
+类型： string
默认值： 'a.sidebar-item'
详情：
标题链接 的选择器。
如果一个 标题锚点 没有对应的 标题链接 ，那么即使滚动到这个 标题锚点 ，该插件也不会更改路由 Hash 。
类型： string
默认值： '.header-anchor'
详情：
标题锚点 的选择器。
你通常不需要设置该选项，除非你通过 markdown.anchor 修改了 markdown-it-anchor 的 permalinkClass 选项。
参考：
类型： number
默认值： 200
详情：
滚动事件监听器的 Debounce 延迟。
类型： number
默认值： 5
详情：
即便直接点击 标题锚点 的链接， scrollTop 也可能不会完全等于 标题锚点 的 offsetTop ，所以我们添加一个 Offset 偏移量来避免这个误差。
该插件会基于 @vuepress/plugin-git 为 frontmatter 追加写作日期。
npm i -D @vuepress/plugin-append-date@next
+import { appendDatePlugin } from '@vuepress/plugin-append-date'
+
+export default {
+ plugins: [appendDatePlugin()],
+}
+string"date""date" | "time" | "full""date"该插件会给你的站点添加一个 返回顶部 按钮。当页面向下滚动时，该按钮会显示在页面的右下角，点击它就会滚动到页面顶部。
该插件已经集成到默认主题中。
npm i -D @vuepress/plugin-back-to-top@next
+import { backToTopPlugin } from '@vuepress/plugin-back-to-top'
+
+export default {
+ plugins: [backToTopPlugin()],
+}
+数字100布尔值true你可以通过 CSS 变量来自定义 返回顶部 按钮的样式：
:root {
+ --back-to-top-z-index: 5;
+ --back-to-top-icon: url("back-to-top.svg");
+ --back-to-top-bg-color: #fff;
+ --back-to-top-color: #3eaf7c;
+ --back-to-top-color-hover: #71cda3;
+ --back-to-top-shadow: rgb(0 0 0 / 20%);
+}
+将 百度统计 集成到 VuePress 中。
提示
请勿打开百度统计内置的“单页应用数据统计”功能，本插件会正确处理相关逻辑。
npm i -D @vuepress/plugin-baidu-analytics@next
+import { baiduAnalyticsPlugin } from '@vuepress/plugin-baidu-analytics'
+
+export default {
+ plugins: [
+ baiduAnalyticsPlugin({
+ // 配置项
+ }),
+ ],
+}
+插件会在访问和切换页面时自动上报页面浏览事件。
另外，一个全局的 hmt 数组会被挂载到 window 对象上，你可以使用它进行 自定义事件的上报 。
stringhm.js URL 中的查询参数。类型: (page: Page) => Record<string, unknown>
必填: 否
参考:
详情：
获取文章信息的函数。
获取到的信息会被稍后注入至路由元数据，以便你可以在客户端中通过组合式 API 获取。
类型: (page: Page) => boolean
默认值: (page) => Boolean(page.filePathRelative) && !page.frontmatter.home
参考:
详情：
页面过滤器，此函数用于鉴别页面是否作为文章。
默认情况下，所有从 Markdown 源文件中生成的非主页页面，会被作为文章。
类型: BlogCategoryOptions[]
必填: 否
详情：
详情：
博客分类配置，详见 博客分类配置。
类型: BlogTypeOptions[]
必填: 否
参考：
详情：
博客分类配置，详见 博客类型配置。
(name: string) => string(name) => name.replace(/ _/g, '-').replace(/[:?*|\\/<>]/g, "").toLowerCase()booleantruestring<!-- more -->类型: number
默认值: 300
参考：
详情：
自动生成的摘要的长度。
提示
摘要的长度会尽可能的接近这个值。如果设置为 0，意味着不自动生成摘要。
类型: (page: Page) => boolean
默认值: filter 选项
参考：
详情： 页面过滤器，此函数用于鉴别插件是否需要生成摘要。
提示
你可以使用此函数来跳过你不需要生成摘要的页面。例如：如果用户在 frontmatter 中设置了 excerpt 或 description，你可能希望直接使用它们。
类型: (tagName: string) => boolean
默认值: () => false
参考：
详情： 被认为是自定义元素的标签。
用于判断一个标签是否是自定义元素，因为在摘要中，所有的未知标签都会被移除。
类型: string
默认值: "_blog"
详情： 注入文章信息至路由元数据时使用的键名。
提示
设置为空字符串会直接注入路由元数据 (而不是一个键下)。
类型: boolean
默认值: 是否使用 --debug 标记
详情： 是否在开发服务器中启用实时热重载。
致主题开发者
默认情况下它是禁用的，因为它确实会对具有很多分类和类别的站点产生性能影响，并且在编辑 Markdown 时会减慢热重载的速度。
如果用户正在添加或组织类别或标签，你可以告诉他们启用此功能，其余的时间最好禁用它。
此外，你可以尝试检测用户项目中的页面数并决定是否启用它。
博客分类配置应为一个数组，每一项控制一个分类规则。
interface BlogCategoryOptions {
+ /**
+ * 唯一的分类名称
+ */
+ key: string
+
+ /**
+ * 从页面中获取分类的函数
+ */
+ getter: (page: Page) => string[]
+
+ /**
+ * 页面排序器
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * 待注册的页面路径图案
+ *
+ * @description `:key` 将会被替换为原 key 的 slugify 结果
+ *
+ * @default `/:key/`
+ */
+ path?: string | false
+
+ /**
+ * 页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Front Matter 配置
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+
+ /**
+ * 待注册的项目页面路径图案或自定义函数
+ *
+ * @description 当填入字符串的时候, `:key` 和 `:name` 会被自动替换为原始的 key、name 的 slugify 结果。
+ *
+ * @default `/:key/:name/`
+ */
+ itemPath?: string | ((name: string) => string) | false
+
+ /**
+ * 项目页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ itemLayout?: string
+
+ /**
+ * 项目 Front Matter 配置
+ */
+ itemFrontmatter?: (name: string, localePath: string) => Record<string, string>
+}
+博客类型配置应为一个数组，每一项控制一个类型规则。
interface BlogTypeOptions {
+ /**
+ * 唯一的类型名称
+ */
+ key: string
+
+ /**
+ * 一个过滤函数来决定页面是否满足此类型
+ */
+ filter: (page: Page) => boolean
+
+ /**
+ * 页面排序器
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * 待注册的页面路径
+ *
+ * @default '/:key/'
+ */
+ path?: string | false
+
+ /**
+ * 页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Front Matter 配置
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+}
+你可以从 @vuepress/plugin-blog/client 导入下列 API:
博客分类
const useBlogCategory: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogCategoryData<T>>
+参数 key 为需要获取的键名。如果未传入 key，会尝试使用与当前路径匹配的 key。
博客类型
const useBlogType: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogTypeData<T>>
+参数 key 为需要获取的键名。如果未传入 key，会尝试使用与当前路径匹配的 key。
详细的返回值如下:
interface Article<T extends Record<string, unknown> = Record<string, unknown>> {
+ /** 文章路径 */
+ path: string
+ /** 文章信息 */
+ info: T
+}
+
+interface BlogCategoryData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** 分类路径 */
+ path: string
+
+ /**
+ * 仅当当前路径和某个子项目匹配时可用
+ */
+ currentItems?: Article<T>[]
+
+ /** 分类映射 */
+ map: {
+ /** 当前分类下全局唯一的 key */
+ [key: string]: {
+ /** 对应键值的分类路径 */
+ path: string
+ /** 对应键值的项目 */
+ items: Article<T>[]
+ }
+ }
+}
+
+interface BlogTypeData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** 类别路径 */
+ path: string
+
+ /** 当前类别下的项目 */
+ items: Article<T>[]
+}
+使用 @vuepress/plugin-blog，你可以轻松地将博客功能引入主题。
起步时，插件会首选过滤并选择那些需要作为文章的页面。这将剔除你不想要的页面，并在后续处理中排除它们。
默认情况下，所有从 Markdown 文件生成但不是主页的页面，都将被视作文章。
你可能需要设置 filter 选项来完全自定义要收集的页面。 filter 接受一个形状为 (page: Page) => boolean 的函数。
接着，你应该设置 getInfo 选项为一个接受 Page 作为参数并返回包含所需信息的对象的函数。这样稍后，你可以从组合 API 中获取这些信息。
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ filter: ({ filePathRelative, frontmatter }) => {
+ // 舍弃那些不是从 Markdown 文件生成的页面
+ if (!filePathRelative) return false
+
+ // 舍弃 `archives` 文件夹的页面
+ if (filePathRelative.startsWith('archives/')) return false
+
+ // 舍弃那些没有使用默认布局的页面
+ if (frontmatter.home || frontmatter.layout) return false
+
+ return true
+ },
+
+ getInfo: ({ frontmatter, git = {}, data = {} }) => {
+ // 获取页面信息
+ const info: Record<string, any> = {
+ author: frontmatter.author || '',
+ categories: frontmatter.categories || [],
+ date: frontmatter.date || git.createdTime || null,
+ tags: frontmatter.tags || [],
+ excerpt: data.excerpt || '',
+ }
+
+ return info
+ },
+ }),
+ // 其他插件 ...
+ ],
+}
+基本上，你的博客中需要两种“类型”:
类别:
“类别”是用文章的标签 (或类别) 对它们进行分组。
例如，每篇文章可能都有对应的“分类”和“标签”。
类型:
“类型”是过滤不同条件的文章。
例如，你的帖子中可能有日记或笔记。当帖子带有写作日期信息时，它可以称为“时间线项目”。
了解这两种类型的描述后，你可以设置 category 和 type 选项，它们都接受一个数组，每个元素代表一个配置。
让我们从此处 2 个例子开始。
假设你想为每篇文章设置标签，并且你正在通过 frontmatter.tag 设置它们。同时，你想要在 /tag/ 中使用 TagMap 布局的标签页面，并在/tag/标签名称 中使用 TagList 布局对标签按名称进行分组，你可能需要这样的配置:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // 其他配置 ...
+ category: [
+ {
+ key: 'tag',
+ getter: ({ frontmatter }) => frontmatter.tag || [],
+ path: '/tag/',
+ layout: 'TagMap',
+ frontmatter: () => ({ title: '标签页' }),
+ itemPath: '/tag/:name/',
+ itemLayout: 'TagList',
+ itemFrontmatter: (name) => ({ title: `${name}标签` }),
+ },
+ ],
+ }),
+ // 其他插件 ...
+ ],
+}
+此外，你可能希望为你的一些文章加注星标，并将其展示给访问者。当你在 frontmatter 中设置 star: true 来标记它们时，你可能需要这样的配置来在 /star/ 路径中以 StarList 布局显示它们:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // 其他配置 ...
+ type: [
+ {
+ key: 'star',
+ filter: ({ frontmatter }) => frontmatter.star,
+ path: '/star/',
+ layout: 'StarList',
+ frontmatter: () => ({ title: '星标文章' }),
+ },
+ ],
+ }),
+ // 其他插件 ...
+ ],
+}
+看，设置这两种类型很容易。有关完整选项，请参阅 博客分类配置 和 博客分类配置。
当生成每个页面时，插件将在 frontmatter.blog 中设置如下信息
interface BlogFrontmatterOptions {
+ /** 当前页面的类型 */
+ type: 'category' | 'type'
+ /** 在当前分类或类别下全局唯一的 key */
+ key: string
+ /**
+ * 当前的分类名称
+ *
+ * @description 仅在分类子项目页面中可用
+ */
+ name?: string
+}
+所以你可以直接调用 useBlogCategory() 和 useBlogType()，结果将是当前路由绑定的类别或类型。
此外，你可以通过传递所需的 key 作为参数，来将获得绑定到该 key 的信息。
对于上方的 Node 配置而言，你可以在客户端通过如下方式获取 tag 和 star 的信息:
TagMap 布局:
<template>
+ <div>
+ <h1>Tag page</h1>
+ <ul>
+ <li v-for="({ items, path }, name) in categoryMap.map">
+ <RouteLink :key="name" :to="path" class="category">
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </li>
+ </ul>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+TagList 布局:
<template>
+ <div>
+ <h1>Tag page</h1>
+ <div class="category-wrapper">
+ <RouteLink
+ v-for="({ items, path }, name) in categoryMap.map"
+ :key="name"
+ :to="path"
+ class="category"
+ >
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </div>
+ <div class="article-wrapper" v-if="categoryMap.currentItems">
+ <div v-if="!categoryMap.currentItems.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in categoryMap.currentItems"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline
+ ? `${new Date(info.date).toLocaleDateString()}: `
+ : '') + info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author"
+ >Author: {{ info.author }}</span
+ >
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag"
+ >Tag: {{ info.tag.join(', ') }}</span
+ >
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+StarList 布局:
<template>
+ <div class="article-wrapper" v-if="stars.items">
+ <div v-if="!stars.items.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in stars.items"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline ? `${new Date(info.date).toLocaleDateString()}: ` : '') +
+ info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author">Author: {{ info.author }}</span>
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag">Tag: {{ info.tag.join(', ') }}</span>
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogType } from '@vuepress/plugin-blog/client'
+
+import ArticleList from '../components/ArticleList.vue'
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+
+const stars = useBlogType('star')
+</script>
+有关返回类型，请参阅 Composition API 返回类型。
该插件添加了原生多语言支持，因此你的设置将自动应用于每种语言。
例如，如果用户进行了以下 locales 配置，并且你正在设置上面的“star”示例:
export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+}
+那么 /zh/star/ 和 /star/ 都将可用，并且只会显示对应语言下的文章。
这个插件提供了一个内置的摘要生成器，可以通过将 excerpt 选项设置为 true 来启用。
摘要介绍
摘要是一个 HTML 片段，被用于在博客列表中显示文章的简短描述，所以摘要有如下限制:
isCustomElement 选项。.vuepress/public 的绝对路径或完整路径以确保它们可以在其他地址被访问。摘要生成器将尝试从 Frontmatter 内容中找到有效的摘要分隔符，如果找到，它将使用分隔符之前的内容，分隔符默认为 <!-- more -->，并且你可以通过 excerptSeparator 选项来自定义它。
如果找不到有效的分隔符，它将从 Markdown 文件的开头开始解析内容，直到长度达到预设值时停止。该值默认为 300，你可以通过设置 excerptLength 选项来自定义它。
要选择哪个页面应该生成摘要，你可以使用 excerptFilter 选项。
示例
通常，如果用户设置了 frontmatter.description，你可能希望使用它们，因此如果 frontmatter.description 不为空，你可以让过滤器函数返回 false。
此插件可以自动生成目录页面，也提供目录组件。
npm i -D @vuepress/plugin-catalog@next
+import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ plugins: [
+ catalogPlugin({
+ // 你的选项
+ }),
+ ],
+}
+首先，你应该在路由元信息中设置目录信息:
import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ extendsPage: (page) => {
+ // 在 routeMeta 中设置目录信息
+ page.routeMeta = {
+ // 目录标题
+ title: page.title,
+ // ... 其他信息
+ }
+ },
+}
+你可以之后导入 defineCatalogInfoGetter 并在 客户端配置文件 中使用它来从元信息中提取目录信息。
import { defineCatalogInfoGetter } from '@vuepress/plugin-catalog/client'
+
+defineCatalogInfoGetter((meta) => (meta.title ? { title: meta.title } : null))
+
+export default {}
+目录信息应包含:
title: 目录标题order: 目录顺序 (可选)content: 目录内容组件 (可选)通过 order 排序
插件将按以下方式通过 order 对页面进行排序:
// 从小到大依次排列正数
+order 1 的项目
+order 2 的项目
+...
+order 10 的项目
+...
+// 无 order 的项目
+无 order 的项目
+无 order 的项目
+...
+// 从小到大依次排列负数
+order -10 的项目
+// ...
+order -2 的项目
+order -1 的项目
+1 | 2 | 33booleanfalse类型：(path: string) => Record<string, any>
详情：生成页面的 Frontmatter 获取器。
示例：
import { catalogPlugin } from '@vuepress/plugin-catalog'
+
+export default {
+ plugins: [
+ catalogPlugin({
+ frontmatter: (path) => ({
+ // 你想要的 frontmatter
+ // 你可以自定义标题、作者、时间等
+ }),
+ }),
+ ],
+}
+类型：(RegExp | string)[]
默认值：[]
详情：
生成中需要排除的目录页路径。
"/foo/" 意味着仅排除 /foo/ 文件夹的目录页生成。/^\/foo\// 意味着排除 /foo/ 文件夹及其子文件夹的目录页生成。404 页面会被自动排除。
string类型：CatalogPluginLocaleConfig
interface CatalogPluginLocaleData {
+ /**
+ * 目录标题
+ */
+ title: string
+
+ /**
+ * 空目录提示
+ */
+ empty: string
+}
+
+interface CatalogPluginLocaleConfig {
+ [localePath: string]: CatalogPluginLocaleData
+}
+必填: 否
详情：目录组件国际化配置。
interface CatalogInfo {
+ /** 目录标题 */
+ title: string
+ /** 目录顺序 */
+ order?: number
+ /** 目录内容 */
+ content?: Component
+}
+
+type CatalogInfoGetter = (meta: Record<string, unknown>) => CatalogInfo | null
+
+const defineCatalogInfoGetter: (options: CatalogInfoGetter) => void
+自定义如何从 meta 中提取目录信息。
详情：
该插件默认会全局注册一个 <Catalog /> 组件（除非你设置了 component 选项）。
你可以在主题布局中或直接在 Markdown 文件中使用 <Catalog />。
组件支持四个属性：
level：更改显示层次深度（最大仅支持 3 层），默认为 3。base：显示指定文件夹的目录，默认显示当前文件夹目录。index：为目录项添加索引号，默认无标号。hideHeading：隐藏组件标题，默认会显示 目录 标题。你可以通过 CSS 变量来自定义目录样式：
:root {
+ --catalog-bg-color: #fff;
+ --catalog-bg-secondary-color: #f8f8f8;
+ --catalog-border-color: #e5e5e5;
+ --catalog-active-color: #3eaf7c;
+ --catalog-hover-color: #71cda3;
+}
+详见 Artalk 配置。
el pageTitle, pageKey 和 site 选项为插件的保留选项，将从 VuePress 配置中自动推断，不可设置。
imgUploader 和 avatarURLBuilder 这两个函数选项只能在客户端配置。
你可以直接在插件选项中配置可序列化的选项:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineArtalkConfig 函数来配置 Artalk。
import { defineClientConfig } from 'vuepress/client'
+import { defineArtalkConfig } from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // Artalk 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+Artalk 是一款简洁的自托管评论系统，你可以在服务器上轻松部署并置入前端页面中。
来到你的博客，或是任意位置，放置 Artalk 评论框，让页面具备丰富的社会化功能。
npm i -D artalk
+请参见 Artalk 文档。
请配置 provider: "Artalk" 并将你的服务端地址传入插件选项中的 server。
其他的配置项详见 Artalk 配置。
提示
插件保留 el 选项在页面自行插入 Artalk。同时插件会自动根据 VuePress 信息为你自动设置 pageTitle, pageKey 和 site 选项。
为了能使 Artalk 应用正确的主题，你需要通过 darkmode 属性向 <CommentService /> 传入一个布尔值，代表当前是否开启夜间模式。
stringstringstringstringstring"pathname"booleantruebooleantruebooleantrue"top" | "bottom""top"类型: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+默认值: "light"
详情：
Giscus 在日间模式下使用的主题
应为一个内置主题关键词或者一个 CSS 链接。
类型: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+默认值: "dark"
详情：
Giscus 在夜间模式下使用的主题
应为一个内置主题关键词或者一个 CSS 链接。
你可以直接在插件选项中配置可序列化的选项:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Giscus',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineGiscusConfig 函数来配置 Giscus。
import { defineClientConfig } from 'vuepress/client'
+import { defineGiscusConfig } from 'vuepress-plugin-comment2/client'
+
+defineGiscusConfig({
+ // Giscus 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+Giscus 是一个基于 GitHub Discussion 的评论系统，启用简便。
你需要创建一个公开仓库，并开启评论区，以作为评论存放的地点
你需要安装 Giscus App，使其有权限访问对应仓库。
在完成以上步骤后，请前往 Giscus 页面 获得你的设置。
你只需要填写仓库和 Discussion 分类，之后滚动到页面下部的 “启用 giscus” 部分，获取 data-repo, data-repo-id, data-category 和 data-category-id 这四个属性。
请配置 provider: "Giscus" 并将 data-repo, data-repo-id, data-category 和 data-category-id 作为插件选项传入 repo, repoId, category categoryId。
其他的配置项详见 Giscus 配置。
默认情况下，Giscus 使用 light 或 dark 主题 (基于夜间模式状态)。
::: info 夜间模式
为了能使 Giscus 应用正确的主题，你需要为 <CommentService /> 通过 darkmode 属性传入一个布尔值，代表当前是否开启夜间模式。
:::
如果你想在日间模式和夜间模式下自定义主题，你可以设置 lightTheme 和 darkTheme 选项，使用内置主题关键字或以 https:// 开头的自定义 css 链接。
你既可以在 Node.js 一侧使用插件选项设置选项，也可以通过客户端配置文件在浏览器一侧设置选项。
import { commentPlugin } from 'vuepress-plugin-comment2'
+
+// .vuepress/config.ts
+export default {
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo
+
+ // 在这里放置其他选项
+ // ...
+ }),
+ ],
+}
+import { defineClientConfig } from 'vuepress/client'
+import {
+ defineArtalkConfig,
+ // defineGiscusConfig,
+ // defineTwikooConfig,
+ // defineWalineConfig,
+} from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+有以下你需要注意的限制：
provider、多语言设置和其他资源相关选项必须在插件选项中设置。
为确保 tree-shaking 有效，我们必须在 Node 一侧优化入口，以便打包器可以了解最终打包中应包含哪些资源。
这些选项将在配置参考中用 仅限插件选项 标记。
不能序列化为 JSON 的选项必须在客户端配置中设置。
接收复杂值的选项（例如：函数）不能在插件选项中设置，因为插件运行在 Node.js 环境下，所以我们无法将这些值和它们的上下文传递给浏览器。
这些选项将在配置参考中用 仅限客户端配置 标记。
该插件全局注册了一个组件 <CommentService />。
alias 和布局槽来插入组件。 我们建议你在 <PageNav /> 组件之后插入评论组件 (<CommentService />)，本页可作为一个 Demo 作为参考。默认情况下，<CommentService /> 组件是全局启用的，你可以在插件选项和页面 frontmatter 中使用 comment 选项来控制它。
comment: false 在本地禁用它。comment 设置为 false。 然后你可以在页面 frontmatter 中设置 comment: true 以在局部启用它。你可以在页面 frontmatter 中设置 commentID 选项来自定义评论 ID，该 ID 用于标识要用于页面的评论存储项。默认情况下，它将是页面的 path ，这意味着如果你将站点部署到多个位置，站点间具有相同内容的页面将共享相同的评论数据。
目前你可以选择 Giscus、Waline、Artalk 和 Twikoo。
推荐的评论服务
"Artalk" | "Giscus" | "Twikoo" | "Waline" | "None""None"booleantruestringstring"ap-shanghai"你可以直接在插件选项中配置可序列化的选项:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Twikoo',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineTwikooConfig 函数来配置 Twikoo。
import { defineClientConfig } from 'vuepress/client'
+import { defineTwikooConfig } from 'vuepress-plugin-comment2/client'
+
+defineTwikooConfig({
+ // Twikoo 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+一个简洁、安全、免费的静态网站评论系统，基于 腾讯云开发。
npm i -D twikoo
+部署共有四种方式。
| 部署方式 | 描述 |
|---|---|
| 一键部署 | [不建议] 虽然方便，但是仅支持按量计费环境——也就是说，一键部署的环境，当免费资源用尽后，将会产生费用。且按量计费环境无法切换为包年包月环境。免费额度数据库读操作数只有 500 次 / 天，无法支撑 Twikoo 的运行需求。 |
| 手动部署 | [建议] 手动部署到腾讯云云开发环境，在中国大陆访问速度较快。由于基础版 1 已从 0 元涨价至 6.9 元 / 月，需要付费购买环境才能部署。 |
| 命令行部署 | [不建议] 仅针对有 Node.js 经验的开发者。 |
| Vercel 部署 | [建议] 适用于想要免费部署的用户，在中国大陆访问速度较慢。 |
如果你打算部署到一个现有的云开发环境，请直接从第 3 步开始。
进入云开发 CloudBase活动页面，滚动到“新用户专享”部分，选择适合的套餐，点击“立即购买”，按提示创建好环境。
提示
twikoo.init() 时额外指定环境 region: "ap-guangzhou"包年包月，套餐版本基础版 1，超出免费额度不会收费进入云开发控制台
进入环境-登录授权，启用“匿名登录”
进入环境-安全配置，将网站域名添加到“WEB 安全域名”
进入环境-云函数，点击“新建云函数”
函数名称请填写 twikoo，创建方式请选择 空白函数，运行环境请选择 Nodejs 10.15，函数内存请选择 128MB，点击“下一步”
清空输入框中的示例代码，复制以下代码、粘贴到“函数代码”输入框中，点击“确定”
exports.main = require('twikoo-func').main
+创建完成后，点击“twikoo”进入云函数详情页，进入“函数代码”标签，点击“文件 - 新建文件”，输入 package.json，回车
复制以下代码、粘贴到代码框中，点击“保存并安装依赖”
{ "dependencies": { "twikoo-func": "1.5.0" } }
+注意
如果你打算部署到一个现有的云开发环境，请直接从第 3 步开始。
进入云开发 CloudBase活动页面，滚动到“新用户专享”部分，选择适合的套餐 (一般 0 元套餐即可) ，点击“立即购买”，按提示创建好环境。
进入云开发控制台
进入环境 - 登录授权，启用“匿名登录”
进入环境 - 安全配置，将网站域名添加到“WEB 安全域名”
克隆本仓库
git clone https://github.com/imaegoo/twikoo.git # 或 git clone https://e.coding.net/imaegoo/twikoo/twikoo.git
+cd twikoo
+如果你没有安装 Git，也可以从 Release 页面下载最新的 Source code
如果你所在的地区访问 GitHub 速度慢，也可以尝试另一个仓库地址: https://imaegoo.coding.net/public/twikoo/twikoo/git
安装依赖项
npm install -g yarn # 如 yarn 已安装，可以跳过此步
+yarn install
+授权云开发环境 (此命令会弹出浏览器要求授权，需在有图形界面的系统下进行)
yarn run login
+自动部署
yarn deploy -e 你的环境id
+申请 MongoDB 账号
创建免费 MongoDB 数据库，区域推荐选择 AWS / N. Virginia (us-east-1)
在 Clusters 页面点击 CONNECT，按步骤设置允许所有 IP 地址的连接 (为什么？) ，创建数据库用户，并记录数据库连接字符串，请将连接字符串中的 <password> 修改为数据库密码
申请 Vercel 账号
点击以下按钮将 Twikoo 一键部署到 Vercel
进入 Settings - Environment Variables，添加环境变量 MONGODB_URI，值为第 3 步的数据库连接字符串
进入 Overview，点击 Domains 下方的链接，如果环境配置正确，可以看到 “Twikoo 云函数运行正常” 的提示
Vercel Domains (包含 https:// 前缀，例如 https://xxx.vercel.app) 即为你的环境 ID
请配置 provider: "Twikoo" 并将你的服务端地址传入插件选项中的 server。
其他的配置项详见 Twikoo 配置。
string类型: (WalineEmojiInfo | WalineEmojiPresets)[] | false
type WalineEmojiPresets = `http://${string}` | `https://${string}`
+
+interface WalineEmojiInfo {
+ /**
+ * 选项卡上的 Emoji 名称
+ */
+ name: string
+ /**
+ * 所在文件夹链接
+ */
+ folder?: string
+ /**
+ * Emoji 通用路径前缀
+ */
+ prefix?: string
+ /**
+ * Emoji 图片的类型，会作为文件扩展名使用
+ */
+ type?: string
+ /**
+ * 选项卡显示的 Emoji 图标
+ */
+ icon: string
+ /**
+ * Emoji 图片列表
+ */
+ items: string[]
+}
+默认值: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
参考：
详情：表情设置
类型: string | boolean
默认值: false
参考：
详情：
暗黑模式适配。
'auto' 会根据设备暗黑模式自适应。类型: WalineCommentSorting
默认值: 'latest'
详情：
评论列表排序方式。可选值: 'latest', 'oldest', 'hottest'
类型: string[]
默认值: ['nick', 'mail', 'link']
详情：
评论者相关属性。可选值: 'nick', 'mail', 'link'
类型: string[]
默认值: []
详情：
设置必填项，默认匿名，可选值:
[]['nick']['nick', 'mail']string'enable'登录模式状态，可选值:
'enable': 启用登录 (默认)'disable': 禁用登录，用户只能填写信息评论'force': 强制登录，用户必须注册并登录才可发布评论类型: number | [number, number]
默认值: 0
详情：
评论字数限制。填入单个数字时为最大字数限制。设置为 0 时无限制。
number10类型: WalineImageUploader | false
详情:
type WalineImageUploader = (image: File) => Promise<string>
+参考:
详情：
自定义图片上传方法。默认行为是将图片 Base 64 编码嵌入，你可以设置为 false 以禁用图片上传功能。
函数应该接收图片对象，返回一个提供图片地址的 Promise。
类型: WalineHighlighter | false
type WalineHighlighter = (code: string, lang: string) => string
+参考:
详情：
代码高亮，默认使用一个 < 1kb 的简单高亮器。函数传入代码块的原始字符和代码块的语言。你应该直接返回一个字符串。
你可以传入一个自己的代码高亮器，也可以设置为 false 以禁用代码高亮功能。
类型: WalineTexRenderer | false
type WalineTexRenderer = (blockMode: boolean, tex: string) => string
+参考:
详情：
自定义 TeX 渲染，默认行为是提示预览模式不支持 TeX。函数提供两个参数，第一个参数表示渲染模式是否为块级，第二个参数是 TeX 的字符串，并返回一段 HTML 字符串作为渲染结果。
你可以自行引入 TeX 渲染器并提供预览渲染，建议使用 Katex 或 MathJax，也可以设置为 false 以禁止渲染 TeX。
类型: WalineSearchOptions | false
interface WalineSearchImageData extends Record<string, unknown> {
+ /**
+ * 图片链接
+ */
+ src: string
+
+ /**
+ * 图片标题
+ *
+ * @description 用于图片的 alt 属性
+ */
+ title?: string
+
+ /**
+ * 图片缩略图
+ *
+ * @description 为了更好的加载性能，我们会优先在列表中使用此缩略图
+ *
+ * @default src
+ */
+ preview?: string
+}
+
+type WalineSearchResult = WalineSearchImageData[]
+
+interface WalineSearchOptions {
+ /**
+ * 搜索操作
+ */
+ search: (word: string) => Promise<WalineSearchResult>
+
+ /**
+ * 打开列表时展示的默认结果
+ *
+ * @default () => search('')
+ */
+ default?: () => Promise<WalineSearchResult>
+
+ /**
+ * 获取更多的操作
+ *
+ * @description 会在列表滚动到底部时触发，如果你的搜索服务支持分页功能，你应该设置此项实现无限滚动
+ *
+ * @default (word) => search(word)
+ */
+ more?: (word: string, currentCount: number) => Promise<WalineSearchResult>
+}
+详情：自定义搜索功能，设置 false 可禁用搜索。
类型: string
详情：
reCAPTCHA V3 是 Google 提供的验证码服务，配置 reCAPTCHA V3 网站密钥即可开启该功能。
服务端需要同步配置 RECAPTCHA_V3_SECRET 环境变量。
类型: boolean | string[]
默认值: false
详情：
为文章增加表情互动功能，设置为 true 提供默认表情，也可以通过设置表情地址数组来自定义表情图片，最大支持 8 个表情。
类型: boolean
默认值: true
详情：
是否导入 Meta 图标。
类型: WalineLocales
interface WalineLocales {
+ [localePath: string]: WalineLocale
+}
+参考:
详情：
Waline 多语言配置
你可以直接在插件选项中配置可序列化的选项:
import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Waline',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineWalineConfig 函数来配置 Waline。
import { defineClientConfig } from 'vuepress/client'
+import { defineWalineConfig } from 'vuepress-plugin-comment2/client'
+
+defineWalineConfig({
+ // Waline 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+一个有后端的安全评论系统。
npm i -D @waline/client
+点击左上角 创建应用 并起一个你喜欢的名字 (请选择免费的开发版):
进入应用，选择左下角的 设置 > 应用 Key。你可以看到你的 APP ID,APP Key 和 Master Key。请记录它们，以便后续使用。
国内版需要完成备案接入
如果你正在使用 Leancloud 国内版 (leancloud.cn)，我们推荐你切换到国际版 (leancloud.app)。否则，你需要为应用额外绑定已备案的域名，同时购买独立 IP 并完成备案接入:
设置 > 域名绑定 > API 访问域名 > 绑定新域名 > 输入域名 > 确定。
点击上方按钮，跳转至 Vercel 进行 Server 端部署。
::: note
如果你未登录的话，Vercel 会让你注册或登录，请使用 GitHub 账户进行快捷登录。
:::
输入一个你喜欢的 Vercel 项目名称并点击 Create 继续:
此时 Vercel 会基于 Waline 模板帮助你新建并初始化仓库，仓库名为你之前输入的项目名。
一两分钟后，满屏的烟花会庆祝你部署成功。此时点击 Go to Dashboard 可以跳转到应用的控制台。
点击顶部的 Settings - Environment Variables 进入环境变量配置页，并配置三个环境变量 LEAN_ID, LEAN_KEY 和 LEAN_MASTER_KEY 。它们的值分别对应上一步在 LeanCloud 中获得的 APP ID, APP KEY, Master Key。
::: note
如果你使用 LeanCloud 国内版，请额外配置 LEAN_SERVER 环境变量，值为你绑定好的域名。
:::
环境变量配置完成之后点击顶部的 Deployments 点击顶部最新的一次部署右侧的 Redeploy 按钮进行重新部署。该步骤是为了让刚才设置的环境变量生效。
此时会跳转到 Overview 界面开始部署，等待片刻后 STATUS 会变成 Ready。此时请点击 Visit ，即可跳转到部署好的网站地址，此地址即为你的服务端地址。
点击顶部的 Settings - Domains 进入域名配置页
输入需要绑定的域名并点击 Add
在域名服务器商处添加新的 CNAME 解析记录
| Type | Name | Value |
|---|---|---|
| CNAME | example | cname.vercel-dns.com |
等待生效，你可以通过自己的域名来访问了🎉
在插件选项中设置 provider: "Waline"，同时设置服务端地址 serverURL 为上一步获取到的值。
此时，将 <CommentService> 组件放置在你网站中合适的位置 (通常是页面的底部)，即可使用 Waline 评论功能。
提示
你也可以传入其他 Waline 支持的选项 (除了 el)。详情请见 Waline 配置
<serverURL>/ui/register 进行注册。首个注册的人会被设定成管理员。为你的 VuePress 站点注册自定义容器。
该插件简化了 markdown-it-container 的使用方法，但同时也保留了其原本的能力。
默认主题的 自定义容器 就是由该插件支持的。
npm i -D @vuepress/plugin-container@next
+import { containerPlugin } from '@vuepress/plugin-container'
+
+export default {
+ plugins: [
+ containerPlugin({
+ // 配置项
+ }),
+ ],
+}
+::: <type> [info]
+[content]
+:::
+type 是必需的，应通过 type 配置项来指定。info 是可选的，其默认值可以通过 locales 的 defaultInfo 配置项来指定。content 可是任何合法的 Markdown 内容。提示
该插件可以被多次使用，以便支持不同类型的容器。
类型： string
详情：
容器的类型。
它将会被用作 markdown-it-container 的 name 参数。
类型： Record<string, { defaultInfo: string }>
详情：
容器在不同 locales 下的默认 info 。
如果没有指定该配置项，默认 info 会使用大写的 type 。
示例：
export default {
+ plugins: [
+ containerPlugin({
+ type: 'tip',
+ locales: {
+ '/': {
+ defaultInfo: 'TIP',
+ },
+ '/zh/': {
+ defaultInfo: '提示',
+ },
+ },
+ }),
+ ],
+}
+类型： (info: string) => string
默认值：
(info: string): string =>
+ `<div class="custom-container ${type}">${info ? `<p class="custom-container-title">${info}</p>` : ''}\n`
+类型： (info: string) => string
默认值：
(): string => '</div>\n'
+type MarkdownItContainerRenderFunction = (
+ tokens: Token[],
+ index: number,
+ options: any,
+ env: MarkdownEnv,
+ self: Renderer,
+) => string
+详情：
markdown-it-container 的 render 配置项。
该插件使用了一个默认的 render 函数。但如果你指定了该配置项，那么默认的 render 函数就会被替换掉，此时 locales 、 before 和 after 配置项都会被忽略。
类型： (params: string) => boolean
详情：
markdown-it-container 的 validate 配置项。
类型： string
详情：
markdown-it-container 的 marker 配置项。
此插件会自动在 PC 设备上为每个代码块右上角添加复制按钮。
默认选择器匹配 @vuepress/theme-default，所以在你自己的主题中集成时可能需要调整它。
npm i -D @vuepress/plugin-copy-code@next
+import { copyCodePlugin } from '@vuepress/plugin-copy-code'
+
+export default {
+ plugins: [
+ copyCodePlugin({
+ // options
+ }),
+ ],
+}
+类型：string | string[]
默认值：'.theme-default-content div[class*="language-"] pre'
详情:
代码块选择器
类型：boolean
默认值：false
详情:
是否展示在移动端
类型：number
默认值：2000
详情:
提示消息显示时间，设置为 0 会禁用提示。
类型：number
默认值：800
详情:
注册复制按钮的延时，单位 ms。
如果你使用的主题有切换动画，建议配置此选项为 切换动画时长 + 200
类型：CopyCodePluginLocaleConfig
interface CopyCodePluginLocaleData {
+ /**
+ * 复制文字
+ */
+ copy: string
+
+ /**
+ * 已复制文字
+ */
+ copied: string
+}
+
+interface CopyCodePluginLocaleConfig {
+ [localePath: string]: CopyCodePluginLocaleData
+}
+必填：否
详情:
复制按钮插件的国际化配置。
示例：
import { copyCodePlugin } from '@vuepress/plugin-copy-code'
+
+export default {
+ locales: {
+ '/': {
+ // 这是一个支持的语言
+ lang: 'zh-CN',
+ },
+ '/xx/': {
+ // 这是一个没有收到插件支持的语言
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ copyCodePlugin({
+ locales: {
+ '/': {
+ // 覆盖复制按钮标签文字
+ copy: '复制此段代码',
+ },
+
+ '/xx/': {
+ // 在这里完整设置 `mm-NN` 的多语言配置
+ },
+ },
+ }),
+ ],
+}
+你可以通过 CSS 变量来自定义复制按钮的样式：
:root {
+ --code-copy-icon: url("copy-button.svg");
+ --code-copied-icon: url("copied-button.svg");
+ --copy-code-color: #9e9e9e;
+ --copy-code-hover: rgb(0 0 0 / 50%);
+}
+此插件可以在访问者从你的站点复制内容时，自动追加版权信息，也可以禁止站点的复制或者选择。
npm i -D @vuepress/plugin-copyright@next
+import { copyrightPlugin } from '@vuepress/plugin-copyright'
+
+export default {
+ plugins: [
+ copyrightPlugin({
+ // options
+ }),
+ ],
+}
+此插件默认全局禁用。你可以:
copy: true 手动开启。global: true 让其全局生效，并在页面的 frontmatter 中设置 copy: false 禁用它。处于不打扰用户的考虑，默认配置下仅当复制长度超过 100 时才会追加版权信息。如果你希望改变这个触发值，你可以插件选项中设置 triggerLength，或在页面 frontmatter 单独设置 copy.triggerLength。
你可以通过插件的 author 和 license 选项设置全局作者和协议信息。
如果文档的不同部分拥有不同的作者和协议，你可以通过 authorGetter 和 licenseGetter 传入一个使用当前页面对象作为参数的函数 (page: Page) => string 并通过它返回相应信息。
插件会默认通过模板从作者、协议和页面链接生成版权信息，并在复制时追加。如果你认为这不够灵活，你可以设置 copyrightGetter 返回一个完全由你自定义的版权信息，或返回 null 以使用默认模板。
如果你希望禁止用户复制较长内容，你可以在插件选项中设置 maxLength 控制这个临界值，或在页面 frontmatter 单独设置 copy.maxLength。
disableCopy 或在页面 frontmatter 中设置 copy.disableCopy 来禁用复制，后者具有更高优先级。disableSelection 或在页面 frontmatter 中设置 copy.disableSelection 来禁用文字选择。此选项具有更高优先级stringstring(page: Page) => string | null(page: Page) => string | null(page: Page) => string | nullnumber100number00 意味着无限制。booleanfalsebooleanfalsebooleanfalse类型：string
详情：
首选部署位置。
例子
如果你在 https://myblog.com 和 https://blog.com/username/ 下部署相同的内容，你可能希望选择一个站点作为首选链接。
canonical 设置为 https://myblog.comcanonical 设置为 https://blog.com/username/这样，在另一个站点触发的版权信息也会指向你的首选站点。
类型：CopyrightPluginLocaleConfig
interface CopyrightPluginLocaleData {
+ /**
+ * 作者文字
+ *
+ * @description `:author` 将会被作者替换
+ */
+ author: string
+
+ /**
+ * 协议文字
+ *
+ * @description `:license` 会被当前协议替换
+ */
+ license: string
+
+ /**
+ * 链接文字
+ *
+ * @description `:link` 会替换为当前页面链接
+ */
+ link: string
+}
+
+interface CopyrightPluginLocaleConfig {
+ [localePath: string]: CopyrightPluginLocaleData
+}
+详情：版权插件的国际化配置。
示例：
import { copyrightPlugin } from '@vuepress/plugin-copyright'
+
+export default {
+ locales: {
+ '/': {
+ // this is a supported language
+ lang: 'en-US',
+ },
+ '/xx/': {
+ // the plugin does not support this language
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ copyrightPlugin({
+ locales: {
+ '/': {
+ // Override link text
+ link: 'Original posted at :link',
+ },
+
+ '/xx/': {
+ // Complete locale config for `mm-NN` language here
+ },
+ },
+ }),
+ ],
+}
+number100number00 意味着无限制。booleanfalsebooleanfalse将 Algolia DocSearch 集成到 VuePress 中，为你的文档网站提供搜索功能。
提示
当你正确配置该插件后，默认主题会把 DocSearch 按钮添加到导航栏。
该插件不一定能在其他主题中直接使用，因此你应参考主题本身的文档来获取更多信息。
npm i -D @vuepress/plugin-docsearch@next
+import { docsearchPlugin } from '@vuepress/plugin-docsearch'
+
+export default {
+ plugins: [
+ docsearchPlugin({
+ // 配置项
+ }),
+ ],
+}
+你需要 提交你的网站 URL 来加入 DocSearch 项目。当你的索引成功创建后， DocSearch 团队会将 apiKey 和 indexName 发送到你的邮箱。接下来，你就可以配置该插件，在 VuePress 中启用 DocSearch 了。
或者，你也可以 运行你自己的爬虫 来创建索引，然后使用你自己的 appId, apiKey 和 indexName 来配置该插件。
new Crawler({
+ appId: 'YOUR_APP_ID',
+ apiKey: 'YOUR_API_KEY',
+ rateLimit: 8,
+ startUrls: [
+ // 这是 Algolia 开始抓取网站的初始地址
+ // 如果你的网站被分为数个独立部分，你可能需要在此设置多个入口链接
+ 'https://YOUR_WEBSITE_URL/',
+ ],
+ sitemaps: [
+ // 如果你在使用 Sitemap 插件 (如: @vuepress-plugin/sitemap)，你可以提供 Sitemap 链接
+ 'https://YOUR_WEBSITE_URL/sitemap.xml',
+ ],
+ ignoreCanonicalTo: false,
+ exclusionPatterns: [
+ // 你可以通过它阻止 Algolia 抓取某些 URL
+ ],
+ discoveryPatterns: [
+ // 这是 Algolia 抓取 URL 的范围
+ 'https://YOUR_WEBSITE_URL/**',
+ ],
+ // 爬虫执行的计划时间，可根据文档更新频率设置
+ schedule: 'at 02:00 every 1 day',
+ actions: [
+ // 你可以拥有多个 action，特别是你在一个域名下部署多个文档时
+ {
+ // 使用适当的名称为索引命名
+ indexName: 'YOUR_INDEX_NAME',
+ // 索引生效的路径
+ pathsToMatch: ['https://YOUR_WEBSITE_URL/**'],
+ // 控制 Algolia 如何抓取你的站点
+ recordExtractor: ({ $, helpers }) => {
+ // @vuepress/theme-default 的选项
+ return helpers.docsearch({
+ recordProps: {
+ lvl0: {
+ selectors: '.sidebar-heading.active',
+ defaultValue: 'Documentation',
+ },
+ lvl1: '.theme-default-content h1',
+ lvl2: '.theme-default-content h2',
+ lvl3: '.theme-default-content h3',
+ lvl4: '.theme-default-content h4',
+ lvl5: '.theme-default-content h5',
+ lvl6: '.theme-default-content h6',
+ content: '.theme-default-content p, .theme-default-content li',
+ },
+ indexHeadings: true,
+ })
+ },
+ },
+ ],
+ initialIndexSettings: {
+ // 控制索引如何被初始化，这仅当索引尚未生成时有效
+ // 你可能需要在修改后手动删除并重新生成新的索引
+ YOUR_INDEX_NAME: {
+ attributesForFaceting: ['type', 'lang'],
+ attributesToRetrieve: ['hierarchy', 'content', 'anchor', 'url'],
+ attributesToHighlight: ['hierarchy', 'hierarchy_camel', 'content'],
+ attributesToSnippet: ['content:10'],
+ camelCaseAttributes: ['hierarchy', 'hierarchy_radio', 'content'],
+ searchableAttributes: [
+ 'unordered(hierarchy_radio_camel.lvl0)',
+ 'unordered(hierarchy_radio.lvl0)',
+ 'unordered(hierarchy_radio_camel.lvl1)',
+ 'unordered(hierarchy_radio.lvl1)',
+ 'unordered(hierarchy_radio_camel.lvl2)',
+ 'unordered(hierarchy_radio.lvl2)',
+ 'unordered(hierarchy_radio_camel.lvl3)',
+ 'unordered(hierarchy_radio.lvl3)',
+ 'unordered(hierarchy_radio_camel.lvl4)',
+ 'unordered(hierarchy_radio.lvl4)',
+ 'unordered(hierarchy_radio_camel.lvl5)',
+ 'unordered(hierarchy_radio.lvl5)',
+ 'unordered(hierarchy_radio_camel.lvl6)',
+ 'unordered(hierarchy_radio.lvl6)',
+ 'unordered(hierarchy_camel.lvl0)',
+ 'unordered(hierarchy.lvl0)',
+ 'unordered(hierarchy_camel.lvl1)',
+ 'unordered(hierarchy.lvl1)',
+ 'unordered(hierarchy_camel.lvl2)',
+ 'unordered(hierarchy.lvl2)',
+ 'unordered(hierarchy_camel.lvl3)',
+ 'unordered(hierarchy.lvl3)',
+ 'unordered(hierarchy_camel.lvl4)',
+ 'unordered(hierarchy.lvl4)',
+ 'unordered(hierarchy_camel.lvl5)',
+ 'unordered(hierarchy.lvl5)',
+ 'unordered(hierarchy_camel.lvl6)',
+ 'unordered(hierarchy.lvl6)',
+ 'content',
+ ],
+ distinct: true,
+ attributeForDistinct: 'url',
+ customRanking: [
+ 'desc(weight.pageRank)',
+ 'desc(weight.level)',
+ 'asc(weight.position)',
+ ],
+ ranking: [
+ 'words',
+ 'filters',
+ 'typo',
+ 'attribute',
+ 'proximity',
+ 'exact',
+ 'custom',
+ ],
+ highlightPreTag: '<span class="algolia-docsearch-suggestion--highlight">',
+ highlightPostTag: '</span>',
+ minWordSizefor1Typo: 3,
+ minWordSizefor2Typos: 7,
+ allowTyposOnNumericTokens: false,
+ minProximity: 1,
+ ignorePlurals: true,
+ advancedSyntax: true,
+ attributeCriteriaComputedByMinProximity: true,
+ removeWordsIfNoResults: 'allOptional',
+ },
+ },
+})
+上述 recordProps 是用于默认主题的配置，你可以根据你使用的主题来修改它们。
注意 initialIndexSettings.YOUR_INDEX_NAME.attributesForFaceting 字段必须包含 'lang'，否则该插件将无法正常工作。
提示
如果你使用的不是默认主题，或者在使用 Docsearch 的时候遇到了任何问题，你也可以检查上述的爬虫配置示例，然后前往 Algolia Crawler 仓库，在你项目侧边栏中的 Editor 页面中修改你的配置。
类型： string
是否必需： true
详情：
从 DocSearch 团队收到的 apiKey ，或者由你自己生成。
参考：
类型： string
是否必需： true
详情：
从 DocSearch 团队收到的 indexName ，或者由你自己生成。
参考：
类型： string
是否必需： true
详情：
用于设置你的 Application ID。
参考：
类型： SearchParameters
详情：
Algolia 搜索 API 参数。
参考：
类型： string
默认值： 'Search docs'
详情：
搜索输入框的 placeholder 属性。
参考：
类型： boolean
默认值： false
详情：
是否禁用所有的个性化功能：最近的搜索、收藏的搜索结果等。
参考：
类型： string
详情：
打开弹窗时的初始请求。
参考：
类型： Partial<DocSearchTranslations>
详情：
允许替换 DocSearch 按钮和弹窗内的默认文字。
参考：
类型： Record<string, DocsearchPluginOptions>
详情：
在不同 locales 下对该插件进行不同的配置。
该插件的所有其他选项都可以在 locale 中进行配置。
示例：
export default {
+ plugins: [
+ docsearchPlugin({
+ appId: '<APP_ID>',
+ apiKey: '<API_KEY>',
+ indexName: '<INDEX_NAME>',
+ locales: {
+ '/': {
+ placeholder: 'Search Documentation',
+ translations: {
+ button: {
+ buttonText: 'Search Documentation',
+ },
+ },
+ },
+ '/zh/': {
+ placeholder: '搜索文档',
+ translations: {
+ button: {
+ buttonText: '搜索文档',
+ },
+ },
+ },
+ },
+ }),
+ ],
+}
+类型： string
默认值： base
详情：
搜索索引基础路径。
如果你需要把你的站点部署到不同的域名上，你不需要把它们全都提交到 Docsearch 上来分别生成搜索索引。你可以选择其中一个域名作为 索引域名 ，并且仅将 索引域名 提交到 DocSearch 上来爬去搜索索引。然后，你就可以在不同的部署域名下复用索引。
如果你不同部署域名下的 base 是不一样的，你就需要将这个配置设置成 索引域名 的 base ，这样其他的部署域名就可以正确复用索引了。
类型： boolean
默认值： true
详情：
是否注入 DocSearch 的默认样式。
如果你认为 DocSearch 的默认样式和你的站点不兼容，你可以尝试覆盖默认样式，或者将该选项设置为 false 来完全移除默认样式。
当该选项被禁用时，你需要为 DocSearch 引入你自己的样式。同时要注意，你也无法再使用 样式 章节中提到的样式自定义能力。
你可以通过 @docsearch/css 提供的 CSS 变量来自定义样式：
:root {
+ --docsearch-primary-color: rgb(84, 104, 255);
+ --docsearch-text-color: rgb(28, 30, 33);
+ --docsearch-spacing: 12px;
+ --docsearch-icon-stroke-width: 1.4;
+ --docsearch-highlight-color: var(--docsearch-primary-color);
+ --docsearch-muted-color: rgb(150, 159, 175);
+ --docsearch-container-background: rgba(101, 108, 133, 0.8);
+ --docsearch-logo-color: rgba(84, 104, 255);
+
+ /* modal */
+ --docsearch-modal-width: 560px;
+ --docsearch-modal-height: 600px;
+ --docsearch-modal-background: rgb(245, 246, 247);
+ --docsearch-modal-shadow: inset 1px 1px 0 0 rgba(255, 255, 255, 0.5), 0 3px
+ 8px 0 rgba(85, 90, 100, 1);
+
+ /* searchbox */
+ --docsearch-searchbox-height: 56px;
+ --docsearch-searchbox-background: rgb(235, 237, 240);
+ --docsearch-searchbox-focus-background: #fff;
+ --docsearch-searchbox-shadow: inset 0 0 0 2px var(--docsearch-primary-color);
+
+ /* hit */
+ --docsearch-hit-height: 56px;
+ --docsearch-hit-color: rgb(68, 73, 80);
+ --docsearch-hit-active-color: #fff;
+ --docsearch-hit-background: #fff;
+ --docsearch-hit-shadow: 0 1px 3px 0 rgb(212, 217, 225);
+
+ /* key */
+ --docsearch-key-gradient: linear-gradient(
+ -225deg,
+ rgb(213, 219, 228) 0%,
+ rgb(248, 248, 248) 100%
+ );
+ --docsearch-key-shadow: inset 0 -2px 0 0 rgb(205, 205, 230), inset 0 0 1px 1px
+ #fff, 0 1px 2px 1px rgba(30, 35, 90, 0.4);
+
+ /* footer */
+ --docsearch-footer-height: 44px;
+ --docsearch-footer-background: #fff;
+ --docsearch-footer-shadow: 0 -1px 0 0 rgb(224, 227, 232), 0 -3px 6px 0 rgba(69, 98, 155, 0.12);
+}
+详情：
该插件会全局注册一个 <Docsearch /> 组件，你可以不传入任何 Props 来使用它。
将该组件放置在你想要显示 docsearch 按钮的地方。例如，默认主题将这个组件放在了导航栏的末尾。
提示
该组件主要用于主题开发。在大多数情况下你不需要直接使用该组件。
该插件会为你 Markdown 内容中的外部链接添加一个图标，即
该插件已经集成到默认主题中。
npm i -D @vuepress/plugin-external-link-icon@next
+import { externalLinkIconPlugin } from '@vuepress/plugin-external-link-icon'
+
+export default {
+ plugins: [
+ externalLinkIconPlugin({
+ // 配置项
+ }),
+ ],
+}
+类型： Record<string, { openInNewWindow: string }>
详情：
外部链接图标在不同 locales 下的 A11y 文字。
如果没有指定该配置项，它会降级使用默认文字。
示例：
export default {
+ plugins: [
+ externalLinkIconPlugin({
+ locales: {
+ '/': {
+ openInNewWindow: 'open in new window',
+ },
+ '/zh/': {
+ openInNewWindow: '在新窗口打开',
+ },
+ },
+ }),
+ ],
+}
+类型： boolean
详情：
是否在当前页面的外部链接的后面添加外部链接图标。
你可以通过 CSS 变量来自定义外部链接图标的样式：
:root {
+ --external-link-icon-color: #aaa;
+}
+详情：
该插件会全局注册一个 <ExternalLinkIcon /> 组件，你可以不传入任何 Props 来使用它。
提示
该组件主要用于主题开发。在大多数情况下你不需要直接使用该组件。
channel 插件选项用于配置 feed 的频道。
stringSiteConfig.title频道的标题
stringoptions.hostname 和 context.base 生成)频道地址
stringSiteConfig.description频道描述信息
stringsiteConfig.locales['/'].locales"en-US"频道使用的语言
stringauthor.name 生成 Copyright by $author频道版权信息
string (需是合法的 Date ISOString)频道内容的发布时间
string (需是合法的 Date ISOString)频道内容的上次更新时间
number内容有效时间，即获取后保持缓存而不进行新获取的时间
string这是一个会在频道中使用的图片，建议设置正方形图片、尺寸最好不小于 512×512。
string一个代表频道的图标，建议设置正方形图片、尺寸最好不小于 128×128，背景色透明。
FeedAuthor频道的作者。
interface FeedAuthor {
+ /** 作者姓名 */
+ name: string
+ /** 作者电子邮箱 */
+ email?: string
+ /** 作者网站 */
+ url?: string
+ /**
+ * 作者头像地址
+ *
+ * 正方形，最好不小于 128×128，透明背景
+ */
+ avatar?: string
+}
+stringWebsub 的链接。Websub 需要服务器后端，与 VuePress 主旨不符，如无特殊需要忽略即可。
WebSub
有关信息，详见 Websub。
string部署网站的域名。
booleanfalse是否启用 Atom 格式输出。
booleanfalse是否启用 JSON 格式输出。
booleanfalse是否启用 RSS 格式输出。
string一个大的图片，用作 feed 展示。
string一个小的图标，显示在订阅列表中。
number100设置 feed 的最大项目数量。在所有页面排序好后，插件会截取前 count 个项目。
如果你的站点文章很多，你应该考虑设置这个选项以减少 feed 文件大小。
(RegExp | string)[] | (tagName：string) => boolean应在 Feed 中保留的自定义元素或组件。
默认情况下，所有未知标签均会被移除。
类型：(page: Page)=> boolean
默认值：
;({ frontmatter, filePathRelative }: Page): boolean =>
+ !(
+ frontmatter.home ||
+ !filePathRelative ||
+ frontmatter.article === false ||
+ frontmatter.feed === false
+ )
+自定义的过滤函数，用于过滤哪些项目在 feed 中显示。
类型： (pageA: Page, pageB: Page)=> number
默认值：
// dateSorter 来源于 @vuepress/helper
+;(pageA, pageB): number =>
+ dateSorter(
+ pageA.data.git?.createdTime
+ ? new Date(pageA.data.git?.createdTime)
+ : pageA.frontmatter.date,
+ pageB.data.git?.createdTime
+ ? new Date(pageB.data.git?.createdTime)
+ : pageB.frontmatter.date,
+ )
+Feed 项目的排序器。
默认的排序行为是通过 Git 的文件添加日期 (需要 @vuepress/plugin-git)。
提示
你应该启用 @vuepress/plugin-git 来获取最新创建的页面作为 feed 项目。否则，feed 项目将按照 VuePress 中页面的默认顺序排序。
channel 选项用于配置 Feed 频道。
可用选项详见 配置 → 频道设置
booleanfalse是否在开发服务器中启用
提示
由于性能原因，我们不提供热更新。重启开发服务器以同步你的变更。
string"http://localhost:${port}"开发服务器使用的主机名
string"atom.xml"Atom 格式输出路径，相对于输出路径。
string@vuepress/plugin-feed/templates/atom.xsl 的内容Atom xsl 模板文件没人陪美国
string"atom.xsl"Atom xsl 输出路径，相对于输出路径。
string"feed.json"JSON 格式输出路径，相对于输出路径。
string"rss.xml"RSS 格式输出路径，相对于输出路径。
string@vuepress/plugin-feed/templates/rss.xsl 的内容RSS xsl 模板文件内容。
string"rss.xsl"RSS xsl 输出路径，相对于输出路径。
Feed 生成控制器，详见 Feed 生成器。
此插件内置了生成器，只有当你想完全控制 feed 生成时才需要设置此选项。
Record<string, BaseFeedOptions>你可以将它用于每个语言环境的特定选项。
除 hostname 外，上述任何选项均受支持。
你可以通过配置每个页面的 Frontmatter，来对每个 Feed 项目生成进行单独的控制。
默认情况下，所有文章均会被添加至 feed 流。如果你想在 feed 中移除特定页面，你可以在 frontmatter 中设置 feed: false。
string由 VuePress 自动生成，默认为页面的 h1 内容
string页面描述
Date页面的发布日期
boolean该页面是否是文章
如果此项设置为
false，则该页不会包含在最终的 feed 中。
string页面版权信息
string页面的封面/分享图，需为完整链接或绝对链接。
stringFeed 项目的标题
stringFeed 项目的描述
stringFeed 项目的内容
FeedAuthor[] | FeedAuthorFeed 项目的作者
interface FeedAuthor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+FeedContributor[] | FeedContributorFeed 项目的贡献者
interface FeedContributor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+stringFeed 项目的标识符，用于标识 Feed 项目。
你应该确保每个 Feed 项目有全局唯一的 guid。
你可以通过控制插件选项中的 getter 来完全控制 Feed 项目的生成。
(page: Page) => string项目标题获取器
(page: Page) => string项目链接获取器
(page: Page) => string | undefined项目描述获取器
提示
因为 Atom 在摘要中支持 HTML，所以如果可能的话，你可以在这里返回 HTML 内容，但内容必须以标记 html: 开头。
(page: Page) => string项目内容获取器
(page: Page) => FeedAuthor[]项目作者获取器。
获取器应在作者信息缺失时返回空数组。
interface FeedAuthor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => FeedCategory[] | undefined项目分类获取器。
interface FeedCategory {
+ /**
+ * 分类名称
+ */
+ name: string
+
+ /**
+ * 标识分类法的字符串
+ *
+ * @description rss format only
+ */
+ domain?: string
+
+ /**
+ * URI 标识的分类 scheme
+ *
+ * @description atom format only
+ */
+ scheme?: string
+}
+(page: Page) => FeedEnclosure | undefined项目附件获取器。
interface FeedEnclosure {
+ /**
+ * Enclosure 地址
+ */
+ url: string
+
+ /**
+ * 类型
+ *
+ * @description 应为一个标准的 MIME 类型，rss format only
+ */
+ type: string
+
+ /**
+ * 按照字节数计算的大小
+ *
+ * @description rss format only
+ */
+ length?: number
+}
+(page: Page) => Date | undefined项目发布日期获取器
(page: Page) => Date项目最后更新日期获取器
(page: Page) => string项目图片获取器
确保返回一个完整的 URL。
(page: Page) => FeedContributor[]项目贡献者获取器
获取器应在贡献者信息缺失时返回空数组。
interface FeedContributor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => string | undefined项目版权获取器
插件可为你生成以下三种格式的 feed 文件:
请按照需要生成的格式，在插件选项中设置 atom, json 或 rss 为 true。
为了正确生成 Feed 链接，你需要在插件选项中设置 hostname。
当你在浏览器中打开 Feed 文件时，我们会通过 xsl 模板将 atom 和 rss feed xml 魔法般地转换为可读的 html。你可以查看本站的 atom 和 rss feed 作为案例！
如果你想在开发服务器中预览 Feed，你需要在插件选项中设置 devServer: true。如果你没有使用默认的 http://localhost:{port}，你还需要设置 devHostname。
你可以通过设置 channel 选项来自自定义 Feed 频道的各项信息。
我们推荐进行如下设置:
channel.pubDate 中channel.ttl 中设置内容的更新周期(单位: 分钟)channel.copyright 设置版权信息channel.author 设置频道作者。详细的选项及其默认值详见 配置 → 频道设置
默认情况下，所有文章均会被添加至 feed 流。
你可以在 frontmatter 中配置 feed 和其他选项控制每个页面的 Feed 项目内容，详见 Frontmatter 选项 了解它们如何被转换。
你可以通过配置插件选项中的 getter 完全控制 Feed 项目的生成逻辑。 详细的选项及其默认值详见 配置 → Feed 获取器
插件会针对每个语言生成单独的 Feed。
你可以通过插件选项中的 locales 分别对不同语言提供不同的默认设置。
该插件会收集你的页面的 Git 信息，包括创建和更新时间、贡献者等。
默认主题的 lastUpdated 和 contributors 就是由该插件支持的。
该插件主要用于开发主题，大部分情况下你不需要直接使用它。
npm i -D @vuepress/plugin-git@next
+import { gitPlugin } from '@vuepress/plugin-git'
+
+export default {
+ plugins: [
+ gitPlugin({
+ // 配置项
+ }),
+ ],
+}
+该插件要求你的项目在 Git 仓库 下，这样它才能从提交历史记录中收集信息。
在构建站点时，你应该确保所有的提交记录是可以获取到的。举例来说， CI 工作流通常会在克隆你的仓库时添加 --depth 1 参数来避免拉取全部的提交记录，因此你需要禁用这个功能，以便该插件在 CI 可以中正常使用。
注意
该插件会显著降低准备数据的速度，特别是在你的页面数量很多的时候。你可以考虑在 dev 模式下禁用该插件来获取更好的开发体验。
类型： boolean
默认值： true
详情：
是否收集页面的创建时间。
类型： boolean
默认值： true
详情：
是否收集页面的更新时间。
类型： boolean
默认值： true
详情：
是否收集页面的贡献者。
类型： string[]
详情：
文件相对路径组成的数组，该数组中的文件会在计算页面数据时被包含在内。
示例：
---
+gitInclude:
+ - relative/path/to/file1
+ - relative/path/to/file2
+---
+该插件会向页面数据中添加一个 git 字段。
在使用该插件后，可以在页面数据中获取该插件收集到的 Git 信息：
import type { GitPluginPageData } from '@vuepress/plugin-git'
+import { usePageData } from 'vuepress/client'
+
+export default {
+ setup() {
+ const page = usePageData<GitPluginPageData>()
+ console.log(page.value.git)
+ },
+}
+类型： number
详情：
页面第一次提交的 Unix 毫秒时间戳。
该属性将取当前页面及 gitInclude 中所列文件的第一次提交的时间戳的最小值。
类型： number
详情：
页面最后一次提交的 Unix 毫秒时间戳。
该属性将取当前页面及 gitInclude 中所列文件的最后一次提交的时间戳的最大值。
GitContributor[]interface GitContributor {
+ name: string
+ email: string
+ commits: number
+}
+详情：
页面的贡献者信息。
该属性将会包含 gitInclude 所列文件的贡献者。
将 Google Analytics 集成到 VuePress 中。
该插件会通过引入 gtag.js 来启用 Google Analytics 4 。
npm i -D @vuepress/plugin-google-analytics@next
+import { googleAnalyticsPlugin } from '@vuepress/plugin-google-analytics'
+
+export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ // 配置项
+ }),
+ ],
+}
+Google Analytics 会 自动收集部分事件 ，比如 page_view, first_visit 等。
因此，如果你只是想收集站点的一些基础数据，你只需要正确设置 Measurement ID ，不需要再额外做其他事情。
在引入该插件之后，一个全局的 gtag() 函数会被挂载到 window 对象上，你可以使用它进行 自定义事件的上报 。
类型： string
详情：
Google Analytics 4 的 Measurement ID ，应以 'G-' 开头。
你可以通过 这里 的指引来找到你的 Measurement ID 。注意区分 Google Analytics 4 的 Measurement ID （即 "G-" 开头的 ID） 和 Universal Analytics 的 Tracking ID （即 "UA-" 开头的 ID）。
示例：
export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ id: 'G-XXXXXXXXXX',
+ }),
+ ],
+}
+类型： boolean
详情：
设置为 true 可以向 DebugView 发送事件。了解更多关于 DebugView 的信息 。
示例：
export default {
+ plugins: [
+ googleAnalyticsPlugin({
+ id: 'G-XXXXXXXXXX',
+ debug: true,
+ }),
+ ],
+}
+此插件将检查您的 markdown 文件中的死链接。
此插件已集成到默认主题中。
npm i -D @vuepress/plugin-links-check@next
+import { linksCheckPlugin } from '@vuepress/plugin-links-check'
+
+export default {
+ plugins: [
+ linksCheckPlugin({
+ // 选项
+ }),
+ ],
+}
+类型：boolean
默认值：true
详情：
是否在开发服务器中检查 markdown 中的死链接
类型：boolean | 'error'
默认值：true
详情：
是否在构建中检查 markdown 中的死链接。如果设置为 'error'，则构建将在存在死链接时失败。
类型：(string | RegExp)[] | ((link: string, isDev: boolean) => boolean)
详情：
应该从检查中排除的链接。您可以使用字符串或正则表达式的列表，或者返回布尔值的函数。
示例：
linksCheckPlugin({
+ exclude: [
+ // 通过字符串排除链接
+ '/exclude-link',
+ // 通过正则表达式排除链接
+ /\/exclude-link-regex/,
+ ],
+
+ // 或者通过函数排除链接
+ exclude: (link, isDev) => {
+ if (isDev) {
+ return link.startsWith('/exclude-link-dev')
+ }
+ return link.startsWith('/exclude-link-build')
+ },
+})
+将 medium-zoom 集成到 VuePress 中，为图片提供可缩放的功能。
该插件已经集成到默认主题中。
npm i -D @vuepress/plugin-medium-zoom@next
+import { mediumZoomPlugin } from '@vuepress/plugin-medium-zoom'
+
+export default {
+ plugins: [
+ mediumZoomPlugin({
+ // 配置项
+ }),
+ ],
+}
+类型： string
默认值： ':not(a) > img'
详情：
可缩放的图片的选择器。
默认情况下，该插件会使 <a> 标签以外的所有图片都支持缩放。
类型： number
默认值： 500
详情：
以毫秒为单位的延迟。
在切换路由进入一个新页面时，该插件会在一定延迟后才使页面内的图片支持缩放。
类型： Object
详情：
medium-zoom 的配置项。
参考：
你可以通过 zoomOptions 对大部分的缩放样式进行自定义，不过作为补充，该插件同样提供了一些 CSS 变量：
:root {
+ --medium-zoom-z-index: 100;
+ --medium-zoom-bg-color: #ffffff;
+ --medium-zoom-opacity: 1;
+}
+详情：
返回该插件使用的 Zoom 实例，便于你直接使用实例上的 methods 。
该插件会在切换路由进入当前页面时使图片支持缩放。但如果你要动态添加新图片，那么你可能就需要这个方法来让这些新图片也支持缩放。
该插件在 Zoom 实例上额外添加了一个 refresh 方法，它将使用 selector 作为默认参数，先调用 zoom.detach() 再调用 zoom.attach() ，便于你快速刷新当前页面图片的缩放状态。
示例：
import { nextTick } from 'vue'
+import { useMediumZoom } from '@vuepress/plugin-medium-zoom/client'
+
+export default {
+ setup() {
+ const zoom = useMediumZoom()
+
+ // ... 进行了一些操作，在当前页面添加了新的图片
+
+ // 此时你可能需要手动调用 `refresh` 来让这些新图片支持缩放
+ nextTick(() => {
+ zoom.refresh()
+ })
+ },
+}
+将 nprogress 集成到 VuePress 中，在切换到另一个页面时会展示进度条。
该插件已经集成到默认主题中。
npm i -D @vuepress/plugin-nprogress@next
+import { nprogressPlugin } from '@vuepress/plugin-nprogress'
+
+export default {
+ plugins: [nprogressPlugin()],
+}
+你可以通过 CSS 变量来自定义进度条的样式：
:root {
+ --nprogress-color: #29d;
+ --nprogress-z-index: 1031;
+}
+为你的主题提供调色板功能。
该插件主要用于开发主题，并且已经集成到默认主题中。大部分情况下你不需要直接使用它。
对于主题作者，该插件可以帮助你提供用户自定义样式的能力。
npm i -D @vuepress/plugin-palette@next
+import { palettePlugin } from '@vuepress/plugin-palette'
+
+export default {
+ plugins: [
+ palettePlugin({
+ // 配置项
+ }),
+ ],
+}
+该插件会提供一个 @vuepress/plugin-palette/palette （调色板文件）和一个 @vuepress/plugin-palette/style （样式文件），用于在你的主题样式中引入。
调色板文件用于定义样式变量，因此它一般会在你主题样式的开头引入。举例来说，用户可以在调色板中定义 CSS 变量 、 SASS 变量 、 LESS 变量 或 Stylus 变量 ，然后你可以在你的主题样式中使用这些变量。
样式文件用于覆盖默认样式或添加额外样式，因此它一般会在你主题样式的末尾引入。
在你的主题中使用该插件，假设你使用 SASS 作为 CSS 预处理器：
export default {
+ // ...
+ plugins: [palettePlugin({ preset: 'sass' })],
+}
+在你主题需要使用对应变量的地方引入该插件的调色板文件，比如在 Layout.vue 中：
<template>
+ <h1 class="palette-title">你好，调色板！</h1>
+</template>
+
+<style lang="scss">
+/* 从该插件的调色板中引入变量 */
+@import '@vuepress/plugin-palette/palette';
+
+/* 设置变量的默认值 */
+$color: red !default;
+
+/* 在你的样式中使用变量 */
+.palette-title {
+ color: $color;
+}
+</style>
+然后，用户就可以在 .vuepress/styles/palette.scss 中自定义变量：
$color: green;
+在你主题的样式之后引入该插件的样式文件，比如在 clientConfigFile 中：
// 引入你主题本身的样式文件
+import 'path/to/your/theme/style'
+// 引入该插件的样式文件
+import '@vuepress/plugin-palette/style'
+然后，用户就可以在 .vuepress/styles/index.scss 中添加额外样式，并可以覆盖你主题本身的样式：
h1 {
+ font-size: 2.5rem;
+}
+类型： 'css' | 'sass' | 'less' | 'stylus'
默认值： 'css'
详情：
设置其他选项的预设。
如果你没有对该插件进行进阶定制化的需要，建议只设置该配置项并忽略其他选项。
类型： string
默认值：
'.vuepress/styles/palette.css''.vuepress/styles/palette.scss''.vuepress/styles/palette.less''.vuepress/styles/palette.styl'详情：
用户调色板文件的路径，是针对源文件目录的相对路径。
默认值依赖于 preset 配置项。
该文件用于用户定义样式变量，建议保持默认值作为约定的文件路径。
类型： string
默认值：
'styles/palette.css''styles/palette.scss''styles/palette.less''styles/palette.styl'详情：
生成的调色板临时文件的路径，是针对临时文件文件目录的相对路径。
默认值依赖于 preset 配置项。
你应该使用 '@vuepress/plugin-palette/palette' 别名来引入调色板文件，因此在绝大多数情况下你不需要修改该配置项。
类型： string
默认值：
'.vuepress/styles/index.css''.vuepress/styles/index.scss''.vuepress/styles/index.less''.vuepress/styles/index.styl'详情：
用户样式文件的路径，是针对源文件目录的相对路径。
默认值依赖于 preset 配置项。
该文件用于用户覆盖默认样式和添加额外样式，建议保持默认值作为约定的文件路径。
类型： string
默认值：
'styles/index.css''styles/index.scss''styles/index.less''styles/index.styl'详情：
生成的样式临时文件的路径，是针对临时文件文件目录的相对路径。
默认值依赖于 preset 配置项。
你应该使用 '@vuepress/plugin-palette/style' 别名来引入样式文件，因此在绝大多数情况下你不需要修改该配置项。
类型： (filePath: string) => string
默认值：
(filePath) => `@import '${filePath}';\n`(filePath) => `@forward 'file:///${filePath}';\n`(filePath) => `@import '${filePath}';\n`(filePath) => `@require '${filePath}';\n`详情：
用于生成引入代码的函数。
默认值依赖于 preset 配置项。
该配置项用于生成 tempPaletteFile 和 tempStyleFile ，在绝大多数情况下你不需要修改该配置项。
此插件会使页面正文内的图片在点击时进入浏览模式浏览。
npm i -D @vuepress/plugin-photo-swipe@next
+import { photoSwipePlugin } from '@vuepress/plugin-photo-swipe'
+
+export default {
+ plugins: [
+ photoSwipePlugin({
+ // 选项
+ }),
+ ],
+}
+在图片预览模式中，你可以:
提示
string | string[]".theme-default-content :not(a) > img:not([no-view])"booleantrue类型：number
默认值：800
详情：
操作页面 DOM 的延时，单位 ms。
提示
如果你使用的主题有切换动画，建议配置此选项为 切换动画时长 + 200。
类型：PhotoSwipePluginLocaleConfig
interface PhotoSwipePluginLocaleData {
+ /**
+ * 关闭按钮标签文字
+ */
+ close: string
+
+ /**
+ * 全屏按钮标签文字
+ */
+ fullscreen: string
+
+ /**
+ * 分享按钮标签文字
+ */
+ share: string
+
+ /**
+ * 缩放按钮标签文字
+ */
+ zoom: string
+
+ /**
+ * 上一张图片按钮标签文字
+ */
+ prev: string
+
+ /**
+ * 下一张图片按钮标签文字
+ */
+ next: string
+
+ /**
+ * 功能按钮配置
+ */
+ buttons: PhotoSwipeDefaultUI.ShareButtonData[]
+}
+
+interface PhotoSwipePluginLocaleConfig {
+ [localePath: string]: PhotoSwipePluginLocaleData
+}
+详情：Photo Swipe 插件的国际化配置。
示例：
import { defineUserConfig } from 'vuepress'
+import { photoSwipePlugin } from '@vuepress/plugin-photo-swipe'
+
+export default defineUserConfig({
+ locales: {
+ '/': {
+ // 这是一个支持的语言
+ lang: 'zh-CN',
+ },
+ '/xx/': {
+ // 这是一个没有收到插件支持的语言
+ lang: 'mm-NN',
+ },
+ },
+
+ plugins: [
+ photoSwipePlugin({
+ locales: {
+ '/': {
+ // 覆盖分享标签文字
+ share: '分享给伙伴',
+ },
+
+ '/xx/': {
+ // 在这里完整设置 `mm-NN` 的多语言配置
+ },
+ },
+ }),
+ ],
+})
+类型： string | false
详情：
当前页面的图片选择器或 false 以在当前页面中禁用 photo-swipe。
传递给 photo-swipe 的额外选项。
import { definePhotoSwipeConfig } from '@vuepress/plugin-photo-swipe/client'
+
+definePhotoSwipeConfig({
+ // 在此设置 photoswipe 选项
+})
+
+export default {}
+你可以通过 API 来调用 photoswipe。
createPhotoSwipe 允许你以编程的方式查看图片链接:
<script setup lang="ts">
+import { onMounted, onUnmounted } from 'vue';
+import { createPhotoSwipe } from "@vuepress/plugin-photo-swipe/client";
+
+let state: PhotoSwipeState | null = null;
+
+const openPhotoSwipe = (index: number) => {
+ state?.open(index - 1);
+};
+
+onMounted(async () => {
+ // 通过图片链接创建一个新的 photoswipe 实例
+ state= await createPhotoSwipe(
+ [
+ 'https://exmaple.com/image1.png'
+ 'https://exmaple.com/image2.png'
+ 'https://exmaple.com/image3.png'
+ ],
+ {
+ // photoswipe 选项
+ }
+ );
+});
+
+onUnmounted(() => {
+ state?.destroy()
+})
+</script>
+
+<template>
+ <button v-for="i in 3" @click="openPhotoSwipe(i)">open photo {{ i }}</button>
+</template>
+registerPhotoSwipe 允许你为给定的图片元素注册 photoswipe:
<script setup lang="ts">
+import { onMounted, onUnmounted } from 'vue'
+import { registerPhotoSwipe } from '@vuepress/plugin-photo-swipe/client'
+
+let destroy: () => void | null = null
+
+onMounted(async () => {
+ await nextTick()
+
+ const images = Array.from(document.querySelectorAll('img'))
+
+ // 通过图片元素创建一个新的 photoswipe 实例
+ state = await registerPhotoSwipe(images, {
+ // photoswipe 选项
+ })
+})
+
+onUnmounted(() => {
+ destroy?.()
+})
+</script>
+你可以通过 CSS 变量来自定义部分样式：
:root {
+ --photo-swipe-bullet: #fff;
+ --photo-swipe-bullet-active: #3eaf7c;
+}
+该插件使用 Prism.js 来为 Markdown 代码块启用代码高亮。
该插件已经集成到默认主题中。
需要注意的是，该插件仅会给代码块添加 HTML 标记，而不会添加样式。当你在一个自定义主题中使用它时，可能需要自己选择并引入 Prism.js 样式主题。
npm i -D @vuepress/plugin-prismjs@next
+import { prismjsPlugin } from '@vuepress/plugin-prismjs'
+
+export default {
+ plugins: [
+ prismjsPlugin({
+ // 配置项
+ }),
+ ],
+}
+类型： string[]
默认值： ['markdown', 'jsdoc', 'yaml']
详情：
需要预加载的语言。
默认情况下，语言会在解析 Markdown 文件时按需加载。
然而， Prism.js 在动态加载语言时可能会遇到 一些潜在的问题 。为了避免这些问题，你可以使用该配置项来预加载一些语言。
类型：boolean
默认值：false
详情：
是否在 Service Worker 首次成功注册时显示 PWA 安装按钮
类型：ManifestOption
详情：
填充一个将被解析为 manifest.webmanifest 的对象。
提示
如果未设置某些选项，它们会回退到插件预设值。
siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.description || siteConfig.locales['/'].description || "A site built with vuepress"siteConfig.locales['/'].lang || "en-US"context.basecontext.base"standalone""#46bd87""#ffffff""portrait-primary"false参考：
类型：string
详情：
favicon.ico 地址，填入绝对路径。
注意
我们建议你为你的站点生成 favicon。
string"#46bd87"booleanfalsebooleanfalse类型：number
默认值：2048
详情：
允许缓存的最大大小 (以 KB 为单位)
注意
此选项具有最高优先级，任何超过此值的文件都会被排除。
所以你如果生成了很大的 HTML 或 JS 文件，请考虑调高此值，否则你的 PWA 可能无法在离线模式下正常运行。
类型：number
默认值：1024
详情：
图片允许缓存的最大大小 (以 KB 为单位)
该选项不能大于 maxSize 选项
类型："disabled" | "available" | "hint" | "force"
默认值："available"
详情：
发现新内容时的控制逻辑。
"disabled": 即使有新的 service worker 也不做任何事情，新的 service work 开始等待后，会在用户下次访问时接管页面，让用户获得新内容。
"available": 仅当新的 service worker 可用时才显示更新弹出窗口
"hint": 显示更新内容可用提示，并允许用户立即刷新。当新的 SW 成功注册后，将转为更新内容就绪弹窗。
当你希望用户立即查看新文档时，这很有帮助。
提示
如果用户在新 SW 就绪前选择刷新，当前的 Service Worker 将被注销，并且请求将开始向 Web 发出。新的 service worker 将开始安装并在安装后接管页面。
"force": 立即注销当前 Service Worker 然后刷新以获取新内容
警告
虽然这可以确保用户访问的是最新内容，但这可能会影响访问体验。
提示
文档的更新方式由以前的版本控制，因此当前选项仅影响此版本的下一次更新。
更高支持苹果的特殊设置，忽略它们是安全的。
string"black" | "white""black"string针对微软磁贴的特殊设置，忽略它们是安全的。
stringstringthemeColorstring"PwaFoundPopup"string"PwaReadyPopup"booleanfalse详情：
传递给 workbox-build 的选项，具体详情，请见 Workbox 文档
类型：PwaPluginLocaleConfig
interface PwaPluginLocaleData {
+ /**
+ * 安装按钮文字
+ */
+ install: string
+
+ /**
+ * iOS 安装文字
+ */
+ iOSInstall: string
+
+ /**
+ * 取消按钮文字
+ */
+ cancel: string
+
+ /**
+ * 关闭按钮文字
+ */
+ close: string
+
+ /**
+ * 上一张图片文字
+ */
+ prevImage: string
+
+ /**
+ * 下一张图片文字
+ */
+ nextImage: string
+
+ /**
+ * 安装解释
+ */
+ explain: string
+
+ /**
+ * 描述标签文字
+ */
+ desc: string
+
+ /**
+ * 特性标签文字
+ */
+ feature: string
+
+ /**
+ * 更新内容提示文字
+ */
+ hint: string
+
+ /**
+ * 更新内容可用文字
+ */
+ update: string
+}
+
+interface PwaPluginLocaleConfig {
+ [localePath: string]: PwaPluginLocaleData
+}
+详情：
PWA 插件的国际化配置。
详情：
返回此插件的事件派发器。
你可以添加监听器函数到 register-service-worker 提供的事件。
示例：
import { usePwaEvent } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+ event.on('ready', (registration) => {
+ console.log('Service worker is active.')
+ })
+ },
+}
+详情：
当发现新内容时强制刷新页面。
示例：
import { forceUpdate } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ forceUpdate()
+ })
+ },
+}
+详情：
手动注册 Service Worker。
参数：
| 参数 | 类型 | 描述 |
|---|---|---|
| serviceWorkerPath | string | Service worker 的路径 |
| hooks | object | Service worker 的钩子 |
| showStatus | boolean | 在控制台输出状态日志 |
interface Hooks {
+ registrationOptions?: RegistrationOptions
+ ready?: (registration: ServiceWorkerRegistration) => void
+ registered?: (registration: ServiceWorkerRegistration) => void
+ cached?: (registration: ServiceWorkerRegistration) => void
+ updated?: (registration: ServiceWorkerRegistration) => void
+ updatefound?: (registration: ServiceWorkerRegistration) => void
+ offline?: () => void
+ error?: (error: Error) => void
+}
+import { registerSW } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ registerSW('/service-worker.js', {
+ ready(registration) {
+ console.log('Service worker is active.')
+ },
+ })
+ })
+ },
+}
+详情：
激活等待中的 Service Worker。
参数：
| 参数 | 类型 | 描述 |
|---|---|---|
| registration | ServiceWorkerRegistration | 想要激活的 Service Worker 的注册 |
import { usePwaEvent, skipWaiting } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+
+ event.on('updated', (registration) => {
+ console.log('The waiting service worker is available.')
+ // activate the waiting service worker
+ skipWaiting(registration)
+ })
+ },
+}
+详情：
手动注销 Service Worker。
示例：
import { unregisterSW } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ unregisterSW()
+ })
+ },
+}
+你可以通过 CSS 变量来自定义样式：
:root {
+ --pwa-z-index: 10;
+ --pwa-color: #2c3e50;
+ --pwa-bg-color: #ffffff;
+ --pwa-border-color: #3eaf7c;
+ --pwa-shadow-color: rgb(0 0 0 / 15%);
+ --pwa-btn-text-color: #ffffff;
+ --pwa-btn-bg-color: #3eaf7c;
+ --pwa-btn-hover-bg-color: #4abf8a;
+ --pwa-content-color: #333;
+ --pwa-content-light-color: #666;
+}
+将你的 VuePress 站点变成渐进式网络应用程序 (PWA)[1]。
此插件使用 workbox-build 生成 Service Worker 文件，并使用 register-service-worker 注册 Service Worker。
注意
如果你启用过该插件，并想要禁用它，你可能需要 `@vuepress/plugin-remove-pwa 来移除现有的 Service Worker 。
A PWA uses a Service Worker [2] (SW for short) to cache and proxy site content.
一个 PWA 使用 Service Worker [2:1] (简称 SW) 来获取并托管网站内容。
为了使你的网站符合 PWA 的要求，一个网络 App 清单[3]文件是必要的，并且你的 PWA 应满足可安装性[4]要求。
你可以通过设置 manifest 选项来自定义 manifest 文件，或者在 public 文件夹中提供 manifest.webmanifest 或 manifest.json。前者优先级更高。
插件会自动为你生成 manifest.webmanifest，并在每个页面的 <head> 中添加清单链接声明，但是 你至少应该通过 manifest.icons 或 PWA 插件中的其他选项设置一个有效的图标。
注意
可安装性[4:1]规范要求 manifest 中至少声明一个有效的图标。
所以如果你不配置 manifest.icons，访问者只能享受到 Service Worker 缓存带来的离线可访问性，而并不能作为 PWA 进行安装。
此外，该插件默认不处理清单中的任何内容，而是按原样输出。 这意味着，如果你计划部署到子目录，则应自行将 URL 前缀附加到自己的清单 Urls 中。如果你需要的所有东西都在 base 文件夹下，你可以在插件选项中设置 appendBase: true 让插件将 base 自动附加到任何地址。
为了更好的控制 Service Worker 可以预缓存的内容，插件提供了相关的缓存控制选项。
默认情况下插件会预缓存所有的 JS 和 CSS 文件，但仅缓存主页和 404 页面的 HTML。插件同时还会缓存字体文件 (woff, woff2, eot, ttf, otf) 和 SVG 图标。
如果你的站点只有少量重要图片，并希望它们在离线模式下显示，你可以通过设置 cacheImage 选项为 true 来缓存站点图片。
我们通过文件后缀名识别图片，任何以 .png, .jpg, .jpeg, .gif, .bmp, .webp 结尾的文件都会视为图片。
当你网站体积不大，并且希望文档完全离线可用时，你可以通过设置 cacheHTML 为 true 来缓存所有 HTML 页面。
为什么默认不缓存非主页和 404 页面
虽然说 VuePress 为所有的页面通过 SSG[5] 生成了 HTML 文件，但是这些文件主要用于 SEO[6]，并能够让你在后端不做 SPA[7] 配置的情况下能够直接访问任何链接。
VuePress 本质上是一个 SPA。这意味着你只需要缓存主页并从主页进入即可正常访问所有页面。所以默认不缓存其他 HTML 能够有效减小缓存大小 (可以缩减大约 40% 的体积)，加快 SW 更新速度。
但是这样做也有缺点，如果用户直接从非主页进入网站，首个页面的 HTML 文件仍需要从互联网加载。同时离线环境下，用户只能通过主页进入再自行导航到对应页面，直接访问某个链接会出现无法访问的提示。
为了防止在预缓存列表中包含大文件，任何 > 2 MB 的文件或 > 1 MB 的图片都将被忽略。 你可以通过 maxSize 和 maxImageSize 来自定义大小限制 (单位为 KB)。
我们提供 update 选项控制用户如何接收更新。
update 选项的默认值是 "available"，这意味着当网站内容更新后，新的 SW 会在后台静默安装，并在安装结束后弹窗提示用户新内容就绪。用户可以自主选择是否立即刷新查看新内容。这意味在新 SW 就绪前用户会访问旧版本网站。
如果你的文档仍在建设期，希望尽早提示用户他可能在阅读已过时的内容，你可以将其设置为 "hint"。这样用户在进入文档后数秒内就可以收到新内容已发布的通知。但这样做的负面效果是如果用户在新 SW 就绪前选择更新，那么他将在新 SW 安装并接管页面前，需要从互联网获取页面的全部资源。
如果你的文档很稳定，或者你在托管博客，不太关心用户立即接收到最新版本，你可以将其设置为 "disabled"，这意味着新的 SW 将在后台完全静默安装并在安装后等待，当旧版本 SW 控制的页面全部关闭后，新 SW 将再下次访问接管并提供用户新内容。此设置可以避免用户在访中被弹窗打扰。
如果你希望通过 SW 来加速用户在弱网或无网条件下的访问，但同时希望用户时刻访问新内容，你可以将此选项设置为 "force"。这意味着检测到新 SW 后旧 SW 将会被立刻销毁并且页面会被刷新以确保用户浏览最新内容。最大的缺点就是致新 SW 发布后，用户在重新进入网站后的几秒内会遇到预期之外的突然刷新，并且他们将必须通过互联网访问文档并完全重新安装最新的 SW。
当检测到新内容 (检测到新的 SW) 时，更新提示弹窗将会出现；当新内容就绪时，更新就绪弹窗将会出现。
如果你对默认的弹窗不满意，你可以自行编写组件更换。从 @vuepress/plugin-pwa/client 中导入 PwaFoundPopup 或 PwaReadyPopup 并使用其 slot 来自定义弹窗内容，然后将组件路径传递给 foundComponent 或 readyComponent 选项。
<script setup lang="ts">
+import { PwaFoundPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaFoundPopup v-slot="{ found, refresh }">
+ <div v-if="found">
+ 已找到新内容
+ <button @click="refresh">刷新</button>
+ </div>
+ </PwaFoundPopup>
+</template>
+<script setup lang="ts">
+import { PwaReadyPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaReadyPopup v-slot="{ isReady, reload }">
+ <div v-if="isReady">
+ 新内容已就绪
+ <button @click="reload">应用</button>
+ </div>
+ </PwaReadyPopup>
+</template>
+插件还提供了其他 PWA 相关选项，比如微软磁贴图标与颜色设置，苹果图标等。 如果你是一个高级用户，你也可以设置 generateSwConfig 来配置 workbox-build。查看 插件选项 了解更多细节。
更多内容，请详见:
PWA 介绍
PWA 全称 Progressive Web app，即渐进式网络应用程序，标准由 W3C 规定。
它允许网站通过支持该特性的浏览器将网站作为 App 安装在对应平台上。
访问 https://developer.mozilla.org/zh-CN/docs/Web/Progressive_web_apps 查看详情。 ↩︎
Service Worker 简要介绍
Service Worker 会在注册过程中获取注册在其中的所有文件并缓存它们。
注册成功后，Service Worker 激活，并开始代理并控制你的全部请求。
每当你想要通过浏览器发起访问请求后，Service Worker 将会查看其是否存在与自身缓存列表中，若存在则直接返回缓存好的结果，否则调用自身的 fetch 方法进行获取。你可以通过自定义 fetch 方法，来完全控制网页内资源获取请求的结果，比如在离线时提供一个 fallback 的网页。
每次用户重新打开网站时，Service Worker 会向自身注册时的地址发出校验命令，如果检测到新版本的 Service Worker，则会更新自身，并开始缓存注册在新 Service Worker 中的资源列表。成功获取内容更新后，Service Worker 将会触发 update 事件。可以通过此事件提示用户，比如将在右下角显示一个弹出窗口，提示用户新内容可用并允许用户触发更新。
清单文件
清单文件使用 JSON 格式，负责声明 PWA 各项信息，如名称、描述、图标、快捷动作等。
为了使你的站点能够被注册为 PWA，你需要满足 manifest 基本的规范，才能使浏览器认为该网站为一个可安装的 PWA 并允许用户安装它。
提示
Manifest 的标准与规范，请详见 MDN 网络 App 清单 和 W3C Manifest
可安装性
想要让网站可以注册为 PWA，网站需要自行成功注册有效的 Service Worker，同时拥有合法的 manifest 清单文件并在网站中声明它。
清单文件应至少包含 name(或 short_name) icons start_url。
SSG: Static Site Generating，静态站点生成。 ↩︎
SEO: Search Engine Optimization，搜索引擎增强，
SPA: Single Page Application, 单页应用
大多只有主页，并使用 history mode 处理路由，而不是真的在页面之间导航。 ↩︎
此插件会为每个页面生成字数统计与预计阅读时间。
npm i -D @vuepress/plugin-reading-time@next
+import { readingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default {
+ plugins: [
+ readingTimePlugin({
+ // 配置项
+ }),
+ ],
+}
+插件会将相关信息注入到页面数据的 readingTime，其中：
readingTime.minutes：为预计阅读时间（分钟）numberreadingTime.words：字数统计，number对于任何页面，你可以从 page.data.readingTime 获取预计阅读时间与字数统计:
page.data.readingTime // { minutes: 3.2, words: 934 }
+你可以在 extendsPage 以及其他生命周期获取它做进一步处理:
export default {
+ // ...
+ extendsPage: (page) => {
+ page.data.readingTime // { minutes: 3.2, words: 934 }
+ },
+
+ onInitialized: (app) => {
+ app.pages.map((page) => {
+ page.data.readingTime // { minutes: 3.2, words: 934 }
+ })
+ },
+}
+你可以从 @vuepress/plugin-reading-time/client 导入 useReadingTimeData 和 useReadingTimeLocale 来获取当前页面的阅读时间数据和语言环境数据：
<script setup lang="ts">
+import {
+ useReadingTimeData,
+ useReadingTimeLocale,
+} from '@vuepress/plugin-reading-time/client'
+
+const readingTimeData = useReadingTimeData() // { minutes: 1.1, words: 100 }
+const readingTimeLocale = useReadingTimeLocale() // { time: "1 分钟", words: "100 字" }
+</script>
+number300类型：ReadingTimePluginLocaleConfig
interface ReadingTimePluginLocaleData {
+ /**
+ * 字数模板，模板中 `$word` 会被自动替换为字数
+ */
+ word: string
+
+ /**
+ * 小于一分钟文字
+ */
+ less1Minute: string
+
+ /**
+ * 时间模板
+ */
+ time: string
+}
+
+interface ReadingTimePluginLocaleConfig {
+ [localePath: string]: ReadingTimePluginLocaleData
+}
+必填：否
详情：
阅读时间插件的国际化配置。
你可以从 @vuepress/plugin-reading-time/client 导入并使用这些 API：
即使插件被禁用，这些 API 也不会抛出错误。
interface ReadingTime {
+ /** 分钟为单位的预计阅读时长 */
+ minutes: number
+ /** 内容的字数 */
+ words: number
+}
+
+const useReadingTimeData: () => ComputedRef<ReadingTime | null>
+当插件被禁用时会返回 null。
interface ReadingTimeLocale {
+ /** 当前语言的预计阅读时间 */
+ time: string
+ /** 当前语言的字数文字 */
+ words: string
+}
+
+const useReadingTimeLocale: () => ComputedRef<ReadingTimeLocale>
+由于此插件主要面向插件和主题开发者，所以提供了 "使用 API"：
import { useReadingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default (options) => (app) => {
+ useReadingTimePlugin(app, {
+ // 你的选项
+ })
+
+ return {
+ name: 'vuepress-plugin-xxx', // or vuepress-theme-xxx
+ }
+}
+为什么你应该使用 "使用 API"
当你多次注册一个插件时，vuepress 会给你一个警告，告诉你只有第一个插件会生效。useReadingTimePlugin 会自动检测插件是否已经注册，避免多次注册。
如果你在 extendsPage 生命周期访问阅读时间数据，那么 @vuepress/plugin-reading-time 必须在你的主题或插件之前被调用，否则你会得到未定义的 page.data.readingTime。useReadingTimePlugin 确保了 @vuepress/plugin-reading-time 在你的主题或插件之前被调用。
我们也提供了一个 removeReadingTimePlugin api 来移除插件。你可以使用它来确保你的调用生效或清除插件:
import { useReadingTimePlugin } from '@vuepress/plugin-reading-time'
+
+export default (options) => (app) => {
+ // 这会移除任何当前存在的阅读时间插件
+ removeReadingTimePlugin(app)
+
+ // 所以这会生效，即使之前已经注册了一个阅读时间插件
+ useReadingTimePlugin(app, {
+ // 你的选项
+ })
+
+ return {
+ name: 'vuepress-plugin-xxx', // or vuepress-theme-xxx
+ }
+}
+此插件提供页面与整站重定向功能。
npm i -D @vuepress/plugin-redirect@next
+import { redirectPlugin } from '@vuepress/plugin-redirect'
+
+export default {
+ plugins: [
+ redirectPlugin({
+ // 配置项
+ }),
+ ],
+}
+如果你改动了已有页面的地址，你可以在 Frontmatter 中使用 redirectFrom 选项设置重定向到此页面的地址，这样可以保证用户在访问旧链接时重定向到新的地址。
如果你需要将已有的页面重定向到新的页面，可以在 Frontmatter 中使用 redirectTo 选项设置需要重定向到的地址。这样该页面会在访问时重定向到新的地址。
你还可以通过插件选项中的 config 设置一个重定向映射，详见 config。
插件可以根据用户的语言首选项，自动将无多语言链接重定向到用户需要的多语言页面。为了实现这一点，你需要留空默认的语言目录 (/)，并在插件选项中设置 autoLocale: true。插件会自动根据用户语言跳转到对应的语言页面。
也就是你需要设置以下目录结构:
.
+├── en
+│ ├── ...
+│ ├── page.md
+│ └── README.md
+├── zh
+│ ├── ...
+│ ├── page.md
+│ └── README.md
+└── other_languages
+ ├── ...
+ ├── page.md
+ └── README.md
+并将主题选项的 locales 设置为:
export default {
+ locales: {
+ '/en/': {
+ lang: 'en-US',
+ // ...
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ // ...
+ },
+ // other languages
+ },
+ // ...
+}
+这样当用户访问 / 或 /page.html 时，他们会自动根据当前浏览器语言重定向到 /en/ /en/page.html 与 /zh/ /zh/page.html。
自定义回退行为
有些时候，用户可能会在系统设置中添加多个语言。默认情况下，在站点支持首选语言，但首选语言不存在相应页面时，插件会尝试匹配用户设置的备用语言。
如果不需要回退到用户备用语言，而直接匹配用户首选语言，请在插件选项中设置 localeFallback: false。
自定义缺失行为
有些时候，当用户访问一个页面时，文档尚未包含用户需要的语言版本 (一个普遍的情况是当前页面尚未完成相关语言的本地化)，这样插件需要做出默认行为，你可以通过插件选项中的 defaultBehavior 定制它:
"defaultLocale": 重定向到默认语言或首个可用语言页面 (默认行为)"homepage": 重定向到当前语言的主页 (仅在文档包含用户语言时可用)"404": 重定向到当前语言的 404 页 (仅在文档包含用户语言时可用)自定义默认路径
你可以通过设置插件选项中的 defaultLocale 来自定义默认路径。默认情况下，插件会使用 locales 中的第一个键名作为默认路径。
插件支持在多语言文档中，自动根据用户语言首选项，将链接切换到用户需要的多语言页面。为了实现这一点，你需要在插件选项中设置 switchLocale，它可以是以下两个值:
direct: 直接切换到用户语言首选项页面，而不询问modal: 在用户语言首选项与当前页面语言不同时，弹出一个对话框询问用户是否切换语言默认情况下，插件会从站点的多语言配置 locales 选项中，读取 语言路径 和 lang 生成多语言配置。有些时候，你可能希望多个语言命中同一个路径，这种情况下，你应该设置插件的 localeConfig 选项。
比如，你可能希望所有英文用户都匹配到 /en/，并将繁体中文用户匹配到 /zh/ 中，那么你可以设置:
redirect({
+ localeConfig: {
+ '/en/': ['en-US', 'en-UK', 'en'],
+ '/zh/': ['zh-CN', 'zh-TW', 'zh'],
+ },
+})
+有时你可能会更改 base 或为你的站点使用新域名，因此你可能希望原始站点自动重定向到新站点。
为了解决这个问题，插件提供了 vp-redirect 脚手架。
使用:
+ $ vp-redirect generate [源文件夹]
+
+Options:
+ --hostname <hostname> 重定向到的域名 (例如: https://new.example.com/) (默认: /)
+ -c, --config <config> 设置配置文件路径
+ -o, --output <output> 设置输出目录 (默认: .vuepress/redirect)
+ --cache <cache> 设置缓存文件的目录
+ -t, --temp <temp> 设置临时文件的目录
+ --clean-cache 生成前清理缓存文件
+ --clean-temp 生成前清理临时文件
+ -h, --help 显示此消息
+你需要传入 VuePress 项目源目录并设置 hostname 选项。重定向助手脚手架将初始化你的 VuePress 项目以获取页面，然后在输出目录生成重定向 html 文件。
默认情况下，插件将输出到源文件夹下的 .vuepress/redirect 目录。你应该将其上传到你的原始站点以提供重定向。
类型：Record<string, string> | ((app: App) => Record<string, string>)
详情
页面重定向映射。
可直接传入对象或传入参数为 App 的函数返回值一个对象。
每个键名必须是一个绝对路径，代表重定向的源页面地址。
每个键值是重定向的目标地址，可以是绝对路径或完整路径。
示例：
当 base 为 /base/时：
/base/foo.html 重定向到 /base/bar.html/base/baz.html 重定向到 https://example.com/qux.html。redirect({
+ config: {
+ '/foo.html': '/bar.html',
+ '/baz.html': 'https://example.com/qux.html',
+ },
+})
+将 post 文件夹的路径重定向到 posts 文件夹
redirect({
+ hostname: 'https://example.com',
+ config: (app) =>
+ Object.fromEntries(
+ app.pages
+ .filter(({ path }) => path.startsWith('/posts/'))
+ .map(({ path }) => [path.replace(/^\/posts\//, '/post/'), path]),
+ ),
+})
+booleanfalse类型："direct" | "modal" | false
默认值: false
详情：
是否根据用户偏好切换到新的语言环境。
"direct": 直接重定向到新的语言环境而不询问"modal": 显示一个模式让用户选择是否切换到新的语言环境Record<string, string | string[]>booleantrue"defaultLocale" | "homepage" | "404""defaultLocale"stringstring | string[]string你可以通过 CSS 变量来自定义重定向弹窗的样式：
:root {
+ --redirect-z-index: 1499;
+ --redirect-bg-color: #fff;
+ --redirect-bg-color-light: #f3f4f5;
+ --redirect-bg-color-lighter: #eeeeee;
+ --redirect-text-color: #2c3e50;
+ --redirect-primary-color: #3eaf7c;
+ --redirect-primary-hover-color: #4abf8a;
+ --redirect-primary-text-color: #fff;
+}
+根据组件文件或目录自动注册 Vue 组件。
npm i -D @vuepress/plugin-register-components@next
+import { registerComponentsPlugin } from '@vuepress/plugin-register-components'
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ // 配置项
+ }),
+ ],
+}
+类型： Record<string, string>
默认值： {}
详情：
一个定义了组件名称和其对应文件路径的对象。
键会被用作组件名称，值是组件文件的绝对路径。
如果该配置项中的组件名称和 componentsDir 配置项发生冲突，那么该配置项会有更高的优先级。
示例：
import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ components: {
+ FooBar: path.resolve(__dirname, './components/FooBar.vue'),
+ },
+ }),
+ ],
+}
+类型： string | null
默认值： null
详情：
组件目录的绝对路径。
该目录下匹配 componentsPatterns 的文件会被自动注册为 Vue 组件。
示例：
import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export default {
+ plugins: [
+ registerComponentsPlugin({
+ componentsDir: path.resolve(__dirname, './components'),
+ }),
+ ],
+}
+组件目录：
components
+├─ FooBar.vue
+└─ Baz.vue
+组件会像这样被注册：
import { defineAsyncComponent } from 'vue'
+
+app.component(
+ 'FooBar',
+ defineAsyncComponent(() => import('/path/to/components/FooBar.vue')),
+)
+
+app.component(
+ 'Baz',
+ defineAsyncComponent(() => import('/path/to/components/Baz.vue')),
+)
+类型： string[]
默认值： ['**/*.vue']
详情：
使用 globby 来匹配组件文件的 Patterns 。
该 Patterns 是相对于 componentsDir 目录的。
类型： (filename: string) => string
默认值： (filename) => path.trimExt(filename.replace(/\/|\\/g, '-'))
详情：
用于从文件名获取对应组件名称的函数。
它只会对 componentsDir 目录下匹配了 componentsPatterns 的文件生效。
注意，这里的 filename 是相对于 componentsPatterns 目录的文件路径。
此插件从你的 VuePress 站点中删除任何相关的 Service Worker，因此如果你在启用后任何 PWA 插件后移除它们，用户仍然可以获得更新。
如果你启用过 PWA，为什么需要这个插件？
PWA 插件，如 @vuepress/plugin-pwa 将 Service Worker 注册到你的站点，这将缓存你的站点并使其离线可用。
但是，如果你删除 PWA 插件，先前的 Service Worker 仍将在那里，但它们永远无法获得更新，因为他们永远无法找到要更新的新 Service Worker。 因此，用户将继续使用你网站的旧版本。
要解决这个问题：
一个新的内容为空的 Service Worker 需要生成在原位置。
新的 Service Worker 应该尝试删除旧 Service Worker 缓存的内容，然后它应该注销自己。
npm i -D @vuepress/plugin-remove-pwa@next
+import { removePwaPlugin } from '@vuepress/plugin-remove-pwa'
+
+export default {
+ plugins: [
+ removePwaPlugin({
+ // options
+ }),
+ ],
+}
+string'workbox'string'service-worker.js'此插件会在配置的语言上设置 rtl 方向。
npm i -D @vuepress/plugin-rtl@next
+import { rtlPlugin } from '@vuepress/plugin-rtl'
+
+export default {
+ plugins: [
+ rtlPlugin({
+ // 配置项
+ locales: ['/ar/'],
+ }),
+ ],
+}
+string[]['/']类型：SelectorOptions
interface SelectorOptions {
+ [element: string]: {
+ [attrs: string]: string
+ }
+}
+默认值：{ 'html': { dir: 'rtl' } }
详情：
开启 RTL 的选择器。
默认设置意味着在 RTL 多语言中，html 元素的 dir 属性将被设置为 rtl。
为你的文档网站提供本地搜索能力。
提示
当你正确配置该插件后，默认主题会把搜索框添加到导航栏。
该插件不一定能在其他主题中直接使用，因此你应参考主题本身的文档来获取更多信息。
npm i -D @vuepress/plugin-search@next
+import { searchPlugin } from '@vuepress/plugin-search'
+
+export default {
+ plugins: [
+ searchPlugin({
+ // 配置项
+ }),
+ ],
+}
+该插件会根据你的页面，在本地生成搜索索引，然后在用户访问站点时加载搜索索引文件。换句话说，这是一个轻量级的内置搜索能力，不会进行任何外部请求。
然而，当你的站点包含大量页面时，搜索索引文件也会变得非常大，它可能会拖慢你的页面加载速度。在这种情况下，我们建议你使用更成熟的解决方案 - docsearch 。
类型： Record<string, { placeholder: string }>
详情：
搜索框在不同 locales 下的文字。
如果没有指定该配置项，它会降级使用默认文字。
示例：
export default {
+ plugins: [
+ searchPlugin({
+ locales: {
+ '/': {
+ placeholder: 'Search',
+ },
+ '/zh/': {
+ placeholder: '搜索',
+ },
+ },
+ }),
+ ],
+}
+(string | HotKeyOptions)[]export interface HotKeyOptions {
+ /**
+ * Value of `event.key` to trigger the hot key
+ */
+ key: string;
+ /**
+ * Whether to press `event.altKey` at the same time
+ *
+ * @default false
+ */
+ alt?: boolean;
+ /**
+ * Whether to press `event.ctrlKey` at the same time
+ *
+ * @default false
+ */
+ ctrl?: boolean;
+ /**
+ * Whether to press `event.shiftKey` at the same time
+ *
+ * @default false
+ */
+ shift?: boolean;
+}
+默认值： ['s', '/']
详情：
指定热键的 event.key 。
当按下热键时，搜索框会被聚焦。
将该配置项设为空数组可以禁用热键功能。
类型： number
默认值： 5
详情：
指定搜索结果的最大条数。
类型： (page: Page) => boolean
默认值： () => true
详情：
一个函数，用于判断一个页面是否应该被包含在搜索索引中。
true 来包含该页面。false 来排除该页面。示例：
export default {
+ plugins: [
+ searchPlugin({
+ // 排除首页
+ isSearchable: (page) => page.path !== '/',
+ }),
+ ],
+}
+类型： (page: Page) => string[]
默认值： () => []
详情：
一个函数，用于在页面的搜索索引中添加额外字段。
默认情况下，该插件会将页面标题和小标题作为搜索索引。该配置项可以帮助你添加更多的可搜索字段。
示例：
export default {
+ plugins: [
+ searchPlugin({
+ // 允许搜索 Frontmatter 中的 `tags`
+ getExtraFields: (page) => page.frontmatter.tags ?? [],
+ }),
+ ],
+}
+你可以通过 CSS 变量来自定义搜索框的样式：
:root {
+ --search-bg-color: #ffffff;
+ --search-accent-color: #3eaf7c;
+ --search-text-color: #2c3e50;
+ --search-border-color: #eaecef;
+ --search-item-text-color: #5d81a5;
+ --search-item-focus-bg-color: #f3f4f5;
+ --search-input-width: 8rem;
+ --search-result-width: 20rem;
+}
+详情：
该插件会全局注册一个 <SearchBox /> 组件，你可以不传入任何 Props 来使用它。
将该组件放置在你想要显示搜索框的地方。例如，默认主题将这个组件放在了导航栏的末尾。
提示
该组件主要用于主题开发。在大多数情况下你不需要直接使用该组件。
类型：string
必填：是
详情：
部署域名
类型：Author
type AuthorName = string
+
+interface AuthorInfo {
+ /**
+ * 作者姓名
+ */
+ name: string
+
+ /**
+ * 作者网站
+ */
+ url?: string
+
+ /**
+ * 作者 Email
+ */
+ email?: string
+}
+
+type Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]
+详情：
默认作者
类型：boolean
默认值：true
详情：
是否自动生成描述
类型：string | ((page: Page) => string | null)
详情：
首选链接
类型：string
详情：
当找不到图片时的回退图片链接
类型：string
详情：
内容的年龄分级，格式为 [int]+，如 "13+"
类型：string
详情：
你的 twitter 用户名
类型：(page: Page) => boolean
详情：
你可以使用此选项判断一个页面是否是文章。
类型：
function ogp(
+ /** 插件推断的 OGP 信息 */
+ ogp: SeoContent,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+详情：
自定义 OGP 生成器
你可以使用此选项来注入新的或覆盖掉默认生成的 OGP 标签。
类型：
function jsonLd(
+ /** 由插件推断出的 JSON-LD 对象 */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+详情：
自定义 JSON-LD 生成器
你可以使用此选项来注入新的或覆盖掉默认生成的 JSON-LD 标签。
类型：
function customHead(
+ /** head 标签配置 */
+ head: HeadConfig[],
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+详情：
你可以使用此选项来直接注入任意格式的标签到 <head>。
本插件会通过向网站 <head> 注入标签，让你的网站完全支持 开放内容协议 OGP 和 JSON-LD 1.1，以全面增强站点的搜索引擎优化性。
插件开箱即用，在不做任何配置的情况下，会尽可能通过页面内容，提取对应的信息补全 OGP 与 JSON-LD 所需的必要标签。
默认情况下，插件会读取站点配置、主题配置与页面的 frontmatter 来尽可能自动生成。诸如站点名称，页面标题，页面类型，写作日期，最后更新日期，文章标签均会自动生成。
| 属性名称 | 值 |
|---|---|
og:url | options.hostname + path |
og:site_name | siteConfig.title |
og:title | page.title |
og:description | page.frontmatter.description || 自动生成 (当插件选项中的 autoDescription 为 true 时) |
og:type | "article" |
og:image | page.frontmatter.banner || page.frontmatter.cover || 页面的第一张图片|| 插件选项的 fallbackImage |
og:updated_time | page.git.updatedTime |
og:locale | page.lang |
og:locale:alternate | siteData.locales 包含的其他语言 |
twitter:card | "summary_large_image" (仅在找到图片时) |
twitter:image:alt | page.title (仅在找到图片时) |
article:author | page.frontmatter.author || options.author |
article:tag | page.frontmatter.tags || page.frontmatter.tag |
article:published_time | page.frontmatter.date || page.git.createdTime |
article:modified_time | page.git.updatedTime |
| 属性名 | 值 |
|---|---|
@context | "https://schema.org" |
@type | "NewsArticle" |
headline | page.title |
image | 页面中的图片|| options.hostname + page.frontmatter.image |
datePublished | page.frontmatter.date || page.git.createdTime |
dateModified | page.git.updatedTime |
author | page.frontmatter.author || options.author |
你可以在页面的 frontmatter 中配置 head 选项，自主添加特定标签到页面 <head> 以增强 SEO。
如:
---
+head:
+ - - meta
+ - name: keywords
+ content: SEO plugin
+---
+会自动注入 <meta name="keywords" content="SEO plugin" />。
本插件也支持你完全控制生成逻辑。
对于大多数页面，基本只有文章和网页两种类型，所以插件提供了 isArticle 选项让你提供辨别文章的逻辑。
选项接受一个 (page: Page) => boolean 格式的函数，默认情况下从 Markdown 文件生成的非主页页面都会被视为文章。
提示
如果某个网页的确符合图书、音乐之类的“冷门”类型，你可以通过设置下方三个选项处理它们。
你可以使用插件选项的 ogp 传入一个函数来按照你的需要修改默认 OGP 对象并返回。
function ogp(
+ /** 插件推断的 OGP 信息 */
+ ogp: SeoContent,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+详细的参数结构详见 配置。
比如你在使用某个第三方主题，并按照主题要求为每篇文章在 Front Matter 中设置了 banner，那你可以传入这样的 ogp:
seoPlugin({
+ ogp: (ogp, page) => ({
+ ...ogp,
+ 'og:image': page.frontmatter.banner || ogp['og:image'],
+ }),
+})
+同 OGP，你可以使用插件选项的 jsonLd 传入一个函数来按照你的需要修改默认 JSON-LD 对象并返回。
function jsonLd(
+ /** 由插件推断出的 JSON-LD 对象 */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+如果你将内容部署到不同的站点，或不同 URL 下的相同内容，你可能需要设置 canonical 选项为你的页面提供 “规范链接”。 你可以设置一个字符串，这样它会附加在页面路由链接之前，或者添加一个自定义函数 (page: Page) => string | null 返回规范链接。
例子
如果你的站点部署在 example.com 的 docs 文件夹下，但同时在下列网址中可用:
http://example.com/docs/xxxhttps://example.com/docs/xxxhttp://www.example.com/docs/xxxhttps://www.example.com/docs/xxx (首选)要让搜索引擎结果始终是首选，你可能需要将 canonical 设置为 https://www.example.com/docs/，以便搜索引擎知道首选第四个 URL 作为索引结果。
有些时候你可能需要符合其他协议或按照其他搜索引擎提供的格式提供对应的 SEO 标签，此时你可以使用 customHead 选项，其类型为:
function customHead(
+ /** head 标签配置 */
+ head: HeadConfig[],
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+你应该直接修改传入的 head 参数。
搜索引擎优化 (Search Engine Optimization)，是一种透过了解搜索引擎的运作规则来调整网站，以及提高目的网站在有关搜索引擎内排名的方式。由于不少研究发现，搜索引擎的用户往往只会留意搜索结果最前面的几个条目，所以不少网站都希望透过各种形式来影响搜索引擎的排序，让自己的网站可以有优秀的搜索排名。 所谓“针对搜索引擎作最优化的处理”，是指为了要让网站更容易被搜索引擎接受。搜索引擎会将网站彼此间的内容做一些相关性的资料比对，然后再由浏览器将这些内容以最快速且接近最完整的方式，呈现给搜索者。搜索引擎优化就是通过搜索引擎的规则进行优化，为用户打造更好的用户体验，最终的目的就是做好用户体验。
开放内容协议 OGP (Open Graph Protocal)
本插件完美支持该协议，会自动生成符合该协议的 <meta> 标签。
本插件会为文章类页面生成 NewsArticle 类标签。
RDFa 主要标记 HTML 结构。这是插件无法支持的内容， 使用了这一功能通过了谷歌的富媒体结构测试。你可以考虑搭配使用。
结构标记的 Schema 定义站点
你可以使用 Google 富媒体结构测试工具 测试本站点。
该插件使用 Shiki 来为 Markdown 代码块启用代码高亮。
提示
Shiki 是 VSCode 正在使用的代码高亮器。它具有更高的保真度，但可能会比 Prism.js 要慢一些，特别是在有大量代码块需要处理的时候。
你可以考虑在 dev 模式下禁用该插件来获取更好的开发体验。
npm i -D @vuepress/plugin-shiki@next
+import { shikiPlugin } from '@vuepress/plugin-shiki'
+
+export default {
+ plugins: [
+ shikiPlugin({
+ // 配置项
+ langs: ['ts', 'json', 'vue', 'md', 'bash', 'diff'],
+ }),
+ ],
+}
+类型： ShikiLang[]
详情：
Shiki 要解析的代码块的语言。
该配置项会被传递到 Shiki 的 getHighlighter() 方法中。
你最好明确传入所有你使用的语言列表，否则 Shiki 会加载所有语言，并可能影响性能。
参考：
类型： ShikiTheme
默认值： 'nord'
详情：
Shiki 的主题。
该配置项会被传递到 Shiki 的 codeToHtml() 方法中。
参考：
类型：Record<'dark' | 'light', ShikiTheme>
详情：
Shiki 的暗黑和明亮模式双主题。
该配置项会被传递到 Shiki 的 codeToHtml() 方法中。
参考：
类型：ShikiTransformer[]
详情：
Shiki 的转换器。
该配置项会被传递到 Shiki 的 codeToHtml() 方法中。
参考：
类型：string
必填：是
详情：
当前网站部署到的域名，插件需要此选项才能工作。
类型：string[]
详情：
需要额外包含的网址。
如果你有一些不包含在 VuePress 路由中的链接 (如: 存放在 public 文件夹下的页面或其他插件或工具直接生成的页面)，你可能需要设置此项。
示例：['/about.html', '/api/']
类型：string[]
默认值：['/404.html']
详情：
不需要收录的页面路径，请以绝对路径开头。
默认情况下 VuePress 自动生成的所有路径 (除 404 页) 都会被添加进 Sitemap。
类型：boolean
默认值：false
详情：
是否在开发服务器中启用
提示
由于性能原因，我们不提供热更新。重启开发服务器以同步你的变更。
类型：string
默认值："http://localhost:${port}"
详情：
开发服务器使用的主机名
类型：string
默认值："sitemap.xml"
详情：
输出的文件名，相对于输出目录。
类型：string
默认值："sitemap.xsl"
详情：
输出的 xsl 文件名，相对于输出目录。
类型：string
默认值："@vuepress-plugin/sitemap/templates/sitemap.xsl"
详情：
用作模板的 XSL 文件内容
类型："always" | "hourly" | "daily" | "weekly" | "monthly" | "yearly" | "never"
默认值："daily"
详情：
页面默认更新频率，会被 Frontmatter 中的 changefreq 选项覆盖。
类型：number
默认值：0.5
详情：
页面优先级，范围 0 至 1。
类型：(page: Page, app: App) => string
详情：
最后修改事件的获得器，需要返回一个 ISO 字符形式的时间，默认会自动通过 Git 插件生成。
类型：SitemapFrontmatterOptions | false
详情：
false 表示将页面排除在 sitemap 之外。
类型："always" | "hourly" | "daily" | "weekly" | "monthly" | "yearly" | "never"
默认值："daily"
详情：
页面默认更新频率。它会覆盖插件选项中的 changefreq 选项。
类型：number
默认值：0.5
详情：
页面优先级，范围 0 至 1。
本插件会为你的网站自动生成 Sitemap。为了使插件正常工作，你需要将部署的域名传递给插件的 hostname 选项。如果你想在开发服务器中预览，请配置 devServer 选项。
插件会自动根据页面的 Git 的时间戳生成页面的最后更新时间，同时会根据站点的多语言配置声明页面的其他语言版本替代地址。
默认情况下，所有除 404 页面以外的网站链接均会被添加进 Sitemap。
如果你希望在 VuePress 项目页面之外，添加其他页面链接到 Sitemap，请将它们变成数组传入插件的 extraUrls 选项。
如果你需要排除一些页面路径，你可以将它们变成数组传入到插件的 excludePaths 选项。你也可以在对应页面的 frontmatter 中，设置 sitemap 为 false。
你还可以通过插件的 sitemapFilename 选项控制输出的地址，此地址相对于输出目录，默认为 sitemap.xml。
页面默认的更新周期是 daily (每天)，如果你希望修改全部的页面周期，请在插件选项中设置 changefreq 。你也可以在页面的 frontmatter 中设置 sitemap.changefreq，页面具有更高的优先级。
合法的频率有:
"always""hourly""daily""weekly""monthly""yearly""never"你可以在插件中设置 priority 以提供一个默认值。同时你可以通过 frontmatter 中的 sitemap.priority 来为每个页面设置优先级。可接受的值为 0 到 1 的浮点数。
你可以通过插件的 modifyTimeGetter 来返回一个 ISO 字符串格式的时间，默认会通过 Git 插件生成。
以下是一个基于文件最后修改时间的例子。
// 基于文件最后修改时间
+({
+ modifyTimeGetter: (page, app) =>
+ fs.statSync(app.dir.source(page.filePathRelative)).mtime.toISOString();
+})
+网站地图 (Sitemap) 提供搜索引擎优化 (SEO):
网站地图通过使所有页面可被找到来增强搜索引擎优化的效果。
大部分搜索引擎只跟踪页面内有限数量的链接，因此当网站非常大的时候，网站地图对于使搜索引擎和访问者可以访问网站中的所有内容就变得必不可少了。
Sitemaps 是站点管理员向搜索引擎爬虫公布站点可被抓取页面的协议，sitemap 文件内容必须遵循 XML 格式的定义。每个 URL 可以包含更新的周期和时间、URL 在整个站点中的优先级。这样可以让搜索引擎更佳有效的抓取网站内容。
同步配置 robots.txt
由于 Sitemap 面向搜索引擎，配合此插件使用时，你最好保证你在 .vuepress/public 文件夹下放置了有效的 robots.txt，以允许搜索引擎收录。一个最简单的 robots.txt 如下 (允许所有搜索引擎访问所有路径)
User-agent: *
+
+Allow: /
+为你的主题提供客户端数据，包含 VuePress 的 多语言支持 。
该插件主要用于开发主题，并且已经集成到默认主题中。大部分情况下你不需要直接使用它。
对于主题作者，该插件可以提供与 VuePress 及默认主题相同的多语言支持机制。但是如果你的主题不需要提供多语言支持，或者你想用你自己的方式来实现多语言支持，那么你不需要使用该插件。
npm i -D @vuepress/plugin-theme-data@next
+import { themeDataPlugin } from '@vuepress/plugin-theme-data'
+
+export default {
+ plugins: [
+ themeDataPlugin({
+ // 配置项
+ }),
+ ],
+}
+类型： ThemeData
默认值： {}
详情：
你希望在 Client 端中使用的主题数据对象。
你可以通过该配置项，在 Node 端提供主题数据，然后在客户端通过 useThemeData 和 useThemeLocaleData 来使用主题数据。
示例：
export default {
+ plugins: [
+ themeDataPlugin({
+ themeData: {
+ foo: 'foo',
+ locales: {
+ '/zh/': {
+ foo: 'zh-foo',
+ },
+ },
+ },
+ }),
+ ],
+}
+注意
主题数据对象在传递到客户端之前，会使用 JSON.stringify() 进行处理，因此你需要保证你提供的是一个可以被 JSON 序列化的对象。
详情：
返回主题数据的 Ref 对象。
数据是通过 themeData 配置项提供的。
示例：
import { useThemeData } from '@vuepress/plugin-theme-data/client'
+import type { ThemeData } from '@vuepress/plugin-theme-data/client'
+
+type MyThemeData = ThemeData<{
+ foo: string
+}>
+
+export default {
+ setup() {
+ const themeData = useThemeData<MyThemeData>()
+ console.log(themeData.value)
+ },
+}
+详情：
返回当前 locale 下主题数据的 Ref 对象。
当前 locale 中的字段已被合并到顶层字段中。
示例：
import { useThemeLocaleData } from '@vuepress/plugin-theme-data/client'
+import type { ThemeData } from '@vuepress/plugin-theme-data/client'
+
+type MyThemeData = ThemeData<{
+ foo: string
+}>
+
+export default {
+ setup() {
+ const themeLocaleData = useThemeLocaleData<MyThemeData>()
+ console.log(themeLocaleData.value)
+ },
+}
+该插件会提供一个目录 (table-of-contents, TOC) 组件。
npm i -D @vuepress/plugin-toc@next
+import { tocPlugin } from '@vuepress/plugin-toc'
+
+export default {
+ plugins: [
+ tocPlugin({
+ // 配置项
+ }),
+ ],
+}
+与 Markdown 目录语法 类似，该插件提供的目录组件可以直接在你的 Markdown 内容中使用：
<!-- Markdown 目录语法 -->
+
+[[toc]]
+
+<!-- Vue 目录组件 -->
+<Toc />
+在 Build 模式中，它们都可以被正确地预渲染。然而，它们之间存在一些区别。
Markdown 语法 [[toc]] 仅能在 Markdown 文件中使用。它是由 markdown-it 解析的，生成的目录是静态内容。
组件 <Toc/> 既可以用在 Markdown 文件中，也可以用在 Vue 文件中。它是由 Vue 加载的，生成的目录是一个 Vue 组件。
该插件可以和 @vuepress/plugin-active-header-links 协同工作，你只需要将 headerLinkSelector 与该插件的 linkClass 匹配即可。当页面滚动至某个标题锚点后，对应的链接就会被加上 linkActiveClass 类名。
因此，该插件对于主题开发者来说更为有用。
类型： string
默认值： 'Toc'
详情：
指定目录组件的名称。
类型： Partial<TocPropsOptions>
默认值： {}
详情：
覆盖组件 options Prop 的默认值。
目录组件可以通过 Props 来进行自定义。
<template>
+ <Toc :headers="headers" :options="options" />
+</template>
+PageHeader[]interface PageHeader {
+ level: number
+ title: string
+ slug: string
+ children: PageHeader[]
+}
+详情：
指定要渲染的标题数组。
如果该 Prop 没有被设置，默认会使用当前页面的标题。
Partial<TocPropsOptions>interface TocPropsOptions {
+ containerTag: string
+ containerClass: string
+ listClass: string
+ itemClass: string
+ linkTag: 'a' | 'RouterLink' | 'RouteLink'
+ linkClass: string
+ linkActiveClass: string
+ linkChildrenActiveClass: string
+}
+默认值：
下列默认值可以用过 defaultPropsOptions 来覆盖：
const defaultOptions = {
+ containerTag: 'nav',
+ containerClass: 'vuepress-toc',
+ listClass: 'vuepress-toc-list',
+ itemClass: 'vuepress-toc-item',
+ linkTag: 'RouteLink',
+ linkClass: 'vuepress-toc-link',
+ linkActiveClass: 'active',
+ linkChildrenActiveClass: 'active',
+}
+详情：
自定义目录组件。
如果 containerTag 设置为空字符串 '' ，那么最外层的 <nav> Container 会被完全移除。
示例：
使用默认 options 的目录组件的渲染结果类似以下结构：
<template>
+ <!-- container -->
+ <nav class="vuepress-toc">
+ <!-- list -->
+ <ul class="vuepress-toc-list">
+ <!-- item -->
+ <li class="vuepress-toc-item">
+ <!-- link -->
+ <RouteLink class="vuepress-toc-link" to="#foo">Foo</RouteLink>
+ </li>
+ <!-- item with children -->
+ <li class="vuepress-toc-item">
+ <!-- link (children active) -->
+ <RouteLink class="vuepress-toc-link active" to="#bar">Bar</RouteLink>
+ <!-- list (children) -->
+ <ul class="vuepress-toc-list">
+ <!-- item -->
+ <li class="vuepress-toc-item">
+ <!-- link (active) -->
+ <RouteLink class="vuepress-toc-link active" to="#bar-child">
+ Bar Child
+ </RouteLink>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </nav>
+</template>
+类型: (page: Page) => Record<string, unknown>
必填: 否
+参考:
+ +详情：
+获取文章信息的函数。
+获取到的信息会被稍后注入至路由元数据，以便你可以在客户端中通过组合式 API 获取。
+类型: (page: Page) => boolean
默认值: (page) => Boolean(page.filePathRelative) && !page.frontmatter.home
参考:
+ +详情：
+页面过滤器，此函数用于鉴别页面是否作为文章。
+默认情况下，所有从 Markdown 源文件中生成的非主页页面，会被作为文章。
+类型: BlogCategoryOptions[]
必填: 否
+详情：
+ +详情：
+博客分类配置，详见 博客分类配置。
+类型: BlogTypeOptions[]
必填: 否
+参考：
+ +详情：
+博客分类配置，详见 博客类型配置。
+(name: string) => string(name) => name.replace(/ _/g, '-').replace(/[:?*|\\/<>]/g, "").toLowerCase()booleantruestring<!-- more -->类型: number
默认值: 300
参考：
+详情：
+自动生成的摘要的长度。
+提示
+摘要的长度会尽可能的接近这个值。如果设置为 0，意味着不自动生成摘要。
类型: (page: Page) => boolean
默认值: filter 选项
参考：
+详情： +页面过滤器，此函数用于鉴别插件是否需要生成摘要。
+提示
+你可以使用此函数来跳过你不需要生成摘要的页面。例如：如果用户在 frontmatter 中设置了 excerpt 或 description，你可能希望直接使用它们。
类型: (tagName: string) => boolean
默认值: () => false
参考：
+详情： +被认为是自定义元素的标签。
+用于判断一个标签是否是自定义元素，因为在摘要中，所有的未知标签都会被移除。
+类型: string
默认值: "_blog"
详情： +注入文章信息至路由元数据时使用的键名。
+提示
+设置为空字符串会直接注入路由元数据 (而不是一个键下)。
+类型: boolean
默认值: 是否使用 --debug 标记
详情： +是否在开发服务器中启用实时热重载。
+致主题开发者
+默认情况下它是禁用的，因为它确实会对具有很多分类和类别的站点产生性能影响，并且在编辑 Markdown 时会减慢热重载的速度。
+如果用户正在添加或组织类别或标签，你可以告诉他们启用此功能，其余的时间最好禁用它。
+此外，你可以尝试检测用户项目中的页面数并决定是否启用它。
+博客分类配置应为一个数组，每一项控制一个分类规则。
+interface BlogCategoryOptions {
+ /**
+ * 唯一的分类名称
+ */
+ key: string
+
+ /**
+ * 从页面中获取分类的函数
+ */
+ getter: (page: Page) => string[]
+
+ /**
+ * 页面排序器
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * 待注册的页面路径图案
+ *
+ * @description `:key` 将会被替换为原 key 的 slugify 结果
+ *
+ * @default `/:key/`
+ */
+ path?: string | false
+
+ /**
+ * 页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Front Matter 配置
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+
+ /**
+ * 待注册的项目页面路径图案或自定义函数
+ *
+ * @description 当填入字符串的时候, `:key` 和 `:name` 会被自动替换为原始的 key、name 的 slugify 结果。
+ *
+ * @default `/:key/:name/`
+ */
+ itemPath?: string | ((name: string) => string) | false
+
+ /**
+ * 项目页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ itemLayout?: string
+
+ /**
+ * 项目 Front Matter 配置
+ */
+ itemFrontmatter?: (name: string, localePath: string) => Record<string, string>
+}
+博客类型配置应为一个数组，每一项控制一个类型规则。
+interface BlogTypeOptions {
+ /**
+ * 唯一的类型名称
+ */
+ key: string
+
+ /**
+ * 一个过滤函数来决定页面是否满足此类型
+ */
+ filter: (page: Page) => boolean
+
+ /**
+ * 页面排序器
+ */
+ sorter?: (pageA: Page, pageB: Page) => number
+
+ /**
+ * 待注册的页面路径
+ *
+ * @default '/:key/'
+ */
+ path?: string | false
+
+ /**
+ * 页面布局组件名称
+ *
+ * @default 'Layout'
+ */
+ layout?: string
+
+ /**
+ * Front Matter 配置
+ */
+ frontmatter?: (localePath: string) => Record<string, string>
+}
+你可以从 @vuepress/plugin-blog/client 导入下列 API:
博客分类
+const useBlogCategory: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogCategoryData<T>>
+参数 key 为需要获取的键名。如果未传入 key，会尝试使用与当前路径匹配的 key。
博客类型
+const useBlogType: <
+ T extends Record<string, unknown> = Record<string, unknown>,
+>(
+ key?: string,
+) => ComputedRef<BlogTypeData<T>>
+参数 key 为需要获取的键名。如果未传入 key，会尝试使用与当前路径匹配的 key。
详细的返回值如下:
+interface Article<T extends Record<string, unknown> = Record<string, unknown>> {
+ /** 文章路径 */
+ path: string
+ /** 文章信息 */
+ info: T
+}
+
+interface BlogCategoryData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** 分类路径 */
+ path: string
+
+ /**
+ * 仅当当前路径和某个子项目匹配时可用
+ */
+ currentItems?: Article<T>[]
+
+ /** 分类映射 */
+ map: {
+ /** 当前分类下全局唯一的 key */
+ [key: string]: {
+ /** 对应键值的分类路径 */
+ path: string
+ /** 对应键值的项目 */
+ items: Article<T>[]
+ }
+ }
+}
+
+interface BlogTypeData<
+ T extends Record<string, unknown> = Record<string, unknown>,
+> {
+ /** 类别路径 */
+ path: string
+
+ /** 当前类别下的项目 */
+ items: Article<T>[]
+}
+@vuepress/plugin-blog，你可以轻松地将博客功能引入主题。
+起步时，插件会首选过滤并选择那些需要作为文章的页面。这将剔除你不想要的页面，并在后续处理中排除它们。
+默认情况下，所有从 Markdown 文件生成但不是主页的页面，都将被视作文章。
+你可能需要设置 filter 选项来完全自定义要收集的页面。 filter 接受一个形状为 (page: Page) => boolean 的函数。
接着，你应该设置 getInfo 选项为一个接受 Page 作为参数并返回包含所需信息的对象的函数。这样稍后，你可以从组合 API 中获取这些信息。
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ filter: ({ filePathRelative, frontmatter }) => {
+ // 舍弃那些不是从 Markdown 文件生成的页面
+ if (!filePathRelative) return false
+
+ // 舍弃 `archives` 文件夹的页面
+ if (filePathRelative.startsWith('archives/')) return false
+
+ // 舍弃那些没有使用默认布局的页面
+ if (frontmatter.home || frontmatter.layout) return false
+
+ return true
+ },
+
+ getInfo: ({ frontmatter, git = {}, data = {} }) => {
+ // 获取页面信息
+ const info: Record<string, any> = {
+ author: frontmatter.author || '',
+ categories: frontmatter.categories || [],
+ date: frontmatter.date || git.createdTime || null,
+ tags: frontmatter.tags || [],
+ excerpt: data.excerpt || '',
+ }
+
+ return info
+ },
+ }),
+ // 其他插件 ...
+ ],
+}
+基本上，你的博客中需要两种“类型”:
+类别:
+“类别”是用文章的标签 (或类别) 对它们进行分组。
+例如，每篇文章可能都有对应的“分类”和“标签”。
+类型:
+“类型”是过滤不同条件的文章。
+例如，你的帖子中可能有日记或笔记。当帖子带有写作日期信息时，它可以称为“时间线项目”。
+了解这两种类型的描述后，你可以设置 category 和 type 选项，它们都接受一个数组，每个元素代表一个配置。
让我们从此处 2 个例子开始。
+假设你想为每篇文章设置标签，并且你正在通过 frontmatter.tag 设置它们。同时，你想要在 /tag/ 中使用 TagMap 布局的标签页面，并在/tag/标签名称 中使用 TagList 布局对标签按名称进行分组，你可能需要这样的配置:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // 其他配置 ...
+ category: [
+ {
+ key: 'tag',
+ getter: ({ frontmatter }) => frontmatter.tag || [],
+ path: '/tag/',
+ layout: 'TagMap',
+ frontmatter: () => ({ title: '标签页' }),
+ itemPath: '/tag/:name/',
+ itemLayout: 'TagList',
+ itemFrontmatter: (name) => ({ title: `${name}标签` }),
+ },
+ ],
+ }),
+ // 其他插件 ...
+ ],
+}
+此外，你可能希望为你的一些文章加注星标，并将其展示给访问者。当你在 frontmatter 中设置 star: true 来标记它们时，你可能需要这样的配置来在 /star/ 路径中以 StarList 布局显示它们:
import { blogPlugin } from '@vuepress/plugin-blog'
+
+export default {
+ name: 'vuepress-theme-xxx',
+ plugins: [
+ blogPlugin({
+ // 其他配置 ...
+ type: [
+ {
+ key: 'star',
+ filter: ({ frontmatter }) => frontmatter.star,
+ path: '/star/',
+ layout: 'StarList',
+ frontmatter: () => ({ title: '星标文章' }),
+ },
+ ],
+ }),
+ // 其他插件 ...
+ ],
+}
+看，设置这两种类型很容易。有关完整选项，请参阅 博客分类配置 和 博客分类配置。
+当生成每个页面时，插件将在 frontmatter.blog 中设置如下信息
interface BlogFrontmatterOptions {
+ /** 当前页面的类型 */
+ type: 'category' | 'type'
+ /** 在当前分类或类别下全局唯一的 key */
+ key: string
+ /**
+ * 当前的分类名称
+ *
+ * @description 仅在分类子项目页面中可用
+ */
+ name?: string
+}
+所以你可以直接调用 useBlogCategory() 和 useBlogType()，结果将是当前路由绑定的类别或类型。
此外，你可以通过传递所需的 key 作为参数，来将获得绑定到该 key 的信息。
对于上方的 Node 配置而言，你可以在客户端通过如下方式获取 tag 和 star 的信息:
+TagMap 布局:
<template>
+ <div>
+ <h1>Tag page</h1>
+ <ul>
+ <li v-for="({ items, path }, name) in categoryMap.map">
+ <RouteLink :key="name" :to="path" class="category">
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </li>
+ </ul>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+TagList 布局:
<template>
+ <div>
+ <h1>Tag page</h1>
+ <div class="category-wrapper">
+ <RouteLink
+ v-for="({ items, path }, name) in categoryMap.map"
+ :key="name"
+ :to="path"
+ class="category"
+ >
+ {{ name }}
+ <span class="category-num">
+ {{ items.length }}
+ </span>
+ </RouteLink>
+ </div>
+ <div class="article-wrapper" v-if="categoryMap.currentItems">
+ <div v-if="!categoryMap.currentItems.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in categoryMap.currentItems"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline
+ ? `${new Date(info.date).toLocaleDateString()}: `
+ : '') + info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author"
+ >Author: {{ info.author }}</span
+ >
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag"
+ >Tag: {{ info.tag.join(', ') }}</span
+ >
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogCategory } from '@vuepress/plugin-blog'
+import { RouteLink } from 'vuepress/client'
+
+const categoryMap = useBlogCategory('tag')
+</script>
+StarList 布局:
<template>
+ <div class="article-wrapper" v-if="stars.items">
+ <div v-if="!stars.items.length">Nothing in here.</div>
+ <article
+ v-for="{ info, path } in stars.items"
+ class="article"
+ @click="$router.push(path)"
+ >
+ <header class="title">
+ {{
+ (isTimeline ? `${new Date(info.date).toLocaleDateString()}: ` : '') +
+ info.title
+ }}
+ </header>
+ <hr />
+ <div class="article-info">
+ <span v-if="info.author" class="author">Author: {{ info.author }}</span>
+ <span v-if="info.date && !isTimeline" class="date"
+ >Date: {{ new Date(info.date).toLocaleDateString() }}</span
+ >
+ <span v-if="info.category" class="category"
+ >Category: {{ info.category.join(', ') }}</span
+ >
+ <span v-if="info.tag" class="tag">Tag: {{ info.tag.join(', ') }}</span>
+ </div>
+ <div v-if="info.excerpt" class="excerpt" v-html="info.excerpt" />
+ </article>
+ </div>
+</template>
+<script setup lang="ts">
+import { useBlogType } from '@vuepress/plugin-blog/client'
+
+import ArticleList from '../components/ArticleList.vue'
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+
+const stars = useBlogType('star')
+</script>
+有关返回类型，请参阅 Composition API 返回类型。
+该插件添加了原生多语言支持，因此你的设置将自动应用于每种语言。
+例如，如果用户进行了以下 locales 配置，并且你正在设置上面的“star”示例:
+export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+}
+那么 /zh/star/ 和 /star/ 都将可用，并且只会显示对应语言下的文章。
这个插件提供了一个内置的摘要生成器，可以通过将 excerpt 选项设置为 true 来启用。
摘要介绍
+摘要是一个 HTML 片段，被用于在博客列表中显示文章的简短描述，所以摘要有如下限制:
+isCustomElement 选项。.vuepress/public 的绝对路径或完整路径以确保它们可以在其他地址被访问。摘要生成器将尝试从 Frontmatter 内容中找到有效的摘要分隔符，如果找到，它将使用分隔符之前的内容，分隔符默认为 <!-- more -->，并且你可以通过 excerptSeparator 选项来自定义它。
如果找不到有效的分隔符，它将从 Markdown 文件的开头开始解析内容，直到长度达到预设值时停止。该值默认为 300，你可以通过设置 excerptLength 选项来自定义它。
要选择哪个页面应该生成摘要，你可以使用 excerptFilter 选项。
示例
+通常，如果用户设置了 frontmatter.description，你可能希望使用它们，因此如果 frontmatter.description 不为空，你可以让过滤器函数返回 false。
你既可以在 Node.js 一侧使用插件选项设置选项，也可以通过客户端配置文件在浏览器一侧设置选项。
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+// .vuepress/config.ts
+export default {
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk', // Artalk | Giscus | Waline | Twikoo
+
+ // 在这里放置其他选项
+ // ...
+ }),
+ ],
+}
+import { defineClientConfig } from 'vuepress/client'
+import {
+ defineArtalkConfig,
+ // defineGiscusConfig,
+ // defineTwikooConfig,
+ // defineWalineConfig,
+} from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+有以下你需要注意的限制：
+provider、多语言设置和其他资源相关选项必须在插件选项中设置。
为确保 tree-shaking 有效，我们必须在 Node 一侧优化入口，以便打包器可以了解最终打包中应包含哪些资源。
+这些选项将在配置参考中用
+不能序列化为 JSON 的选项必须在客户端配置中设置。
+接收复杂值的选项（例如：函数）不能在插件选项中设置，因为插件运行在 Node.js 环境下，所以我们无法将这些值和它们的上下文传递给浏览器。
+这些选项将在配置参考中用
+该插件全局注册了一个组件 <CommentService />。
alias 和布局槽来插入组件。 我们建议你在 <PageNav /> 组件之后插入评论组件 (<CommentService />)，本页可作为一个 Demo 作为参考。默认情况下，<CommentService /> 组件是全局启用的，你可以在插件选项和页面 frontmatter 中使用 comment 选项来控制它。
comment: false 在本地禁用它。comment 设置为 false。 然后你可以在页面 frontmatter 中设置 comment: true 以在局部启用它。你可以在页面 frontmatter 中设置 commentID 选项来自定义评论 ID，该 ID 用于标识要用于页面的评论存储项。默认情况下，它将是页面的 path ，这意味着如果你将站点部署到多个位置，站点间具有相同内容的页面将共享相同的评论数据。
目前你可以选择 Giscus、Waline、Artalk 和 Twikoo。
+推荐的评论服务
+"Artalk" | "Giscus" | "Twikoo" | "Waline" | "None""None"booleantruechannel 插件选项用于配置 feed 的频道。
+stringSiteConfig.title频道的标题
+stringoptions.hostname 和 context.base 生成)频道地址
+stringSiteConfig.description频道描述信息
+stringsiteConfig.locales['/'].locales"en-US"频道使用的语言
+stringauthor.name 生成 Copyright by $author频道版权信息
+string (需是合法的 Date ISOString)频道内容的发布时间
+string (需是合法的 Date ISOString)频道内容的上次更新时间
+number内容有效时间，即获取后保持缓存而不进行新获取的时间
+string这是一个会在频道中使用的图片，建议设置正方形图片、尺寸最好不小于 512×512。
+string一个代表频道的图标，建议设置正方形图片、尺寸最好不小于 128×128，背景色透明。
+FeedAuthor频道的作者。
+interface FeedAuthor {
+ /** 作者姓名 */
+ name: string
+ /** 作者电子邮箱 */
+ email?: string
+ /** 作者网站 */
+ url?: string
+ /**
+ * 作者头像地址
+ *
+ * 正方形，最好不小于 128×128，透明背景
+ */
+ avatar?: string
+}
+stringWebsub 的链接。Websub 需要服务器后端，与 VuePress 主旨不符，如无特殊需要忽略即可。
+WebSub
+有关信息，详见 Websub。
+string部署网站的域名。
+booleanfalse是否启用 Atom 格式输出。
+booleanfalse是否启用 JSON 格式输出。
+booleanfalse是否启用 RSS 格式输出。
+string一个大的图片，用作 feed 展示。
+string一个小的图标，显示在订阅列表中。
+number100设置 feed 的最大项目数量。在所有页面排序好后，插件会截取前 count 个项目。
+如果你的站点文章很多，你应该考虑设置这个选项以减少 feed 文件大小。
+(RegExp | string)[] | (tagName：string) => boolean应在 Feed 中保留的自定义元素或组件。
+默认情况下，所有未知标签均会被移除。
+类型：(page: Page)=> boolean
默认值：
+;({ frontmatter, filePathRelative }: Page): boolean =>
+ !(
+ frontmatter.home ||
+ !filePathRelative ||
+ frontmatter.article === false ||
+ frontmatter.feed === false
+ )
+自定义的过滤函数，用于过滤哪些项目在 feed 中显示。
+类型： (pageA: Page, pageB: Page)=> number
默认值：
+// dateSorter 来源于 @vuepress/helper
+;(pageA, pageB): number =>
+ dateSorter(
+ pageA.data.git?.createdTime
+ ? new Date(pageA.data.git?.createdTime)
+ : pageA.frontmatter.date,
+ pageB.data.git?.createdTime
+ ? new Date(pageB.data.git?.createdTime)
+ : pageB.frontmatter.date,
+ )
+Feed 项目的排序器。
+默认的排序行为是通过 Git 的文件添加日期 (需要 @vuepress/plugin-git)。
提示
+你应该启用 @vuepress/plugin-git 来获取最新创建的页面作为 feed 项目。否则，feed 项目将按照 VuePress 中页面的默认顺序排序。
channel 选项用于配置 Feed 频道。
可用选项详见 配置 → 频道设置
+booleanfalse是否在开发服务器中启用
+提示
+由于性能原因，我们不提供热更新。重启开发服务器以同步你的变更。
+string"http://localhost:${port}"开发服务器使用的主机名
+string"atom.xml"Atom 格式输出路径，相对于输出路径。
+string@vuepress/plugin-feed/templates/atom.xsl 的内容Atom xsl 模板文件没人陪美国
+string"atom.xsl"Atom xsl 输出路径，相对于输出路径。
+string"feed.json"JSON 格式输出路径，相对于输出路径。
+string"rss.xml"RSS 格式输出路径，相对于输出路径。
+string@vuepress/plugin-feed/templates/rss.xsl 的内容RSS xsl 模板文件内容。
+string"rss.xsl"RSS xsl 输出路径，相对于输出路径。
+Feed 生成控制器，详见 Feed 生成器。
+此插件内置了生成器，只有当你想完全控制 feed 生成时才需要设置此选项。
+Record<string, BaseFeedOptions>你可以将它用于每个语言环境的特定选项。
+除 hostname 外，上述任何选项均受支持。
默认情况下，所有文章均会被添加至 feed 流。如果你想在 feed 中移除特定页面，你可以在 frontmatter 中设置 feed: false。
string由 VuePress 自动生成，默认为页面的 h1 内容
+string页面描述
+Date页面的发布日期
+boolean该页面是否是文章
+++如果此项设置为
+false，则该页不会包含在最终的 feed 中。
string页面版权信息
+string页面的封面/分享图，需为完整链接或绝对链接。
+stringFeed 项目的标题
+stringFeed 项目的描述
+stringFeed 项目的内容
+FeedAuthor[] | FeedAuthorFeed 项目的作者
+interface FeedAuthor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+FeedContributor[] | FeedContributorFeed 项目的贡献者
+interface FeedContributor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+stringFeed 项目的标识符，用于标识 Feed 项目。
+你应该确保每个 Feed 项目有全局唯一的 guid。
+getter 来完全控制 Feed 项目的生成。
+(page: Page) => string项目标题获取器
+(page: Page) => string项目链接获取器
+(page: Page) => string | undefined项目描述获取器
+提示
+因为 Atom 在摘要中支持 HTML，所以如果可能的话，你可以在这里返回 HTML 内容，但内容必须以标记 html: 开头。
(page: Page) => string项目内容获取器
+(page: Page) => FeedAuthor[]项目作者获取器。
+获取器应在作者信息缺失时返回空数组。
+interface FeedAuthor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => FeedCategory[] | undefined项目分类获取器。
+interface FeedCategory {
+ /**
+ * 分类名称
+ */
+ name: string
+
+ /**
+ * 标识分类法的字符串
+ *
+ * @description rss format only
+ */
+ domain?: string
+
+ /**
+ * URI 标识的分类 scheme
+ *
+ * @description atom format only
+ */
+ scheme?: string
+}
+(page: Page) => FeedEnclosure | undefined项目附件获取器。
+interface FeedEnclosure {
+ /**
+ * Enclosure 地址
+ */
+ url: string
+
+ /**
+ * 类型
+ *
+ * @description 应为一个标准的 MIME 类型，rss format only
+ */
+ type: string
+
+ /**
+ * 按照字节数计算的大小
+ *
+ * @description rss format only
+ */
+ length?: number
+}
+(page: Page) => Date | undefined项目发布日期获取器
+(page: Page) => Date项目最后更新日期获取器
+(page: Page) => string项目图片获取器
+确保返回一个完整的 URL。
+(page: Page) => FeedContributor[]项目贡献者获取器
+获取器应在贡献者信息缺失时返回空数组。
+interface FeedContributor {
+ /**
+ * 作者名字
+ */
+ name?: string
+
+ /**
+ * 作者邮件
+ */
+ email?: string
+
+ /**
+ * 作者网站
+ *
+ * @description json format only
+ */
+ url?: string
+
+ /**
+ * 作者头像
+ *
+ * @description json format only
+ */
+ avatar?: string
+}
+(page: Page) => string | undefined项目版权获取器
+]]>插件可为你生成以下三种格式的 feed 文件:
+请按照需要生成的格式，在插件选项中设置 atom, json 或 rss 为 true。
为了正确生成 Feed 链接，你需要在插件选项中设置 hostname。
当你在浏览器中打开 Feed 文件时，我们会通过 xsl 模板将 atom 和 rss feed xml 魔法般地转换为可读的 html。你可以查看本站的 atom 和 rss feed 作为案例！
+如果你想在开发服务器中预览 Feed，你需要在插件选项中设置 devServer: true。如果你没有使用默认的 http://localhost:{port}，你还需要设置 devHostname。
你可以通过设置 channel 选项来自自定义 Feed 频道的各项信息。
我们推荐进行如下设置:
+channel.pubDate 中channel.ttl 中设置内容的更新周期(单位: 分钟)channel.copyright 设置版权信息channel.author 设置频道作者。详细的选项及其默认值详见 配置 → 频道设置
+默认情况下，所有文章均会被添加至 feed 流。
+你可以在 frontmatter 中配置 feed 和其他选项控制每个页面的 Feed 项目内容，详见 Frontmatter 选项 了解它们如何被转换。
你可以通过配置插件选项中的 getter 完全控制 Feed 项目的生成逻辑。 详细的选项及其默认值详见 配置 → Feed 获取器
插件会针对每个语言生成单独的 Feed。
+你可以通过插件选项中的 locales 分别对不同语言提供不同的默认设置。
类型：boolean
默认值：false
详情：
+是否在 Service Worker 首次成功注册时显示 PWA 安装按钮
+类型：ManifestOption
详情：
+填充一个将被解析为 manifest.webmanifest 的对象。
+提示
+如果未设置某些选项，它们会回退到插件预设值。
+siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.title || siteConfig.locales['/'].title || "Site"siteConfig.description || siteConfig.locales['/'].description || "A site built with vuepress"siteConfig.locales['/'].lang || "en-US"context.basecontext.base"standalone""#46bd87""#ffffff""portrait-primary"false参考：
+ +类型：string
详情：
+favicon.ico 地址，填入绝对路径。
注意
+我们建议你为你的站点生成 favicon。
+string"#46bd87"booleanfalsebooleanfalse类型：number
默认值：2048
详情：
+允许缓存的最大大小 (以 KB 为单位)
+注意
+此选项具有最高优先级，任何超过此值的文件都会被排除。
+所以你如果生成了很大的 HTML 或 JS 文件，请考虑调高此值，否则你的 PWA 可能无法在离线模式下正常运行。
+类型：number
默认值：1024
详情：
+图片允许缓存的最大大小 (以 KB 为单位)
+该选项不能大于 maxSize 选项
+类型："disabled" | "available" | "hint" | "force"
默认值："available"
详情：
+发现新内容时的控制逻辑。
+"disabled": 即使有新的 service worker 也不做任何事情，新的 service work 开始等待后，会在用户下次访问时接管页面，让用户获得新内容。
"available": 仅当新的 service worker 可用时才显示更新弹出窗口
"hint": 显示更新内容可用提示，并允许用户立即刷新。当新的 SW 成功注册后，将转为更新内容就绪弹窗。
当你希望用户立即查看新文档时，这很有帮助。
+提示
+如果用户在新 SW 就绪前选择刷新，当前的 Service Worker 将被注销，并且请求将开始向 Web 发出。新的 service worker 将开始安装并在安装后接管页面。
+"force": 立即注销当前 Service Worker 然后刷新以获取新内容
警告
+虽然这可以确保用户访问的是最新内容，但这可能会影响访问体验。
+提示
+文档的更新方式由以前的版本控制，因此当前选项仅影响此版本的下一次更新。
+更高支持苹果的特殊设置，忽略它们是安全的。
+string"black" | "white""black"string针对微软磁贴的特殊设置，忽略它们是安全的。
+stringstringthemeColorstring"PwaFoundPopup"string"PwaReadyPopup"booleanfalse详情：
+传递给 workbox-build 的选项，具体详情，请见 Workbox 文档
类型：PwaPluginLocaleConfig
interface PwaPluginLocaleData {
+ /**
+ * 安装按钮文字
+ */
+ install: string
+
+ /**
+ * iOS 安装文字
+ */
+ iOSInstall: string
+
+ /**
+ * 取消按钮文字
+ */
+ cancel: string
+
+ /**
+ * 关闭按钮文字
+ */
+ close: string
+
+ /**
+ * 上一张图片文字
+ */
+ prevImage: string
+
+ /**
+ * 下一张图片文字
+ */
+ nextImage: string
+
+ /**
+ * 安装解释
+ */
+ explain: string
+
+ /**
+ * 描述标签文字
+ */
+ desc: string
+
+ /**
+ * 特性标签文字
+ */
+ feature: string
+
+ /**
+ * 更新内容提示文字
+ */
+ hint: string
+
+ /**
+ * 更新内容可用文字
+ */
+ update: string
+}
+
+interface PwaPluginLocaleConfig {
+ [localePath: string]: PwaPluginLocaleData
+}
+详情：
+PWA 插件的国际化配置。
+详情：
+返回此插件的事件派发器。
+你可以添加监听器函数到 register-service-worker 提供的事件。
+示例：
+import { usePwaEvent } from '@vuepress/plugin-pwa/client'
+
+export default {
+ setup() {
+ const event = usePwaEvent()
+ event.on('ready', (registration) => {
+ console.log('Service worker is active.')
+ })
+ },
+}
+详情：
+当发现新内容时强制刷新页面。
+示例：
+import { forceUpdate } from '@vuepress/plugin-pwa/client'
+import { onMounted } from 'vue'
+
+export default {
+ setup() {
+ onMounted(() => {
+ forceUpdate()
+ })
+ },
+}
+详情：
+手动注册 Service Worker。
+参数：
+| 参数 | 类型 | 描述 | +|
+]]>将你的 VuePress 站点变成渐进式网络应用程序 (PWA)[1]。
+此插件使用 workbox-build 生成 Service Worker 文件，并使用 register-service-worker 注册 Service Worker。
+注意
+如果你启用过该插件，并想要禁用它，你可能需要 `@vuepress/plugin-remove-pwa 来移除现有的 Service Worker 。
+A PWA uses a Service Worker [2] (SW for short) to cache and proxy site content.
+一个 PWA 使用 Service Worker [2:1] (简称 SW) 来获取并托管网站内容。
+为了使你的网站符合 PWA 的要求，一个网络 App 清单[3]文件是必要的，并且你的 PWA 应满足可安装性[4]要求。
+你可以通过设置 manifest 选项来自定义 manifest 文件，或者在 public 文件夹中提供 manifest.webmanifest 或 manifest.json。前者优先级更高。
插件会自动为你生成 manifest.webmanifest，并在每个页面的 <head> 中添加清单链接声明，但是 你至少应该通过 manifest.icons 或 PWA 插件中的其他选项设置一个有效的图标。
注意
+可安装性[4:1]规范要求 manifest 中至少声明一个有效的图标。
+所以如果你不配置 manifest.icons，访问者只能享受到 Service Worker 缓存带来的离线可访问性，而并不能作为 PWA 进行安装。
此外，该插件默认不处理清单中的任何内容，而是按原样输出。 这意味着，如果你计划部署到子目录，则应自行将 URL 前缀附加到自己的清单 Urls 中。如果你需要的所有东西都在 base 文件夹下，你可以在插件选项中设置 appendBase: true 让插件将 base 自动附加到任何地址。
为了更好的控制 Service Worker 可以预缓存的内容，插件提供了相关的缓存控制选项。
+默认情况下插件会预缓存所有的 JS 和 CSS 文件，但仅缓存主页和 404 页面的 HTML。插件同时还会缓存字体文件 (woff, woff2, eot, ttf, otf) 和 SVG 图标。
+如果你的站点只有少量重要图片，并希望它们在离线模式下显示，你可以通过设置 cacheImage 选项为 true 来缓存站点图片。
我们通过文件后缀名识别图片，任何以 .png, .jpg, .jpeg, .gif, .bmp, .webp 结尾的文件都会视为图片。
当你网站体积不大，并且希望文档完全离线可用时，你可以通过设置 cacheHTML 为 true 来缓存所有 HTML 页面。
为什么默认不缓存非主页和 404 页面
+虽然说 VuePress 为所有的页面通过 SSG[5] 生成了 HTML 文件，但是这些文件主要用于 SEO[6]，并能够让你在后端不做 SPA[7] 配置的情况下能够直接访问任何链接。
+VuePress 本质上是一个 SPA。这意味着你只需要缓存主页并从主页进入即可正常访问所有页面。所以默认不缓存其他 HTML 能够有效减小缓存大小 (可以缩减大约 40% 的体积)，加快 SW 更新速度。
+但是这样做也有缺点，如果用户直接从非主页进入网站，首个页面的 HTML 文件仍需要从互联网加载。同时离线环境下，用户只能通过主页进入再自行导航到对应页面，直接访问某个链接会出现无法访问的提示。
+为了防止在预缓存列表中包含大文件，任何 > 2 MB 的文件或 > 1 MB 的图片都将被忽略。 你可以通过 maxSize 和 maxImageSize 来自定义大小限制 (单位为 KB)。
我们提供 update 选项控制用户如何接收更新。
update 选项的默认值是 "available"，这意味着当网站内容更新后，新的 SW 会在后台静默安装，并在安装结束后弹窗提示用户新内容就绪。用户可以自主选择是否立即刷新查看新内容。这意味在新 SW 就绪前用户会访问旧版本网站。
如果你的文档仍在建设期，希望尽早提示用户他可能在阅读已过时的内容，你可以将其设置为 "hint"。这样用户在进入文档后数秒内就可以收到新内容已发布的通知。但这样做的负面效果是如果用户在新 SW 就绪前选择更新，那么他将在新 SW 安装并接管页面前，需要从互联网获取页面的全部资源。
如果你的文档很稳定，或者你在托管博客，不太关心用户立即接收到最新版本，你可以将其设置为 "disabled"，这意味着新的 SW 将在后台完全静默安装并在安装后等待，当旧版本 SW 控制的页面全部关闭后，新 SW 将再下次访问接管并提供用户新内容。此设置可以避免用户在访中被弹窗打扰。
如果你希望通过 SW 来加速用户在弱网或无网条件下的访问，但同时希望用户时刻访问新内容，你可以将此选项设置为 "force"。这意味着检测到新 SW 后旧 SW 将会被立刻销毁并且页面会被刷新以确保用户浏览最新内容。最大的缺点就是致新 SW 发布后，用户在重新进入网站后的几秒内会遇到预期之外的突然刷新，并且他们将必须通过互联网访问文档并完全重新安装最新的 SW。
当检测到新内容 (检测到新的 SW) 时，更新提示弹窗将会出现；当新内容就绪时，更新就绪弹窗将会出现。
+如果你对默认的弹窗不满意，你可以自行编写组件更换。从 @vuepress/plugin-pwa/client 中导入 PwaFoundPopup 或 PwaReadyPopup 并使用其 slot 来自定义弹窗内容，然后将组件路径传递给 foundComponent 或 readyComponent 选项。
<script setup lang="ts">
+import { PwaFoundPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaFoundPopup v-slot="{ found, refresh }">
+ <div v-if="found">
+ 已找到新内容
+ <button @click="refresh">刷新</button>
+ </div>
+ </PwaFoundPopup>
+</template>
+<script setup lang="ts">
+import { PwaReadyPopup } from '@vuepress/plugin-pwa/client'
+</script>
+<template>
+ <PwaReadyPopup v-slot="{ isReady, reload }">
+ <div v-if="isReady">
+ 新内容已就绪
+ <button @click="reload">应用</button>
+ </div>
+ </PwaReadyPopup>
+</template>
+插件还提供了其他 PWA 相关选项，比如微软磁贴图标与颜色设置，苹果图标等。 如果你是一个高级用户，你也可以设置 generateSwConfig 来配置 workbox-build。查看 插件选项 了解更多细节。
更多内容，请详见:
+ +PWA 介绍
+PWA 全称 Progressive Web app，即渐进式网络应用程序，标准由 W3C 规定。
+它允许网站通过支持该特性的浏览器将网站作为 App 安装在对应平台上。
+访问 https://developer.mozilla.org/zh-CN/docs/Web/Progressive_web_apps 查看详情。 ↩︎
+Service Worker 简要介绍
+Service Worker 会在注册过程中获取注册在其中的所有文件并缓存它们。
+注册成功后，Service Worker 激活，并开始代理并控制你的全部请求。
+每当你想要通过浏览器发起访问请求后，Service Worker 将会查看其是否存在与自身缓存列表中，若存在则直接返回缓存好的结果，否则调用自身的 fetch 方法进行获取。你可以通过自定义 fetch 方法，来完全控制网页内资源获取请求的结果，比如在离线时提供一个 fallback 的网页。
+每次用户重新打开网站时，Service Worker 会向自身注册时的地址发出校验命令，如果检测到新版本的 Service Worker，则会更新自身，并开始缓存注册在新 Service Worker 中的资源列表。成功获取内容更新后，Service Worker 将会触发 update 事件。可以通过此事件提示用户，比如将在右下角显示一个弹出窗口，提示用户新内容可用并允许用户触发更新。
清单文件
+清单文件使用 JSON 格式，负责声明 PWA 各项信息，如名称、描述、图标、快捷动作等。
+为了使你的站点能够被注册为 PWA，你需要满足 manifest 基本的规范，才能使浏览器认为该网站为一个可安装的 PWA 并允许用户安装它。
+提示
+Manifest 的标准与规范，请详见 MDN 网络 App 清单 和 W3C Manifest
+可安装性
+想要让网站可以注册为 PWA，网站需要自行成功注册有效的 Service Worker，同时拥有合法的 manifest 清单文件并在网站中声明它。
+清单文件应至少包含 name(或 short_name) icons start_url。
SSG: Static Site Generating，静态站点生成。 ↩︎
+SEO: Search Engine Optimization，搜索引擎增强，
+ +SPA: Single Page Application, 单页应用
+大多只有主页，并使用 history mode 处理路由，而不是真的在页面之间导航。 ↩︎
+类型：string
必填：是
+详情：
+部署域名
+类型：Author
type AuthorName = string
+
+interface AuthorInfo {
+ /**
+ * 作者姓名
+ */
+ name: string
+
+ /**
+ * 作者网站
+ */
+ url?: string
+
+ /**
+ * 作者 Email
+ */
+ email?: string
+}
+
+type Author = AuthorName | AuthorName[] | AuthorInfo | AuthorInfo[]
+详情：
+默认作者
+类型：boolean
默认值：true
详情：
+是否自动生成描述
+类型：string | ((page: Page) => string | null)
详情：
+首选链接
+类型：string
详情：
+当找不到图片时的回退图片链接
+类型：string
详情：
+内容的年龄分级，格式为 [int]+，如 "13+"
类型：string
详情：
+你的 twitter 用户名
+类型：(page: Page) => boolean
详情：
+你可以使用此选项判断一个页面是否是文章。
+类型：
+function ogp(
+ /** 插件推断的 OGP 信息 */
+ ogp: SeoContent,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): SeoContent
+详情：
+自定义 OGP 生成器
+你可以使用此选项来注入新的或覆盖掉默认生成的 OGP 标签。
+类型：
+function jsonLd(
+ /** 由插件推断出的 JSON-LD 对象 */
+ jsonLD: ArticleSchema | BlogPostingSchema | WebPageSchema,
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): ArticleSchema | BlogPostingSchema | WebPageSchema
+详情：
+自定义 JSON-LD 生成器
+你可以使用此选项来注入新的或覆盖掉默认生成的 JSON-LD 标签。
+类型：
+function customHead(
+ /** head 标签配置 */
+ head: HeadConfig[],
+ /** 页面对象 */
+ page: Page,
+ /** VuePress App */
+ app: App,
+): void
+详情：
+你可以使用此选项来直接注入任意格式的标签到 <head>。
<head> 注入标签，让你的网站完全支持 开放内容协议 OGP 和 JSON-LD 1.1，以全面增强站点的搜索引擎优化性。
+
+插件开箱即用，在不做任何配置的情况下，会尽可能通过页面内容，提取对应的信息补全 OGP 与 JSON-LD 所需的必要标签。
+默认情况下，插件会读取站点配置、主题配置与页面的 frontmatter 来尽可能自动生成。诸如站点名称，页面标题，页面类型，写作日期，最后更新日期，文章标签均会自动生成。
+| 属性名称 | 值 | +| :
+]]>类型：string
必填：是
+详情：
+当前网站部署到的域名，插件需要此选项才能工作。
+类型：string[]
详情：
+需要额外包含的网址。
+如果你有一些不包含在 VuePress 路由中的链接 (如: 存放在 public 文件夹下的页面或其他插件或工具直接生成的页面)，你可能需要设置此项。
+示例：['/about.html', '/api/']
类型：string[]
默认值：['/404.html']
详情：
+不需要收录的页面路径，请以绝对路径开头。
+默认情况下 VuePress 自动生成的所有路径 (除 404 页) 都会被添加进 Sitemap。
+类型：boolean
默认值：false
详情：
+是否在开发服务器中启用
+提示
+由于性能原因，我们不提供热更新。重启开发服务器以同步你的变更。
+类型：string
默认值："http://localhost:${port}"
详情：
+开发服务器使用的主机名
+类型：string
默认值："sitemap.xml"
详情：
+输出的文件名，相对于输出目录。
+类型：string
默认值："sitemap.xsl"
详情：
+输出的 xsl 文件名，相对于输出目录。
+类型：string
默认值："@vuepress-plugin/sitemap/templates/sitemap.xsl"
详情：
+用作模板的 XSL 文件内容
+类型："always" | "hourly" | "daily" | "weekly" | "monthly" | "yearly" | "never"
默认值："daily"
详情：
+页面默认更新频率，会被 Frontmatter 中的 changefreq 选项覆盖。
+类型：number
默认值：0.5
详情：
+页面优先级，范围 0 至 1。
类型：(page: Page, app: App) => string
详情：
+最后修改事件的获得器，需要返回一个 ISO 字符形式的时间，默认会自动通过 Git 插件生成。
+类型：SitemapFrontmatterOptions | false
详情：
+false 表示将页面排除在 sitemap 之外。
类型："always" | "hourly" | "daily" | "weekly" | "monthly" | "yearly" | "never"
默认值："daily"
详情：
+页面默认更新频率。它会覆盖插件选项中的 changefreq 选项。
+类型：number
默认值：0.5
详情：
+页面优先级，范围 0 至 1。
hostname 选项。如果你想在开发服务器中预览，请配置 devServer 选项。
+插件会自动根据页面的 Git 的时间戳生成页面的最后更新时间，同时会根据站点的多语言配置声明页面的其他语言版本替代地址。
+默认情况下，所有除 404 页面以外的网站链接均会被添加进 Sitemap。
+如果你希望在 VuePress 项目页面之外，添加其他页面链接到 Sitemap，请将它们变成数组传入插件的 extraUrls 选项。
如果你需要排除一些页面路径，你可以将它们变成数组传入到插件的 excludePaths 选项。你也可以在对应页面的 frontmatter 中，设置 sitemap 为 false。
你还可以通过插件的 sitemapFilename 选项控制输出的地址，此地址相对于输出目录，默认为 sitemap.xml。
页面默认的更新周期是 daily (每天)，如果你希望修改全部的页面周期，请在插件选项中设置 changefreq 。你也可以在页面的 frontmatter 中设置 sitemap.changefreq，页面具有更高的优先级。
合法的频率有:
+"always""hourly""daily""weekly""monthly""yearly""never"你可以在插件中设置 priority 以提供一个默认值。同时你可以通过 frontmatter 中的 sitemap.priority 来为每个页面设置优先级。可接受的值为 0 到 1 的浮点数。
你可以通过插件的 modifyTimeGetter 来返回一个 ISO 字符串格式的时间，默认会通过 Git 插件生成。
以下是一个基于文件最后修改时间的例子。
+// 基于文件最后修改时间
+({
+ modifyTimeGetter: (page, app) =>
+ fs.statSync(app.dir.source(page.filePathRelative)).mtime.toISOString();
+})
+网站地图 (Sitemap) 提供搜索引擎优化 (SEO):
+网站地图通过使所有页面可被找到来增强搜索引擎优化的效果。
+大部分搜索引擎只跟踪页面内有限数量的链接，因此当网站非常大的时候，网站地图对于使搜索引擎和访问者可以访问网站中的所有内容就变得必不可少了。
+Sitemaps 是站点管理员向搜索引擎爬虫公布站点可被抓取页面的协议，sitemap 文件内容必须遵循 XML 格式的定义。每个 URL 可以包含更新的周期和时间、URL 在整个站点中的优先级。这样可以让搜索引擎更佳有效的抓取网站内容。
+同步配置 robots.txt
+由于 Sitemap 面向搜索引擎，配合此插件使用时，你最好保证你在 .vuepress/public 文件夹下放置了有效的 robots.txt，以允许搜索引擎收录。一个最简单的 robots.txt 如下 (允许所有搜索引擎访问所有路径)
User-agent: *
+
+Allow: /
+类型： string
详情：
+部署的域名，例如 https://example.com
类型： { [path: string]: Partial<DefaultThemeLocaleData> }
默认值： {}
详情：
+多语言支持的各个语言 locales 。
+所有在 Locale 配置 章节内的配置项都可以在 locales 中使用。
+该配置项仅能在默认主题内生效，注意不要和 站点配置 中的 locales 混淆。
参考：
+该章节内的配置项可以作为一般配置使用，也可以使用在 locales 内。
+类型： 'auto' | 'light' | 'dark'
默认值： 'auto'
详情：
+默认颜色模式。
+如果设置为 'auto' ，则会根据 prefers-color-scheme 自动设置初始颜色模式。
参考：
+ +类型： boolean
默认值： true
详情：
+是否启用切换颜色模式的功能。
+如果设置为 true ，将会在导航栏展示一个切换颜色模式的按钮。
参考：
+ +类型： string
默认值： /
详情：
+首页的路径。
+它将被用于：
+类型： false | (NavbarItem | NavbarGroup | string)[]
默认值： []
详情：
+导航栏配置。
+设置为 false 可以禁用导航栏。
为了配置导航栏元素，你可以将其设置为 导航栏数组 ，其中的每个元素是 NavbarItem 对象、 NavbarGroup 对象、或者字符串：
NavbarItem 对象应该有一个 text 字段和一个 link 字段，还有一个可选的 activeMatch 字段。NavbarGroup 对象应该有一个 text 字段和一个 children 字段。 children 字段同样是一个 导航栏数组 。NavbarItem 对象，将页面标题作为 text ，将页面路由路径作为 link 。示例 1：
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // NavbarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ },
+ // NavbarGroup
+ {
+ text: 'Group',
+ children: ['/group/foo.md', '/group/bar.md'],
+ },
+ // 字符串 - 页面文件路径
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // 嵌套 Group - 最大深度为 2
+ {
+ text: 'Group',
+ children: [
+ {
+ text: 'SubGroup',
+ children: ['/group/sub/foo.md', '/group/sub/bar.md'],
+ },
+ ],
+ },
+ // 控制元素何时被激活
+ {
+ text: 'Group 2',
+ children: [
+ {
+ text: 'Always active',
+ link: '/',
+ // 该元素将一直处于激活状态
+ activeMatch: '/',
+ },
+ {
+ text: 'Active on /foo/',
+ link: '/not-foo/',
+ // 该元素在当前路由路径是 /foo/ 开头时激活
+ // 支持正则表达式
+ activeMatch: '^/foo/',
+ },
+ ],
+ },
+ ],
+ }),
+}
+类型： null | string
详情：
+Logo 图片的 URL。
+Logo 图片将会显示在导航栏的左端。
+设置为 null 可以禁用 Logo 。
示例：
+export default {
+ theme: defaultTheme({
+ // Public 文件路径
+ logo: '/images/hero.png',
+ // URL
+ logo: 'https://vuejs.org/images/logo.png',
+ }),
+}
+类型： null | string
详情：
+在夜间模式中使用的 Logo 图片的 URL。
+如果你想在夜间模式中使用不同的 Logo 图片，就可以使用该配置项。
+设置为 null 可以在夜间模式下禁用 Logo 。忽略该配置项将会在夜间模式中使用 logo 配置。
参考：
+ +类型：null | string
详情：
+指定 Logo 图片的替代文字。
+当未指定时，将默认与站点标题相同。
+类型： string
详情：
+项目仓库的 URL。
+它将被用作 仓库链接 的链接。仓库链接 将会显示为导航栏的最后一个元素。
+export default {
+ theme: defaultTheme({
+ // 如果你按照 `organization/repository` 的格式设置它
+ // 我们会将它作为一个 GitHub 仓库
+ repo: 'vuejs/vuepress',
+ // 你也可以直接将它设置为一个 URL
+ repo: 'https://gitlab.com/foo/bar',
+ }),
+}
+类型： false | 'auto' | SidebarConfigArray | SidebarConfigObject
默认值： 'auto'
详情：
+侧边栏配置。
+你可以通过页面的 sidebar frontmatter 来覆盖这个全局配置。
+设置为 false 可以禁用侧边栏。
如果你设置为 'auto'，侧边栏会根据页面标题自动生成。
为了手动配置侧边栏元素，你可以将其设置为 侧边栏数组 ，其中的每个元素是一个 SidebarItem 对象或者一个字符串：
SidebarItem 对象应该有一个 text 字段，有一个可选的 link 字段、一个可选的 children 字段和一个可选的 collapsible 字段。 children 字段同样是一个 侧边栏数组 。 collapsible 字段来控制它是否可折叠。SidebarItem 对象，将页面标题作为 text ，将页面路由路径作为 link ，并根据页面小标题自动生成 children 。如果你想在不同子路径中使用不同的侧边栏，你可以将该配置项设置为 侧边栏对象 ：
+"heading" 以自动为相应路径生成基于标题的侧边栏。示例 1：
+export default {
+ theme: defaultTheme({
+ // 侧边栏数组
+ // 所有页面会使用相同的侧边栏
+ sidebar: [
+ // SidebarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ children: [
+ // SidebarItem
+ {
+ text: 'github',
+ link: 'https://github.com',
+ children: [],
+ },
+ // 字符串 - 页面文件路径
+ '/foo/bar.md',
+ ],
+ },
+ // 字符串 - 页面文件路径
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // 侧边栏对象
+ // 不同子路径下的页面会使用不同的侧边栏
+ sidebar: {
+ '/guide/': [
+ {
+ text: 'Guide',
+ children: ['/guide/introduction.md', '/guide/getting-started.md'],
+ },
+ ],
+ '/reference/': 'heading',
+ },
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // 可折叠的侧边栏
+ sidebar: {
+ '/reference/': [
+ {
+ text: 'VuePress Reference',
+ collapsible: true,
+ children: ['/reference/cli.md', '/reference/config.md'],
+ },
+ {
+ text: 'Bundlers Reference',
+ collapsible: true,
+ children: [
+ '/reference/bundler/vite.md',
+ '/reference/bundler/webpack.md',
+ ],
+ },
+ ],
+ },
+ }),
+}
+类型： number
默认值： 2
详情：
+设置根据页面标题自动生成的侧边栏的最大深度。
+0 来禁用所有级别的页面标题。1 来包含 <h2> 标题。2 来包含 <h2> 和 <h3> 标题。最大值取决于你通过 markdown.headers.level 提取了哪些级别的标题。
+由于 markdown.headers.level 的默认值是 [2, 3] ，因此 sidebarDepth 的默认最大值是 2 。
你可以通过页面的 sidebarDepth frontmatter 来覆盖这个全局配置。
+类型： boolean
默认值： true
详情：
+是否启用 编辑此页 链接。
+你可以通过页面的 editLink frontmatter 来覆盖这个全局配置。
+类型： string
详情：
+编辑此页 链接的 Pattern 。
+它将会用于生成 编辑此页 的链接。
+如果你不设置该选项，则会根据 docsRepo 配置项来推断 Pattern 。但是如果你的文档仓库没有托管在常用的平台上，比如 GitHub 、 GitLab 、 Bitbucket 、 Gitee 等，那么你必须设置该选项才能使 编辑此页 链接正常工作。
+用法：
+| Pattern | 描述 | +|
+默认主题的 Layout 布局提供了一些插槽：
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottom在它们的帮助下，你可以很容易地添加或替换内容。下面通过一个示例来介绍一下如何使用布局插槽来继承默认主题。
+首先，创建一个客户端配置文件 .vuepress/client.ts ：
import { defineClientConfig } from 'vuepress/client'
+import Layout from './layouts/Layout.vue'
+
+export default defineClientConfig({
+ layouts: {
+ Layout,
+ },
+})
+接下来，创建 .vuepress/layouts/Layout.vue ，并使用由默认主题的 Layout 布局提供的插槽：
<script setup>
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+</script>
+
+<template>
+ <ParentLayout>
+ <template #page-bottom>
+ <div class="my-footer">This is my custom page footer</div>
+ </template>
+ </ParentLayout>
+</template>
+
+<style lang="css">
+.my-footer {
+ text-align: center;
+}
+</style>
+此时默认的 Layout 布局已经被你的本地布局覆盖，将会在除了首页外的所有页面添加一个自定义的页脚：
布局插槽十分实用，但有时候你可能会觉得它不够灵活。默认主题同样提供了替换单个组件的能力。
+默认主题将所有 非全局的组件 都注册了一个带 @theme 前缀的 alias 。例如，HomeFooter.vue 的别名是 @theme/HomeFooter.vue 。
接下来，如果你想要替换 HomeFooter.vue 组件，只需要在配置文件 .vuepress/config.ts 中覆盖这个别名即可：
import { defaultTheme } from '@vuepress/theme-default'
+import { getDirname, path } from 'vuepress/utils'
+import { defineUserConfig } from 'vuepress'
+
+const __dirname = getDirname(import.meta.url)
+
+export default defineUserConfig({
+ theme: defaultTheme(),
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+})
+除了在 .vuepress/config.ts 和 .vuepress/client.ts 中直接扩展默认主题以外，你可以通过继承默认主题来开发一个你自己的主题：
import { defaultTheme, type DefaultThemeOptions } from '@vuepress/theme-default'
+import type { Theme } from 'vuepress/core'
+import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export const childTheme = (options: DefaultThemeOptions): Theme => {
+ return {
+ name: 'vuepress-theme-child',
+ extends: defaultTheme(options),
+
+ // 在子主题的客户端配置文件中覆盖布局
+ // 注意，你在发布到 NPM 之前会将 TS 构建为 JS ，因此这里需要设置为 JS 文件的路径
+ clientConfigFile: path.resolve(__dirname, './client.js'),
+
+ // 覆盖组件别名
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+ }
+}
+如果你的站点是以英语以外的其他语言提供服务的，你应该为每个语言设置这些选项来提供翻译。
+类型： string
详情：
+项目仓库的标签。
+它将被用作 仓库链接 的文字。仓库链接 将会显示为导航栏的最后一个元素。
+如果你不明确指定该配置项，它将会根据 repo 配置项自动推断。
+类型： string
详情：
+选择语言菜单 的文字。
+如果你在站点配置中设置了多个 locales ，那么 选择语言菜单 就会显示在导航栏中仓库按钮的旁边。
+类型： string
详情：
+选择语言菜单 的 aria-label 属性。
它主要是为了站点的可访问性 (a11y) 。
+类型： string
详情：
+Locale 的语言名称。
+该配置项 仅能在主题配置的 locales 的内部生效 。它将被用作 locale 的语言名称，展示在 选择语言菜单 内。
+示例：
+export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+ theme: defaultTheme({
+ locales: {
+ '/': {
+ selectLanguageName: 'English',
+ },
+ '/zh/': {
+ selectLanguageName: '简体中文',
+ },
+ },
+ }),
+}
+类型：null | string
详情：
+导航栏中主导航 aria-label 属性的值。
类型：null | string
详情：
+下一页/上一页导航 aria-label 属性的值
类型： string
默认值： 'Edit this page'
详情：
+编辑此页 链接的文字。
+类型： string
默认值： 'Last Updated'
详情：
+最近更新时间戳 标签的文字。
+类型： string
默认值： 'Contributors'
详情：
+贡献者列表 标签的文字。
+类型： string
默认值： 'TIP'
详情：
+Tip 自定义容器 的默认标题。
+类型： string
默认值： 'WARNING'
详情：
+Warning 自定义容器 的默认标题。
+类型： string
默认值： 'DANGER'
详情：
+Danger 自定义容器 的默认标题。
+类型： string[]
默认值： ['Not Found']
详情：
+404 页面的提示信息。
+当用户进入 404 页面时，会从数组中随机选取一条信息进行展示。
+类型： string
默认值： 'Back to home'
详情：
+404 页面中 返回首页 链接的文字。
+类型： string
默认值： 'open in new window'
详情：
+ExternalLinkIcon. 链接内的 sr-only 文字。
它主要是为了站点的可访问性 (a11y) 。
+参考：
+ +类型： string
默认值： 'toggle color mode'
详情：
+切换颜色模式按钮的标题文字。
+它主要是为了站点的可访问性 (a11y) 。
+参考：
+ +类型： string
默认值： 'toggle sidebar'
详情：
+切换侧边栏按钮的标题文字。
+它主要是为了站点的可访问性 (a11y) 。
+类型： string
默认值： 'Prev'
详情：
+上一页按钮的文字。
+类型： string
默认值： 'Next'
详情：
+下一页按钮的文字。
+themePlugins 设置默认主题使用的插件。
+默认主题使用了一些插件，如果你确实不需要该插件，你可以选择禁用它。在禁用插件之前，请确保你已了解它的用途。
+import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ themePlugins: {
+ // 在这里自定义主题插件
+ },
+ }),
+}
+类型： boolean
默认值： true
详情：
+ +类型： BackToTopPluginOptions | boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-back-to-top 。
+支持对象格式以作为插件选项。
+类型： Record<ContainerType, boolean>
详情：
+是否启用由 @vuepress/plugin-container 支持的自定义容器。
+ContainerType 类型为：
tipwarningdangerdetailscodeGroupcodeGroupItem参考：
+ +类型： CopyCodePluginOptions | boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-copy-code 。
+支持对象格式以作为插件选项。
+类型： boolean
默认值： true
详情：
+ +类型： boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-git 。
+类型： boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-links-check 。
+类型： boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-medium-zoom 。
+类型： boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-nprogress 。
+类型： boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-prismjs 。
+类型： SeoPluginOptions | boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-seo 。
+支持对象格式以作为插件选项。
+类型： SitemapPluginOptions | boolean
默认值： true
详情：
+是否启用 @vuepress/plugin-sitemap 。
+支持对象格式以作为插件选项。
+检查组件是否已全局注册。
+提示
+setup 之外调用时，你需要将 app 实例作为第二个参数传递。export const hasGlobalComponent: (name: string, app?: App) => boolean
+// 如果你全局注册了 `<my-component>`
+hasGlobalComponent('MyComponent') // true
+hasGlobalComponent('my-component') // true
+
+hasGlobalComponent('MyComponent2') // false
+从语言环境设置中获取当前语言环境配置。
+export const useLocaleConfig: <T extends LocaleData>(
+ localesConfig: RequiredLocaleConfig<T>,
+) => ComputedRef<T>
+const localesCOnfig = {
+ '/': 'Title',
+ '/zh/': '标题',
+}
+
+const locale = useLocaleConfig(localesConfig)
+
+// under `/page`
+locale.value // 'Title'
+
+// under `/zh/page`
+locale.value // '标题'
+此方法在 MarkdownIt 插件中很有用。有些时候你可能需要在 Markdown 插件中生成组件，并将复杂的数据写入到组件属性中，一个通常做法是使用 JSON.stringify + encodeURIComponent，并在客户端 decodeURIComponent + JSON.parse。但如果内容包含很多特殊字符，转换结果会很长。
所以我们提供 encodeData 和 decodeData 来压缩和编码内容。
export const encodeData: (
+ data: string,
+ level: DeflateOptions['level'] = 6,
+) => string
+
+export const decodeData: (compressed: string) => string
+const content = `
+{
+ "type": "bar",
+ "data": {
+ "labels": ["Red", "Blue", "Yellow", "Green", "Purple", "Orange"],
+ "datasets": [
+ {
+ "label": "# of Votes",
+ "data": [12, 19, 3, 5, 2, 3],
+ "backgroundColor": [
+ "rgba(255, 99, 132, 0.2)",
+ "rgba(54, 162, 235, 0.2)",
+ "rgba(255, 206, 86, 0.2)",
+ "rgba(75, 192, 192, 0.2)",
+ "rgba(153, 102, 255, 0.2)",
+ "rgba(255, 159, 64, 0.2)"
+ ],
+ "borderColor": [
+ "rgba(255, 99, 132, 1)",
+ "rgba(54, 162, 235, 1)",
+ "rgba(255, 206, 86, 1)",
+ "rgba(75, 192, 192, 1)",
+ "rgba(153, 102, 255, 1)",
+ "rgba(255, 159, 64, 1)"
+ ],
+ "borderWidth": 1
+ }
+ ]
+ },
+ "options": {
+ "scales": {
+ "y": {
+ "beginAtZero": true
+ }
+ }
+ }
+}
+`
+
+const prop = encodeData(content) // "eJyNUsFOwzAMve8rrHABKZqWlg5WxAE4cARxAMHEIV1NmQhNlaaCCe3fcdKtW0sLWGpjxy/v+UV512mlcIyfhTa2hHP4GgHYVYExsEQaxqlMpZWxbwAomaAqY5izO0wZB3apKnTrIyqlP1x2bRBzl9xWplC+eWNkniF7dmw1X4nWsfgaNtwNP2kfgH6Be22x9CPUUQ8yFwEHMeMQcog4UBFuiF0kcvGWGV3l6ZVW2uw0XDCTJfIwiOjYjAhESIcn4+BoT2MLio6pP6V+EBJ6AOSZgsmUwyl9A6ATwoiZn3lYTkTkRkycnuP8TU9ENPqUxuuA9i9BmxTNPy9A/G2/F9I23wtpW++FdIwPKzW2W5Afph+WqX2NQWz313XicT7XhV3qnB5f/ejKhVTYVACrXUqUmC3zC/uERsdgTYUdVr/Qb302+gZxe7S/"
+
+decodeData(prop) // will be the original content
+
+// if you use `encodeURIComponent`, it will be much longer
+encodeURIComponent(content) // '%0A%7B%0A%20%20%22type%22%3A%20%22bar%22%2C%0A%20%20%22data%22%3A%20%7B%0A%20%20%20%20%22labels%22%3A%20%5B%22Red%22%2C%20%22Blue%22%2C%20%22Yellow%22%2C%20%22Green%22%2C%20%22Purple%22%2C%20%22Orange%22%5D%2C%0A%20%20%20%20%22datasets%22%3A%20%5B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%22label%22%3A%20%22%23%20of%20Votes%22%2C%0A%20%20%20%20%20%20%20%20%22data%22%3A%20%5B12%2C%2019%2C%203%2C%205%2C%202%2C%203%5D%2C%0A%20%20%20%20%20%20%20%20%22backgroundColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%200.2)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%201)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderWidth%22%3A%201%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%0A%20%20%7D%2C%0A%20%20%22options%22%3A%20%7B%0A%20%20%20%20%22scales%22%3A%20%7B%0A%20%20%20%20%20%20%22y%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22beginAtZero%22%3A%20true%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A'
+isDef(x): 判断 x 是否定义。isBoolean(x): 判断 x 是否为布尔值。isString(x): 判断 x 是否为字符串。isNumber(x): 判断 x 是否为数字。isPlainObject(x): 判断值是否为纯对象。isArray(x): 判断 x 是否为数组isFunction(x): 判断 x 是否为函数。isRegExp(x): 判断 x 是否为正则表达式startsWith(a, b): 判断字符串 a 是否以指定字符串 b 开头endsWith(a, b): 判断字符串 a 是否以指定字符串 b 结尾当 a 不是字符串时返回 false
keys(x): 以数组形式返回对象 x 的键
values(x): 以数组形式返回对象 x 的值
entries(x): 将对象 x 转换为键值对数组。
fromEntries(x): 将键值对数组 x 转换为对象。
deepAssign(x, y, ...): Object.assign 的深度版本。
// or @vuepress/helper/client
+import { deepAssign } from '@vuepress/helper'
+
+const defaultOptions = {
+ optionA: {
+ optionA1: 'defaultOptionA1',
+ optionA2: 'defaultOptionA2',
+ optionA3: 'defaultOptionA3',
+ },
+ optionB: true,
+ optionC: 'optionC',
+}
+
+const userOptions = {
+ optionA: {
+ optionA1: 'optionA1',
+ optionA2: 'optionA2',
+ },
+ optionB: false,
+}
+
+deepAssign(defaultOptions, userOptions)
+// {
+// optionA: {
+// optionA1: "optionA1",
+// optionA2: "optionA2",
+// optionA3: "defaultOptionA3",
+// },
+// optionB: false,
+// optionC: "optionC",
+// }
+getDate(x): 将输入 x 转换为日期，可以支持 Date，时间戳，日期字符串。日期字符串的支持度以环境的 Date.parse 支持度为准。当不能转换为日期时返回 null
getDate('2021-01-01') // a Date object represents 2021-01-01
+getDate(1609459200000) // a Date object represents 2021-01-01
+getDate('2021-01-01T00:00:00.000Z') // a Date object represents 2021-01-01
+getDate('2021/01/01') // a Date object represents 2021-01-01 (might be null in some browsers)
+getDate('invalid date') // null
+getDate(undefined) // null
+getDate(-32) // null
+dateSorter: 将可转换为日期的值从新到旧排序，不能转换为日期的值会在最后。
const arr = [
+ '2020-01-01',
+ 1609459200000,
+ '2022-01-01T00:00:00.000Z',
+ '2023/01/01',
+ 'invalid date',
+ undefined,
+ -32,
+]
+
+arr.sort(dateSorter)
+// [
+// '2023/01/01',
+// '2022-01-01T00:00:00.000Z',
+// 1609459200000,
+// '2020-01-01',
+// 'invalid date',
+// undefined,
+// -32,
+// ]
+isLinkHttp(x): x 是否是有效的 HTTP URL。isLinkWithProtocol(x): x 是否是有效的带有协议的 URL。isLinkExternal(x): x 是否是有效的外部 URL。isLinkAbsolute(x): x 是否是有效的绝对 URL。ensureEndingSlash(x): 确保 x 以斜杠结尾。ensureLeadingSlash(x): 确保 x 以斜杠开头。removeEndingSlash(x): 确保 x 不以斜杠结尾。removeLeadingSlash(x): 确保 x 不以斜杠开头。来到你的博客，或是任意位置，放置 Artalk 评论框，让页面具备丰富的社会化功能。
+ +npm i -D artalk
+请参见 Artalk 文档。
+请配置 provider: "Artalk" 并将你的服务端地址传入插件选项中的 server。
其他的配置项详见 Artalk 配置。
+提示
+插件保留 el 选项在页面自行插入 Artalk。同时插件会自动根据 VuePress 信息为你自动设置 pageTitle, pageKey 和 site 选项。
为了能使 Artalk 应用正确的主题，你需要通过 darkmode 属性向 <CommentService /> 传入一个布尔值，代表当前是否开启夜间模式。
详见 Artalk 配置。
+el pageTitle, pageKey 和 site 选项为插件的保留选项，将从 VuePress 配置中自动推断，不可设置。
imgUploader 和 avatarURLBuilder 这两个函数选项只能在客户端配置。
你可以直接在插件选项中配置可序列化的选项:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Artalk',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineArtalkConfig 函数来配置 Artalk。
import { defineClientConfig } from 'vuepress/client'
+import { defineArtalkConfig } from 'vuepress-plugin-comment2/client'
+
+defineArtalkConfig({
+ // Artalk 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+你需要创建一个公开仓库，并开启评论区，以作为评论存放的地点
+你需要安装 Giscus App，使其有权限访问对应仓库。
+在完成以上步骤后，请前往 Giscus 页面 获得你的设置。
+你只需要填写仓库和 Discussion 分类，之后滚动到页面下部的 “启用 giscus” 部分，获取 data-repo, data-repo-id, data-category 和 data-category-id 这四个属性。
请配置 provider: "Giscus" 并将 data-repo, data-repo-id, data-category 和 data-category-id 作为插件选项传入 repo, repoId, category categoryId。
其他的配置项详见 Giscus 配置。
+默认情况下，Giscus 使用 light 或 dark 主题 (基于夜间模式状态)。
::: info 夜间模式
+为了能使 Giscus 应用正确的主题，你需要为 <CommentService /> 通过 darkmode 属性传入一个布尔值，代表当前是否开启夜间模式。
:::
+如果你想在日间模式和夜间模式下自定义主题，你可以设置 lightTheme 和 darkTheme 选项，使用内置主题关键字或以 https:// 开头的自定义 css 链接。
stringstringstringstringstring"pathname"booleantruebooleantruebooleantrue"top" | "bottom""top"类型: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+默认值: "light"
详情：
+Giscus 在日间模式下使用的主题
+应为一个内置主题关键词或者一个 CSS 链接。
+类型: GiscusTheme
type GiscusTheme =
+ | 'light'
+ | 'light_high_contrast'
+ | 'light_protanopia'
+ | 'dark'
+ | 'dark_high_contrast'
+ | 'dark_protanopia'
+ | 'dark_dimmed'
+ | 'transparent_dark'
+ | 'preferred_color_scheme'
+ | `https://${string}`
+默认值: "dark"
详情：
+Giscus 在夜间模式下使用的主题
+应为一个内置主题关键词或者一个 CSS 链接。
+你可以直接在插件选项中配置可序列化的选项:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Giscus',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineGiscusConfig 函数来配置 Giscus。
import { defineClientConfig } from 'vuepress/client'
+import { defineGiscusConfig } from 'vuepress-plugin-comment2/client'
+
+defineGiscusConfig({
+ // Giscus 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+npm i -D twikoo
+部署共有四种方式。
+| 部署方式 | 描述 | +|
+]]>stringstring"ap-shanghai"你可以直接在插件选项中配置可序列化的选项:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Twikoo',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineTwikooConfig 函数来配置 Twikoo。
import { defineClientConfig } from 'vuepress/client'
+import { defineTwikooConfig } from 'vuepress-plugin-comment2/client'
+
+defineTwikooConfig({
+ // Twikoo 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+npm i -D @waline/client
+点击左上角 创建应用 并起一个你喜欢的名字 (请选择免费的开发版):
+ +进入应用，选择左下角的 设置 > 应用 Key。你可以看到你的 APP ID,APP Key 和 Master Key。请记录它们，以便后续使用。
国内版需要完成备案接入
+如果你正在使用 Leancloud 国内版 (leancloud.cn)，我们推荐你切换到国际版 (leancloud.app)。否则，你需要为应用额外绑定已备案的域名，同时购买独立 IP 并完成备案接入:
+设置 > 域名绑定 > API 访问域名 > 绑定新域名 > 输入域名 > 确定。点击上方按钮，跳转至 Vercel 进行 Server 端部署。
+::: note
+如果你未登录的话，Vercel 会让你注册或登录，请使用 GitHub 账户进行快捷登录。
+:::
+输入一个你喜欢的 Vercel 项目名称并点击 Create 继续:
此时 Vercel 会基于 Waline 模板帮助你新建并初始化仓库，仓库名为你之前输入的项目名。
+
一两分钟后，满屏的烟花会庆祝你部署成功。此时点击 Go to Dashboard 可以跳转到应用的控制台。
点击顶部的 Settings - Environment Variables 进入环境变量配置页，并配置三个环境变量 LEAN_ID, LEAN_KEY 和 LEAN_MASTER_KEY 。它们的值分别对应上一步在 LeanCloud 中获得的 APP ID, APP KEY, Master Key。
::: note
+如果你使用 LeanCloud 国内版，请额外配置 LEAN_SERVER 环境变量，值为你绑定好的域名。
:::
+环境变量配置完成之后点击顶部的 Deployments 点击顶部最新的一次部署右侧的 Redeploy 按钮进行重新部署。该步骤是为了让刚才设置的环境变量生效。
此时会跳转到 Overview 界面开始部署，等待片刻后 STATUS 会变成 Ready。此时请点击 Visit ，即可跳转到部署好的网站地址，此地址即为你的服务端地址。
点击顶部的 Settings - Domains 进入域名配置页
输入需要绑定的域名并点击 Add
在域名服务器商处添加新的 CNAME 解析记录
| Type | Name | Value | +|
+string类型: (WalineEmojiInfo | WalineEmojiPresets)[] | false
type WalineEmojiPresets = `http://${string}` | `https://${string}`
+
+interface WalineEmojiInfo {
+ /**
+ * 选项卡上的 Emoji 名称
+ */
+ name: string
+ /**
+ * 所在文件夹链接
+ */
+ folder?: string
+ /**
+ * Emoji 通用路径前缀
+ */
+ prefix?: string
+ /**
+ * Emoji 图片的类型，会作为文件扩展名使用
+ */
+ type?: string
+ /**
+ * 选项卡显示的 Emoji 图标
+ */
+ icon: string
+ /**
+ * Emoji 图片列表
+ */
+ items: string[]
+}
+默认值: ['//unpkg.com/@waline/emojis@1.1.0/weibo']
参考：
+详情：表情设置
+类型: string | boolean
默认值: false
参考：
+详情：
+暗黑模式适配。
+'auto' 会根据设备暗黑模式自适应。类型: WalineCommentSorting
默认值: 'latest'
详情：
+评论列表排序方式。可选值: 'latest', 'oldest', 'hottest'
类型: string[]
默认值: ['nick', 'mail', 'link']
详情：
+评论者相关属性。可选值: 'nick', 'mail', 'link'
类型: string[]
默认值: []
详情：
+设置必填项，默认匿名，可选值:
+[]['nick']['nick', 'mail']string'enable'登录模式状态，可选值:
+'enable': 启用登录 (默认)'disable': 禁用登录，用户只能填写信息评论'force': 强制登录，用户必须注册并登录才可发布评论类型: number | [number, number]
默认值: 0
详情：
+评论字数限制。填入单个数字时为最大字数限制。设置为 0 时无限制。
number10类型: WalineImageUploader | false
详情:
+type WalineImageUploader = (image: File) => Promise<string>
+参考:
+ +详情：
+自定义图片上传方法。默认行为是将图片 Base 64 编码嵌入，你可以设置为 false 以禁用图片上传功能。
函数应该接收图片对象，返回一个提供图片地址的 Promise。
+类型: WalineHighlighter | false
type WalineHighlighter = (code: string, lang: string) => string
+参考:
+ +详情：
+代码高亮，默认使用一个 < 1kb 的简单高亮器。函数传入代码块的原始字符和代码块的语言。你应该直接返回一个字符串。
+你可以传入一个自己的代码高亮器，也可以设置为 false 以禁用代码高亮功能。
类型: WalineTexRenderer | false
type WalineTexRenderer = (blockMode: boolean, tex: string) => string
+参考:
+ +详情：
+自定义 TeX 渲染，默认行为是提示预览模式不支持 TeX。函数提供两个参数，第一个参数表示渲染模式是否为块级，第二个参数是 TeX 的字符串，并返回一段 HTML 字符串作为渲染结果。
+你可以自行引入 TeX 渲染器并提供预览渲染，建议使用 Katex 或 MathJax，也可以设置为 false 以禁止渲染 TeX。
类型: WalineSearchOptions | false
interface WalineSearchImageData extends Record<string, unknown> {
+ /**
+ * 图片链接
+ */
+ src: string
+
+ /**
+ * 图片标题
+ *
+ * @description 用于图片的 alt 属性
+ */
+ title?: string
+
+ /**
+ * 图片缩略图
+ *
+ * @description 为了更好的加载性能，我们会优先在列表中使用此缩略图
+ *
+ * @default src
+ */
+ preview?: string
+}
+
+type WalineSearchResult = WalineSearchImageData[]
+
+interface WalineSearchOptions {
+ /**
+ * 搜索操作
+ */
+ search: (word: string) => Promise<WalineSearchResult>
+
+ /**
+ * 打开列表时展示的默认结果
+ *
+ * @default () => search('')
+ */
+ default?: () => Promise<WalineSearchResult>
+
+ /**
+ * 获取更多的操作
+ *
+ * @description 会在列表滚动到底部时触发，如果你的搜索服务支持分页功能，你应该设置此项实现无限滚动
+ *
+ * @default (word) => search(word)
+ */
+ more?: (word: string, currentCount: number) => Promise<WalineSearchResult>
+}
+详情：自定义搜索功能，设置 false 可禁用搜索。
类型: string
详情：
+reCAPTCHA V3 是 Google 提供的验证码服务，配置 reCAPTCHA V3 网站密钥即可开启该功能。
+服务端需要同步配置 RECAPTCHA_V3_SECRET 环境变量。
类型: boolean | string[]
默认值: false
详情：
+为文章增加表情互动功能，设置为 true 提供默认表情，也可以通过设置表情地址数组来自定义表情图片，最大支持 8 个表情。
类型: boolean
默认值: true
详情：
+是否导入 Meta 图标。
+类型: WalineLocales
interface WalineLocales {
+ [localePath: string]: WalineLocale
+}
+参考:
+详情：
+Waline 多语言配置
+你可以直接在插件选项中配置可序列化的选项:
+import { defineUserConfig } from 'vuepress'
+import { commentPlugin } from 'vuepress-plugin-comment2'
+
+export default defineUserConfig({
+ plugins: [
+ commentPlugin({
+ provider: 'Waline',
+ // 其他选项
+ // ...
+ }),
+ ],
+})
+你可以使用 defineWalineConfig 函数来配置 Waline。
import { defineClientConfig } from 'vuepress/client'
+import { defineWalineConfig } from 'vuepress-plugin-comment2/client'
+
+defineWalineConfig({
+ // Waline 选项
+})
+
+export default defineClientConfig({
+ // ...
+})
+所有函数都应在 extendsBundlerOptions 生命周期挂钩中调用。
提示
+我们在示例中省略了它。 实际代码应该是这样的：
+// 导入你需要的函数
+import { addCustomElement } from '@vuepress/helper'
+
+export const yourPlugin = {
+ // ...
+ extendsBundlerOptions: (bundlerOptions, app) => {
+ // 在此添加它们
+ addCustomElement(bundlerOptions, app, 'my-custom-element')
+ },
+}
+获取当前打包器的名称。
+export const getBundlerName: (app: App) => string
+// @vuepress/bundler-vite
+getBundleName(app) === 'vite' // true
+// @vuepress/bundler-webpack
+getBundleName(app) === 'webpack' // true
+将自定义元素声明添加到当前的打包器。
+interface CustomElementCommonOptions {
+ app: App;
+ config: unknown;
+}
+/**
+ * Add tags as customElement
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param customElements tags recognized as custom element
+ */
+export const addCustomElement = (
+ bundlerOptions: unknown,
+ app: App,
+ customElement: string[] | string | RegExp
+) => void;
+import { addCustomElement } from '@vuepress/helper'
+
+addCustomElement(bundlerConfig, app, 'my-custom-element')
+addCustomElement(bundlerOptions, app, [
+ 'custom-element1',
+ 'custom-element2',
+ // all tags start with `math-`
+ /^math-/,
+])
+为开发服务器中的特定路径提供内容。
+export interface DevServerOptions {
+ /**
+ * Path to be responded
+ */
+ path: string;
+ /**
+ * Respond function
+ */
+ response: (request?: IncomingMessage) => Promise<string | Buffer>;
+
+ /**
+ * error msg
+ */
+ errMsg?: string;
+}
+
+/**
+ * Handle specific path when running VuePress Dev Server
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param path Path to be responded
+ * @param response respond function
+ * @param errMsg error msg
+ */
+export const customizeDevServer: (
+ bundlerOptions: unknown,
+ app: App,
+ {
+ errMsg:"The server encountered an error",
+ response: responseHandler,
+ path,
+ }: CustomServerOptions
+) => void;
+import { useCustomDevServer } from '@vuepress/helper'
+
+// handle `/api/` path
+useCustomDevServer(bundlerOptions, app, {
+ path: '/api/',
+ response: async () => getData(),
+ errMsg: 'Unexpected api error',
+})
+addViteOptimizeDepsInclude
+向 Vite optimizeDeps.include 列表中添加模块
提示
+如果一个包满足下列条件之一，你应该考虑将它添加至此。
+import() 动态导入addViteOptimizeDepsExclude
+向 Vite optimizeDeps.exclude 列表中添加模块
如果一个包和它的依赖都是纯 ESM 包，你应该考虑将它添加至此。
+addViteSsrExternal
+向 Vite ssr.external 列表中添加模块
如果一个包是纯 ESM 包，且未使用别名 (alias) 或定义变量 (define)，你应该考虑将它添加至此。
+addViteSsrNoExternal
+向 Vite ssr.noExternal 列表中添加模块
如果一个包内使用了别名 (alias) 或定义变量 (define)，你必须将它添加至此。
+/**
+ * Add modules to Vite `optimizeDeps.include` list
+ */
+export const addViteOptimizeDepsInclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `optimizeDeps.exclude` list
+ */
+export const addViteOptimizeDepsExclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.external` list
+ */
+export const addViteSsrExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.noExternal` list
+ */
+export const addViteSsrNoExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+import {
+ addViteOptimizeDepsInclude,
+ addViteOptimizeDepsExclude,
+ addViteSsrExternal,
+ addViteSsrNoExternal,
+} from '@vuepress/helper'
+
+addViteOptimizeDepsInclude(bundlerOptions, app, ['vue', 'vue-router'])
+addViteOptimizeDepsExclude(bundlerOptions, app, 'packageA')
+addViteSsrNoExternal(bundlerOptions, app, ['vue', 'vue-router'])
+addViteSsrExternal(bundlerOptions, app, 'packageA')
+addViteConfig
+A function for you to add vite config
+export const addViteConfig: (
+ bundlerOptions: unknown,
+ app: App,
+ config: Record<string, unknown>,
+) => void
+import { addViteConfig } from '@vuepress/helper'
+
+addViteConfig(bundlerOptions, app, {
+ build: {
+ charset: 'utf8',
+ },
+})
+mergeViteConfig
+无需导入 vite 即可合并 vite 配置的功能
+export const mergeViteConfig: (
+ defaults: Record<string, any>,
+ overrides: Record<string, any>,
+) => Record<string, any>
+注意
+你不应将 vite 作为依赖，因为你的的用户可能选择其他打包器！
+import { mergeViteConfig } from "@vuepress/helper";
+
+config.viteOptions mergeViteConfig(config.viteOptions, {
+ build: {
+ charset: "utf8",
+ },
+});
+chainWebpack
+链式修改 webpack 配置.
+export const chainWebpack: (
+ { app, config }: WebpackCommonOptions,
+ chainWebpack: (
+ config: WebpackChainConfig,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { chainWebpack } from '@vuepress/helper'
+
+chainWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+configWebpack
+配置 Webpack
+export const configWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ configureWebpack: (
+ config: WebpackConfiguration,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { configWebpack } from '@vuepress/helper'
+
+configWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+获取页面摘要。
+export interface PageExcerptOptions {
+ /**
+ * 摘要分隔符
+ *
+ * @default "<!-- more -->"
+ */
+ separator?: string
+
+ /**
+ * 摘要的长度
+ *
+ * @description 摘要的长度会尽可能的接近这个值
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * 被认为是自定义元素的标签
+ *
+ * @description 用于判断一个标签是否是自定义元素，因为在摘要中，所有的未知标签都会被移除。
+ */
+ isCustomElement?: (tagName: string) => boolean
+
+ /**
+ * 是否保留页面标题 (第一个 h1)
+ *
+ * @default false
+ */
+ keepPageTitle?: boolean
+
+ /**
+ * 是否保留代码块的标签，诸如行号和高亮行
+ *
+ * @default false
+ */
+ keepFenceDom?: boolean
+}
+
+export const getPageExcerpt: (
+ app: App,
+ page: Page,
+ options?: PageExcerptOptions,
+) => string
+获取页面纯文本。
+export interface PageTextOptions {
+ /**
+ * 是否将文字转换成单行内容
+ *
+ * @default false
+ */
+ singleLine?: boolean
+
+ /**
+ * 文字的长度
+ *
+ * @description 文字的长度会尽可能的接近这个值
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * 需要移除的标签
+ *
+ * @description 默认情况下表格和代码块会被移除
+ *
+ * @default ['table', 'pre']
+ */
+ removedTags?: string[]
+}
+
+export const getPageText: (
+ app: App,
+ page: Page,
+ options?: PageTextOptions,
+) => string
+| Language: | +
+ |
+
| Published Date: | +
+ |
+
| Last Build Date: | +
+ |
+
| Copyright: | +
+ |
+
| + Catetory: + | +
+ |
+
Props:
'tip' | 'warning' | 'danger''tip'string'''top' | 'middle' | 'bottom' | undefinedundefined示例：
输入
- VuePress - <Badge type="tip" text="v2" vertical="top" />
+- VuePress - <Badge type="warning" text="v2" vertical="middle" />
+- VuePress - <Badge type="danger" text="v2" vertical="bottom" />
+输出
详情：
CodeGroupItem 组件的 Wrapper 。
Props:
stringtruebooleanfalse详情：
该组件必须放置在 CodeGroup 组件的内部。
可以通过 active Prop 来设置初始激活的元素。如果不设置，默认激活第一个元素。
示例：
输入
<CodeGroup>
+ <CodeGroupItem title="pnpm">
+
+```bash:no-line-numbers
+pnpm install
+```
+
+ </CodeGroupItem>
+
+ <CodeGroupItem title="yarn">
+
+```bash:no-line-numbers
+yarn install
+```
+
+ </CodeGroupItem>
+
+ <CodeGroupItem title="npm" active>
+
+```bash:no-line-numbers
+npm install
+```
+
+ </CodeGroupItem>
+</CodeGroup>
+输出
pnpm install
+yarn install
+npm install
+注意
你必须在 <CodeGroupItem> 的开始标签和代码块之间添加一个空行，否则代码块无法被 Markdown 正确解析。
所有内容首先都必须是合法的 Markdown ，然后才是一个 Vue SFC 。
了解更多： Cookbook > Markdown 与 Vue SFC
或者你可以选择使用 自定义容器 。
类型： string
详情：
部署的域名，例如 https://example.com
类型： { [path: string]: Partial<DefaultThemeLocaleData> }
默认值： {}
详情：
多语言支持的各个语言 locales 。
所有在 Locale 配置 章节内的配置项都可以在 locales 中使用。
该配置项仅能在默认主题内生效，注意不要和 站点配置 中的 locales 混淆。
参考：
该章节内的配置项可以作为一般配置使用，也可以使用在 locales 内。
类型： 'auto' | 'light' | 'dark'
默认值： 'auto'
详情：
默认颜色模式。
如果设置为 'auto' ，则会根据 prefers-color-scheme 自动设置初始颜色模式。
参考：
类型： boolean
默认值： true
详情：
是否启用切换颜色模式的功能。
如果设置为 true ，将会在导航栏展示一个切换颜色模式的按钮。
参考：
类型： string
默认值： /
详情：
首页的路径。
它将被用于：
类型： false | (NavbarItem | NavbarGroup | string)[]
默认值： []
详情：
导航栏配置。
设置为 false 可以禁用导航栏。
为了配置导航栏元素，你可以将其设置为 导航栏数组 ，其中的每个元素是 NavbarItem 对象、 NavbarGroup 对象、或者字符串：
NavbarItem 对象应该有一个 text 字段和一个 link 字段，还有一个可选的 activeMatch 字段。NavbarGroup 对象应该有一个 text 字段和一个 children 字段。 children 字段同样是一个 导航栏数组 。NavbarItem 对象，将页面标题作为 text ，将页面路由路径作为 link 。示例 1：
export default {
+ theme: defaultTheme({
+ navbar: [
+ // NavbarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ },
+ // NavbarGroup
+ {
+ text: 'Group',
+ children: ['/group/foo.md', '/group/bar.md'],
+ },
+ // 字符串 - 页面文件路径
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ navbar: [
+ // 嵌套 Group - 最大深度为 2
+ {
+ text: 'Group',
+ children: [
+ {
+ text: 'SubGroup',
+ children: ['/group/sub/foo.md', '/group/sub/bar.md'],
+ },
+ ],
+ },
+ // 控制元素何时被激活
+ {
+ text: 'Group 2',
+ children: [
+ {
+ text: 'Always active',
+ link: '/',
+ // 该元素将一直处于激活状态
+ activeMatch: '/',
+ },
+ {
+ text: 'Active on /foo/',
+ link: '/not-foo/',
+ // 该元素在当前路由路径是 /foo/ 开头时激活
+ // 支持正则表达式
+ activeMatch: '^/foo/',
+ },
+ ],
+ },
+ ],
+ }),
+}
+类型： null | string
详情：
Logo 图片的 URL。
Logo 图片将会显示在导航栏的左端。
设置为 null 可以禁用 Logo 。
示例：
export default {
+ theme: defaultTheme({
+ // Public 文件路径
+ logo: '/images/hero.png',
+ // URL
+ logo: 'https://vuejs.org/images/logo.png',
+ }),
+}
+类型： null | string
详情：
在夜间模式中使用的 Logo 图片的 URL。
如果你想在夜间模式中使用不同的 Logo 图片，就可以使用该配置项。
设置为 null 可以在夜间模式下禁用 Logo 。忽略该配置项将会在夜间模式中使用 logo 配置。
参考：
类型：null | string
详情：
指定 Logo 图片的替代文字。
当未指定时，将默认与站点标题相同。
类型： string
详情：
项目仓库的 URL。
它将被用作 仓库链接 的链接。仓库链接 将会显示为导航栏的最后一个元素。
export default {
+ theme: defaultTheme({
+ // 如果你按照 `organization/repository` 的格式设置它
+ // 我们会将它作为一个 GitHub 仓库
+ repo: 'vuejs/vuepress',
+ // 你也可以直接将它设置为一个 URL
+ repo: 'https://gitlab.com/foo/bar',
+ }),
+}
+类型： false | 'auto' | SidebarConfigArray | SidebarConfigObject
默认值： 'auto'
详情：
侧边栏配置。
你可以通过页面的 sidebar frontmatter 来覆盖这个全局配置。
设置为 false 可以禁用侧边栏。
如果你设置为 'auto'，侧边栏会根据页面标题自动生成。
为了手动配置侧边栏元素，你可以将其设置为 侧边栏数组 ，其中的每个元素是一个 SidebarItem 对象或者一个字符串：
SidebarItem 对象应该有一个 text 字段，有一个可选的 link 字段、一个可选的 children 字段和一个可选的 collapsible 字段。 children 字段同样是一个 侧边栏数组 。 collapsible 字段来控制它是否可折叠。SidebarItem 对象，将页面标题作为 text ，将页面路由路径作为 link ，并根据页面小标题自动生成 children 。如果你想在不同子路径中使用不同的侧边栏，你可以将该配置项设置为 侧边栏对象 ：
"heading" 以自动为相应路径生成基于标题的侧边栏。示例 1：
export default {
+ theme: defaultTheme({
+ // 侧边栏数组
+ // 所有页面会使用相同的侧边栏
+ sidebar: [
+ // SidebarItem
+ {
+ text: 'Foo',
+ link: '/foo/',
+ children: [
+ // SidebarItem
+ {
+ text: 'github',
+ link: 'https://github.com',
+ children: [],
+ },
+ // 字符串 - 页面文件路径
+ '/foo/bar.md',
+ ],
+ },
+ // 字符串 - 页面文件路径
+ '/bar/README.md',
+ ],
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // 侧边栏对象
+ // 不同子路径下的页面会使用不同的侧边栏
+ sidebar: {
+ '/guide/': [
+ {
+ text: 'Guide',
+ children: ['/guide/introduction.md', '/guide/getting-started.md'],
+ },
+ ],
+ '/reference/': 'heading',
+ },
+ }),
+}
+export default {
+ theme: defaultTheme({
+ // 可折叠的侧边栏
+ sidebar: {
+ '/reference/': [
+ {
+ text: 'VuePress Reference',
+ collapsible: true,
+ children: ['/reference/cli.md', '/reference/config.md'],
+ },
+ {
+ text: 'Bundlers Reference',
+ collapsible: true,
+ children: [
+ '/reference/bundler/vite.md',
+ '/reference/bundler/webpack.md',
+ ],
+ },
+ ],
+ },
+ }),
+}
+类型： number
默认值： 2
详情：
设置根据页面标题自动生成的侧边栏的最大深度。
0 来禁用所有级别的页面标题。1 来包含 <h2> 标题。2 来包含 <h2> 和 <h3> 标题。最大值取决于你通过 markdown.headers.level 提取了哪些级别的标题。
由于 markdown.headers.level 的默认值是 [2, 3] ，因此 sidebarDepth 的默认最大值是 2 。
你可以通过页面的 sidebarDepth frontmatter 来覆盖这个全局配置。
类型： boolean
默认值： true
详情：
是否启用 编辑此页 链接。
你可以通过页面的 editLink frontmatter 来覆盖这个全局配置。
类型： string
详情：
编辑此页 链接的 Pattern 。
它将会用于生成 编辑此页 的链接。
如果你不设置该选项，则会根据 docsRepo 配置项来推断 Pattern 。但是如果你的文档仓库没有托管在常用的平台上，比如 GitHub 、 GitLab 、 Bitbucket 、 Gitee 等，那么你必须设置该选项才能使 编辑此页 链接正常工作。
用法：
| Pattern | 描述 |
|---|---|
:repo | 文档仓库 URL ，即 docsRepo |
:branch | 文档仓库分支 ，即 docsBranch |
:path | 页面源文件的路径，即 docsDir 拼接上页面文件的相对路径 |
示例：
export default {
+ theme: defaultTheme({
+ docsRepo: 'https://gitlab.com/owner/name',
+ docsBranch: 'master',
+ docsDir: 'docs',
+ editLinkPattern: ':repo/-/edit/:branch/:path',
+ }),
+}
+则会生成类似于 'https://gitlab.com/owner/name/-/edit/master/docs/path/to/file.md' 的链接。
类型： string
详情：
文档源文件的仓库 URL 。
它将会用于生成 编辑此页 的链接。
如果你不设置该选项，则默认会使用 repo 配置项。但是如果你的文档源文件是在一个不同的仓库内，你就需要设置该配置项了。
类型： string
默认值： 'main'
详情：
文档源文件的仓库分支。
它将会用于生成 编辑此页 的链接。
类型： string
默认值： ''
详情：
文档源文件存放在仓库中的目录名。
它将会用于生成 编辑此页 的链接。
类型： boolean
默认值： true
详情：
是否启用 最近更新时间戳 。
你可以通过页面的 lastUpdated frontmatter 来覆盖这个全局配置。要注意的是，如果你已经将该选项设为了 false ，那么这个功能会被完全禁用，并且无法在 locales 或页面 frontmatter 中启用。
类型： boolean
默认值： true
详情：
是否启用 贡献者列表 。
你可以通过页面的 contributors frontmatter 来覆盖这个全局配置。要注意的是，如果你已经将该选项设为了 false ，那么这个功能会被完全禁用，并且无法在 locales 或页面 frontmatter 中启用。
VuePress 默认主题有着大量的用户，因此我们对它进行了一些便于继承的设计，以便用户轻松进行定制化。
默认主题的 Layout 布局提供了一些插槽：
navbarnavbar-beforenavbar-aftersidebarsidebar-topsidebar-bottompagepage-toppage-bottompage-content-toppage-content-bottom在它们的帮助下，你可以很容易地添加或替换内容。下面通过一个示例来介绍一下如何使用布局插槽来继承默认主题。
首先，创建一个客户端配置文件 .vuepress/client.ts ：
import { defineClientConfig } from 'vuepress/client'
+import Layout from './layouts/Layout.vue'
+
+export default defineClientConfig({
+ layouts: {
+ Layout,
+ },
+})
+接下来，创建 .vuepress/layouts/Layout.vue ，并使用由默认主题的 Layout 布局提供的插槽：
<script setup>
+import ParentLayout from '@vuepress/theme-default/layouts/Layout.vue'
+</script>
+
+<template>
+ <ParentLayout>
+ <template #page-bottom>
+ <div class="my-footer">This is my custom page footer</div>
+ </template>
+ </ParentLayout>
+</template>
+
+<style lang="css">
+.my-footer {
+ text-align: center;
+}
+</style>
+此时默认的 Layout 布局已经被你的本地布局覆盖，将会在除了首页外的所有页面添加一个自定义的页脚：
布局插槽十分实用，但有时候你可能会觉得它不够灵活。默认主题同样提供了替换单个组件的能力。
默认主题将所有 非全局的组件 都注册了一个带 @theme 前缀的 alias 。例如，HomeFooter.vue 的别名是 @theme/HomeFooter.vue 。
接下来，如果你想要替换 HomeFooter.vue 组件，只需要在配置文件 .vuepress/config.ts 中覆盖这个别名即可：
import { defaultTheme } from '@vuepress/theme-default'
+import { getDirname, path } from 'vuepress/utils'
+import { defineUserConfig } from 'vuepress'
+
+const __dirname = getDirname(import.meta.url)
+
+export default defineUserConfig({
+ theme: defaultTheme(),
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+})
+除了在 .vuepress/config.ts 和 .vuepress/client.ts 中直接扩展默认主题以外，你可以通过继承默认主题来开发一个你自己的主题：
import { defaultTheme, type DefaultThemeOptions } from '@vuepress/theme-default'
+import type { Theme } from 'vuepress/core'
+import { getDirname, path } from 'vuepress/utils'
+
+const __dirname = getDirname(import.meta.url)
+
+export const childTheme = (options: DefaultThemeOptions): Theme => {
+ return {
+ name: 'vuepress-theme-child',
+ extends: defaultTheme(options),
+
+ // 在子主题的客户端配置文件中覆盖布局
+ // 注意，你在发布到 NPM 之前会将 TS 构建为 JS ，因此这里需要设置为 JS 文件的路径
+ clientConfigFile: path.resolve(__dirname, './client.js'),
+
+ // 覆盖组件别名
+ alias: {
+ '@theme/HomeFooter.vue': path.resolve(
+ __dirname,
+ './components/MyHomeFooter.vue',
+ ),
+ },
+ }
+}
+本章节中的 Frontmatter 会在所有类型的页面中生效。
类型： boolean
详情：
参考：
类型： boolean
详情：
是否在当前页面展示导航栏。
如果你在主题配置中禁用了导航栏，那么该 Frontmatter 将不会生效。
参考：
类型： string
详情：
为当前页面添加额外的类名。
示例：
---
+pageClass: custom-page-class
+---
+然后你可以在 .vuepress/styles/index.scss 文件中为这个页面添加自定义样式：
.theme-container.custom-page-class {
+ /* 页面样式 */
+}
+本章节中的 Frontmatter 只会在首页中生效。
类型： boolean
详情：
设定该页面是首页还是普通页面。
如果你不设置该 Frontmatter 或将其设为 false ，则该页面会是一个 普通页面
示例：
---
+home: true
+---
+类型： string
详情：
首页图片的 URL 。
示例：
---
+# Public 文件路径
+heroImage: /images/hero.png
+# URL
+heroImage: https://vuejs.org/images/logo.png
+---
+参考：
类型： string
详情：
在夜间模式中使用的首页图片的 URL 。
如果你想在夜间模式中使用不同的首页图片，就可以使用该配置项。
参考：
类型： string
详情：
首页图片的 alt 属性。
如果不设置，则默认使用 heroText 。
类型： number
默认值： 280
详情：
首页图片 <img> 标签的 height 属性。
当你的首页图片高度小于默认值时，你可能需要减小该属性。
需要注意的是，首页图片的高度同样受到了 CSS 的约束。设置这个属性主要是为了减少由加载首页图片引起的 累积布局偏移 (CLS) 。
类型： string | null
详情：
首页的大标题。
如果不设置，则默认使用站点 title 。
设置为 null 来禁用首页大标题。
类型： string | null
详情：
首页的标语。
如果不设置，则默认使用站点 description 。
设置为 null 来禁用首页标语。
Array<{
+ text: string
+ link: string
+ type?: 'primary' | 'secondary'
+}>
+详情：
配置首页按钮。
示例：
---
+actions:
+ - text: 快速上手
+ link: /zh/guide/getting-started.html
+ type: primary
+ - text: 项目简介
+ link: /zh/guide/introduction.html
+ type: secondary
+---
+Array<{
+ title: string
+ details: string
+}>
+详情：
配置首页特性列表。
示例：
---
+features:
+ - title: 简洁至上
+ details: 以 Markdown 为中心的项目结构，以最少的配置帮助你专注于写作。
+ - title: Vue 驱动
+ details: 享受 Vue 的开发体验，可以在 Markdown 中使用 Vue 组件，又可以使用 Vue 来开发自定义主题。
+ - title: 高性能
+ details: VuePress 会为每个页面预渲染生成静态的 HTML，同时，每个页面被加载的时候，将作为 SPA 运行。
+---
+类型： string
详情：
首页的页脚。
类型： boolean
详情：
是否允许页脚中使用 HTML 。
如果设置为 true ，那么 footer 会被作为 HTML 代码处理。
本章节中的 Frontmatter 只会在普通页面中生效。
类型： boolean
详情：
是否在本页面中启用 编辑此页 链接。
参考：
类型： string
详情：
本页面中 编辑此页 链接的 Pattern 。
参考：
类型： boolean
详情：
是否在本页面中启用 最近更新时间戳 。
参考：
类型： boolean
详情：
是否在本页面中启用 贡献者列表 。
参考：
类型： false | 'auto' | SidebarConfigArray | SidebarConfigObject
详情：
配置本页面的侧边栏。
参考：
类型： number
详情：
配置本页面的侧边栏深度。
参考：
类型： NavLink | string
详情：
上一个页面的链接。
如果你不设置该 Frontmatter ，该链接会自动根据侧边栏配置进行推断。
为了手动配置上一页面的链接，你可以将其设置为一个 NavLink 对象或者一个字符串：
NavLink 对象应该有一个 text 字段和一个 link 字段。NavLink 对象，将页面标题作为 text ，将页面路由路径作为 link 。示例：
---
+# NavLink
+prev:
+ text: Get Started
+ link: /guide/getting-started.html
+
+# NavLink - 外部 URL
+prev:
+ text: GitHub
+ link: https://github.com
+
+# 字符串 - 页面文件路径
+prev: /guide/getting-started.md
+
+# 字符串 - 页面文件相对路径
+prev: ../../guide/getting-started.md
+---
+类型： NavLink | string
详情：
下一个页面的链接。
如果你不设置该 Frontmatter ，该链接会自动根据侧边栏配置进行推断。
类型和 prev Frontmatter 相同。
这些选项用于配置与语言相关的文本。
如果你的站点是以英语以外的其他语言提供服务的，你应该为每个语言设置这些选项来提供翻译。
类型： string
详情：
项目仓库的标签。
它将被用作 仓库链接 的文字。仓库链接 将会显示为导航栏的最后一个元素。
如果你不明确指定该配置项，它将会根据 repo 配置项自动推断。
类型： string
详情：
选择语言菜单 的文字。
如果你在站点配置中设置了多个 locales ，那么 选择语言菜单 就会显示在导航栏中仓库按钮的旁边。
类型： string
详情：
选择语言菜单 的 aria-label 属性。
它主要是为了站点的可访问性 (a11y) 。
类型： string
详情：
Locale 的语言名称。
该配置项 仅能在主题配置的 locales 的内部生效 。它将被用作 locale 的语言名称，展示在 选择语言菜单 内。
示例：
export default {
+ locales: {
+ '/': {
+ lang: 'en-US',
+ },
+ '/zh/': {
+ lang: 'zh-CN',
+ },
+ },
+ theme: defaultTheme({
+ locales: {
+ '/': {
+ selectLanguageName: 'English',
+ },
+ '/zh/': {
+ selectLanguageName: '简体中文',
+ },
+ },
+ }),
+}
+类型：null | string
详情：
导航栏中主导航 aria-label 属性的值。
类型：null | string
详情：
下一页/上一页导航 aria-label 属性的值
类型： string
默认值： 'Edit this page'
详情：
编辑此页 链接的文字。
类型： string
默认值： 'Last Updated'
详情：
最近更新时间戳 标签的文字。
类型： string
默认值： 'Contributors'
详情：
贡献者列表 标签的文字。
类型： string
默认值： 'TIP'
详情：
Tip 自定义容器 的默认标题。
类型： string
默认值： 'WARNING'
详情：
Warning 自定义容器 的默认标题。
类型： string
默认值： 'DANGER'
详情：
Danger 自定义容器 的默认标题。
类型： string[]
默认值： ['Not Found']
详情：
404 页面的提示信息。
当用户进入 404 页面时，会从数组中随机选取一条信息进行展示。
类型： string
默认值： 'Back to home'
详情：
404 页面中 返回首页 链接的文字。
类型： string
默认值： 'open in new window'
详情：
ExternalLinkIcon. 链接内的 sr-only 文字。
它主要是为了站点的可访问性 (a11y) 。
参考：
类型： string
默认值： 'toggle color mode'
详情：
切换颜色模式按钮的标题文字。
它主要是为了站点的可访问性 (a11y) 。
参考：
类型： string
默认值： 'toggle sidebar'
详情：
切换侧边栏按钮的标题文字。
它主要是为了站点的可访问性 (a11y) 。
类型： string
默认值： 'Prev'
详情：
上一页按钮的文字。
类型： string
默认值： 'Next'
详情：
下一页按钮的文字。
使用：
::: <type> [title]
+[content]
+:::
+type 是必需的， title 和 content 是可选的。
支持的 type 有：
tipwarningdangerdetailscode-groupcode-group-item示例 1 （默认标题）：
输入
::: tip
+这是一个提示
+:::
+
+::: warning
+这是一个警告
+:::
+
+::: danger
+这是一个危险警告
+:::
+
+::: details
+这是一个 details 标签
+:::
+输出
提示
这是一个提示
注意
这是一个警告
警告
这是一个危险警告
这是一个 details 标签
输入
::: danger STOP
+危险区域，禁止通行
+:::
+
+::: details 点击查看代码
+
+```ts
+console.log('你好，VuePress！')
+```
+
+:::
+输出
STOP
危险区域，禁止通行
console.log('你好，VuePress！')
+输入
:::: code-group
+::: code-group-item FOO
+
+```ts
+const foo = 'foo'
+```
+
+:::
+
+::: code-group-item BAR
+
+```ts
+const bar = 'bar'
+```
+
+:::
+::::
+输出
const foo = 'foo'
+const bar = 'bar'
+你可以通过 themePlugins 设置默认主题使用的插件。
默认主题使用了一些插件，如果你确实不需要该插件，你可以选择禁用它。在禁用插件之前，请确保你已了解它的用途。
import { defaultTheme } from '@vuepress/theme-default'
+
+export default {
+ theme: defaultTheme({
+ themePlugins: {
+ // 在这里自定义主题插件
+ },
+ }),
+}
+类型： boolean
默认值： true
详情：
类型： BackToTopPluginOptions | boolean
默认值： true
详情：
是否启用 @vuepress/plugin-back-to-top 。
支持对象格式以作为插件选项。
类型： Record<ContainerType, boolean>
详情：
是否启用由 @vuepress/plugin-container 支持的自定义容器。
ContainerType 类型为：
tipwarningdangerdetailscodeGroupcodeGroupItem参考：
类型： CopyCodePluginOptions | boolean
默认值： true
详情：
是否启用 @vuepress/plugin-copy-code 。
支持对象格式以作为插件选项。
类型： boolean
默认值： true
详情：
类型： boolean
默认值： true
详情：
是否启用 @vuepress/plugin-git 。
类型： boolean
默认值： true
详情：
是否启用 @vuepress/plugin-links-check 。
类型： boolean
默认值： true
详情：
是否启用 @vuepress/plugin-medium-zoom 。
类型： boolean
默认值： true
详情：
是否启用 @vuepress/plugin-nprogress 。
类型： boolean
默认值： true
详情：
是否启用 @vuepress/plugin-prismjs 。
类型： SeoPluginOptions | boolean
默认值： true
详情：
是否启用 @vuepress/plugin-seo 。
支持对象格式以作为插件选项。
类型： SitemapPluginOptions | boolean
默认值： true
详情：
是否启用 @vuepress/plugin-sitemap 。
支持对象格式以作为插件选项。
默认主题使用 SASS 作为 CSS 预处理器。
用户可以通过 palette 文件 来自定义样式变量，还可以通过 style 文件 来添加额外的样式。
Palette 文件的路径是 .vuepress/styles/palette.scss 。
你可以利用它来覆盖默认主题的预定义 SASS 变量。
// responsive breakpoints
+$MQNarrow: 959px !default;
+$MQMobile: 719px !default;
+$MQMobileNarrow: 419px !default;
+Style 文件的路径是 .vuepress/styles/index.scss 。
你可以在这里添加额外的样式，或者覆盖默认样式：
:root {
+ scroll-behavior: smooth;
+}
+你也可以利用它来覆盖默认主题的预定义 CSS 变量。
:root {
+ // brand colors
+ --c-brand: #3eaf7c;
+ --c-brand-light: #4abf8a;
+
+ // background colors
+ --c-bg: #ffffff;
+ --c-bg-light: #f3f4f5;
+ --c-bg-lighter: #eeeeee;
+ --c-bg-dark: #ebebec;
+ --c-bg-darker: #e6e6e6;
+ --c-bg-navbar: var(--c-bg);
+ --c-bg-sidebar: var(--c-bg);
+ --c-bg-arrow: #cccccc;
+
+ // text colors
+ --c-text: #2c3e50;
+ --c-text-accent: var(--c-brand);
+ --c-text-light: #3a5169;
+ --c-text-lighter: #4e6e8e;
+ --c-text-lightest: #6a8bad;
+ --c-text-quote: #999999;
+
+ // border colors
+ --c-border: #eaecef;
+ --c-border-dark: #dfe2e5;
+
+ // custom container colors
+ --c-tip: #42b983;
+ --c-tip-bg: var(--c-bg-light);
+ --c-tip-title: var(--c-text);
+ --c-tip-text: var(--c-text);
+ --c-tip-text-accent: var(--c-text-accent);
+ --c-warning: #ffc310;
+ --c-warning-bg: #fffae3;
+ --c-warning-bg-light: #fff3ba;
+ --c-warning-bg-lighter: #fff0b0;
+ --c-warning-border-dark: #f7dc91;
+ --c-warning-details-bg: #fff5ca;
+ --c-warning-title: #f1b300;
+ --c-warning-text: #746000;
+ --c-warning-text-accent: #edb100;
+ --c-warning-text-light: #c1971c;
+ --c-warning-text-quote: #ccab49;
+ --c-danger: #f11e37;
+ --c-danger-bg: #ffe0e0;
+ --c-danger-bg-light: #ffcfde;
+ --c-danger-bg-lighter: #ffc9c9;
+ --c-danger-border-dark: #f1abab;
+ --c-danger-details-bg: #ffd4d4;
+ --c-danger-title: #ed1e2c;
+ --c-danger-text: #660000;
+ --c-danger-text-accent: #bd1a1a;
+ --c-danger-text-light: #b5474d;
+ --c-danger-text-quote: #c15b5b;
+ --c-details-bg: #eeeeee;
+
+ // badge component colors
+ --c-badge-tip: var(--c-tip);
+ --c-badge-warning: #ecc808;
+ --c-badge-warning-text: var(--c-bg);
+ --c-badge-danger: #dc2626;
+ --c-badge-danger-text: var(--c-bg);
+
+ // code group colors
+ --c-code-group-tab-title: rgba(255, 255, 255, 0.9);
+ --c-code-group-tab-bg: var(--code-bg-color);
+ --c-code-group-tab-outline: var(var(--c-code-group-tab-title));
+ --c-code-group-tab-active-border: var(--c-brand);
+
+ // transition vars
+ --t-color: 0.3s ease;
+ --t-transform: 0.3s ease;
+
+ // code blocks vars
+ --code-bg-color: #282c34;
+ --code-hl-bg-color: rgba(0, 0, 0, 0.66);
+ --code-ln-color: #9e9e9e;
+ --code-ln-wrapper-width: 3.5rem;
+
+ // font vars
+ --font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen,
+ Ubuntu, Cantarell, 'Fira Sans', 'Droid Sans', 'Helvetica Neue', sans-serif;
+ --font-family-code: Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono', monospace;
+
+ // layout vars
+ --navbar-height: 3.6rem;
+ --navbar-padding-v: 0.7rem;
+ --navbar-padding-h: 1.5rem;
+ --sidebar-width: 20rem;
+ --sidebar-width-mobile: calc(var(--sidebar-width) * 0.82);
+ --content-width: 740px;
+ --homepage-width: 960px;
+}
+
+// plugin-back-to-top
+.vp-back-to-top-button {
+ --back-to-top-color: var(--c-brand);
+ --back-to-top-color-hover: var(--c-brand-light);
+ --back-to-top-bg-color: var(--c-bg);
+}
+
+// plugin-catalog
+.vp-catalog-wrapper {
+ --catalog-bg-color: var(--c-bg);
+ --catalog-bg-secondary-color: var(--c-bg-dark);
+ --catalog-border-color: var(--c-border);
+ --catalog-active-color: var(--c-brand);
+ --catalog-hover-color: var(--c-brand-light);
+}
+
+// plugin-comment
+.waline-wrapper {
+ --waline-bg-color: var(--c-bg);
+ --waline-bg-color-light: var(--c-bg-light);
+ --waline-text-color: var(--c-color);
+ --waline-border: 1px solid var(--c-border);
+ --waline-border-color: var(--c-border);
+ --waline-theme-color: var(--c-brand);
+ --waline-active-color: var(--c-brand-light);
+}
+
+// plugin-docsearch
+.DocSearch {
+ --docsearch-primary-color: var(--c-brand);
+ --docsearch-text-color: var(--c-text);
+ --docsearch-highlight-color: var(--c-brand);
+ --docsearch-muted-color: var(--c-text-quote);
+ --docsearch-container-background: rgba(9, 10, 17, 0.8);
+ --docsearch-modal-background: var(--c-bg-light);
+ --docsearch-searchbox-background: var(--c-bg-lighter);
+ --docsearch-searchbox-focus-background: var(--c-bg);
+ --docsearch-searchbox-shadow: inset 0 0 0 2px var(--c-brand);
+ --docsearch-hit-color: var(--c-text-light);
+ --docsearch-hit-active-color: var(--c-bg);
+ --docsearch-hit-background: var(--c-bg);
+ --docsearch-hit-shadow: 0 1px 3px 0 var(--c-border-dark);
+ --docsearch-footer-background: var(--c-bg);
+}
+
+// plugin-external-link-icon
+.external-link-icon {
+ --external-link-icon-color: var(--c-text-quote);
+}
+
+// plugin-medium-zoom
+.medium-zoom-overlay {
+ --medium-zoom-bg-color: var(--c-bg);
+}
+
+// plugin-nprogress
+#nprogress {
+ --nprogress-color: var(--c-brand);
+}
+
+// plugin-photo-swipe
+body {
+ --photo-swipe-bullet: var(--c-bg);
+ --photo-swipe-bullet-active: var(--c-brand);
+}
+
+// plugin-pwa-popup
+body {
+ --pwa-text-color: var(--c-text);
+ --pwa-bg-color: var(--c-bg);
+ --pwa-border-color: var(--c-brand);
+ --pwa-btn-text-color: var(--c-bg);
+ --pwa-btn-bg-color: var(--c-brand);
+ --pwa-btn-hover-bg-color: var(--c-brand-light);
+}
+
+// plugin-redirect
+.language-modal-mask {
+ --redirect-bg-color: var(--c-bg);
+ --redirect-bg-color-light: var(--c-bg-light);
+ --redirect-bg-color-lighter: var(--c-bg-lighter);
+ --redirect-text-color: var(--c-text);
+ --redirect-primary-color: var(--c-brand);
+ --redirect-primary-hover-color: var(--c-brand-light);
+ --redirect-primary-text-color: var(--c-bg);
+}
+
+// plugin-search
+.search-box {
+ --search-bg-color: var(--c-bg);
+ --search-accent-color: var(--c-brand);
+ --search-text-color: var(--c-text);
+ --search-border-color: var(--c-border);
+
+ --search-item-text-color: var(--c-text-lighter);
+ --search-item-focus-bg-color: var(--c-bg-light);
+}
+html.dark {
+ // brand colors
+ --c-brand: #3aa675;
+ --c-brand-light: #349469;
+
+ // background colors
+ --c-bg: #22272e;
+ --c-bg-light: #2b313a;
+ --c-bg-lighter: #262c34;
+ --c-bg-dark: #343b44;
+ --c-bg-darker: #37404c;
+
+ // text colors
+ --c-text: #adbac7;
+ --c-text-light: #96a7b7;
+ --c-text-lighter: #8b9eb0;
+ --c-text-lightest: #8094a8;
+
+ // border colors
+ --c-border: #3e4c5a;
+ --c-border-dark: #34404c;
+
+ // custom container colors
+ --c-tip: #318a62;
+ --c-warning: #e0ad15;
+ --c-warning-bg: #2d2f2d;
+ --c-warning-bg-light: #423e2a;
+ --c-warning-bg-lighter: #44442f;
+ --c-warning-border-dark: #957c35;
+ --c-warning-details-bg: #39392d;
+ --c-warning-title: #fdca31;
+ --c-warning-text: #d8d96d;
+ --c-warning-text-accent: #ffbf00;
+ --c-warning-text-light: #ddb84b;
+ --c-warning-text-quote: #ccab49;
+ --c-danger: #fc1e38;
+ --c-danger-bg: #39232c;
+ --c-danger-bg-light: #4b2b35;
+ --c-danger-bg-lighter: #553040;
+ --c-danger-border-dark: #a25151;
+ --c-danger-details-bg: #482936;
+ --c-danger-title: #fc2d3b;
+ --c-danger-text: #ea9ca0;
+ --c-danger-text-accent: #fd3636;
+ --c-danger-text-light: #d9777c;
+ --c-danger-text-quote: #d56b6b;
+ --c-details-bg: #323843;
+
+ // badge component colors
+ --c-badge-warning: var(--c-warning);
+ --c-badge-warning-text: #3c2e05;
+ --c-badge-danger: var(--c-danger);
+ --c-badge-danger-text: #401416;
+
+ // code blocks vars
+ --code-hl-bg-color: #363b46;
+}
+
+// plugin-docsearch
+html.dark .DocSearch {
+ --docsearch-logo-color: var(--c-text);
+ --docsearch-modal-shadow: inset 1px 1px 0 0 #2c2e40, 0 3px 8px 0 #000309;
+ --docsearch-key-shadow: inset 0 -2px 0 0 #282d55, inset 0 0 1px 1px #51577d,
+ 0 2px 2px 0 rgba(3, 4, 9, 0.3);
+ --docsearch-key-gradient: linear-gradient(-225deg, #444950, #1c1e21);
+ --docsearch-footer-shadow: inset 0 1px 0 0 rgba(73, 76, 106, 0.5),
+ 0 -4px 8px 0 rgba(0, 0, 0, 0.2);
+}
+
+// plugin-pwa
+html.dark body {
+ --pwa-shadow-color: rgb(0 0 0 / 30%);
+ --pwa-content-color: #ccc;
+ --pwa-content-light-color: #999;
+}
+检查组件是否已全局注册。
提示
setup 之外调用时，你需要将 app 实例作为第二个参数传递。export const hasGlobalComponent: (name: string, app?: App) => boolean
+// 如果你全局注册了 `<my-component>`
+hasGlobalComponent('MyComponent') // true
+hasGlobalComponent('my-component') // true
+
+hasGlobalComponent('MyComponent2') // false
+从语言环境设置中获取当前语言环境配置。
export const useLocaleConfig: <T extends LocaleData>(
+ localesConfig: RequiredLocaleConfig<T>,
+) => ComputedRef<T>
+const localesCOnfig = {
+ '/': 'Title',
+ '/zh/': '标题',
+}
+
+const locale = useLocaleConfig(localesConfig)
+
+// under `/page`
+locale.value // 'Title'
+
+// under `/zh/page`
+locale.value // '标题'
+此包为 VuePress 开发者提供辅助函数。
@vuepress/helper: Node.js 一侧的辅助函数。
@vuepress/helper/client: 客户端一侧的辅助函数。
@vuepress/helper/shared: Node.js 和客户端共享的辅助函数。
打包器函数用于在主题和插件中追加或修改打包器选项。
所有函数都应在 extendsBundlerOptions 生命周期挂钩中调用。
提示
我们在示例中省略了它。 实际代码应该是这样的：
// 导入你需要的函数
+import { addCustomElement } from '@vuepress/helper'
+
+export const yourPlugin = {
+ // ...
+ extendsBundlerOptions: (bundlerOptions, app) => {
+ // 在此添加它们
+ addCustomElement(bundlerOptions, app, 'my-custom-element')
+ },
+}
+获取当前打包器的名称。
export const getBundlerName: (app: App) => string
+// @vuepress/bundler-vite
+getBundleName(app) === 'vite' // true
+// @vuepress/bundler-webpack
+getBundleName(app) === 'webpack' // true
+将自定义元素声明添加到当前的打包器。
interface CustomElementCommonOptions {
+ app: App;
+ config: unknown;
+}
+/**
+ * Add tags as customElement
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param customElements tags recognized as custom element
+ */
+export const addCustomElement = (
+ bundlerOptions: unknown,
+ app: App,
+ customElement: string[] | string | RegExp
+) => void;
+import { addCustomElement } from '@vuepress/helper'
+
+addCustomElement(bundlerConfig, app, 'my-custom-element')
+addCustomElement(bundlerOptions, app, [
+ 'custom-element1',
+ 'custom-element2',
+ // all tags start with `math-`
+ /^math-/,
+])
+为开发服务器中的特定路径提供内容。
export interface DevServerOptions {
+ /**
+ * Path to be responded
+ */
+ path: string;
+ /**
+ * Respond function
+ */
+ response: (request?: IncomingMessage) => Promise<string | Buffer>;
+
+ /**
+ * error msg
+ */
+ errMsg?: string;
+}
+
+/**
+ * Handle specific path when running VuePress Dev Server
+ *
+ * @param bundlerOptions VuePress Bundler config
+ * @param app VuePress Node App
+ * @param path Path to be responded
+ * @param response respond function
+ * @param errMsg error msg
+ */
+export const customizeDevServer: (
+ bundlerOptions: unknown,
+ app: App,
+ {
+ errMsg:"The server encountered an error",
+ response: responseHandler,
+ path,
+ }: CustomServerOptions
+) => void;
+import { useCustomDevServer } from '@vuepress/helper'
+
+// handle `/api/` path
+useCustomDevServer(bundlerOptions, app, {
+ path: '/api/',
+ response: async () => getData(),
+ errMsg: 'Unexpected api error',
+})
+addViteOptimizeDepsInclude
向 Vite optimizeDeps.include 列表中添加模块
提示
如果一个包满足下列条件之一，你应该考虑将它添加至此。
import() 动态导入addViteOptimizeDepsExclude
向 Vite optimizeDeps.exclude 列表中添加模块
如果一个包和它的依赖都是纯 ESM 包，你应该考虑将它添加至此。
addViteSsrExternal
向 Vite ssr.external 列表中添加模块
如果一个包是纯 ESM 包，且未使用别名 (alias) 或定义变量 (define)，你应该考虑将它添加至此。
addViteSsrNoExternal
向 Vite ssr.noExternal 列表中添加模块
如果一个包内使用了别名 (alias) 或定义变量 (define)，你必须将它添加至此。
/**
+ * Add modules to Vite `optimizeDeps.include` list
+ */
+export const addViteOptimizeDepsInclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `optimizeDeps.exclude` list
+ */
+export const addViteOptimizeDepsExclude: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.external` list
+ */
+export const addViteSsrExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+
+/**
+ * Add modules to Vite `ssr.noExternal` list
+ */
+export const addViteSsrNoExternal: (
+ bundlerOptions: unknown,
+ app: App,
+ module: string | string[],
+) => void
+import {
+ addViteOptimizeDepsInclude,
+ addViteOptimizeDepsExclude,
+ addViteSsrExternal,
+ addViteSsrNoExternal,
+} from '@vuepress/helper'
+
+addViteOptimizeDepsInclude(bundlerOptions, app, ['vue', 'vue-router'])
+addViteOptimizeDepsExclude(bundlerOptions, app, 'packageA')
+addViteSsrNoExternal(bundlerOptions, app, ['vue', 'vue-router'])
+addViteSsrExternal(bundlerOptions, app, 'packageA')
+addViteConfig
A function for you to add vite config
export const addViteConfig: (
+ bundlerOptions: unknown,
+ app: App,
+ config: Record<string, unknown>,
+) => void
+import { addViteConfig } from '@vuepress/helper'
+
+addViteConfig(bundlerOptions, app, {
+ build: {
+ charset: 'utf8',
+ },
+})
+mergeViteConfig
无需导入 vite 即可合并 vite 配置的功能
export const mergeViteConfig: (
+ defaults: Record<string, any>,
+ overrides: Record<string, any>,
+) => Record<string, any>
+注意
你不应将 vite 作为依赖，因为你的的用户可能选择其他打包器！
import { mergeViteConfig } from "@vuepress/helper";
+
+config.viteOptions mergeViteConfig(config.viteOptions, {
+ build: {
+ charset: "utf8",
+ },
+});
+chainWebpack
链式修改 webpack 配置.
export const chainWebpack: (
+ { app, config }: WebpackCommonOptions,
+ chainWebpack: (
+ config: WebpackChainConfig,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { chainWebpack } from '@vuepress/helper'
+
+chainWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+configWebpack
配置 Webpack
export const configWebpack: (
+ bundlerOptions: unknown,
+ app: App,
+ configureWebpack: (
+ config: WebpackConfiguration,
+ isServer: boolean,
+ isBuild: boolean,
+ ) => void,
+) => void
+import { configWebpack } from '@vuepress/helper'
+
+configWebpack(bundlerOptions, app, (config, isServer, isBuild) => {
+ // do some customize here
+})
+这些函数为你的页面生成常见信息。
获取页面摘要。
export interface PageExcerptOptions {
+ /**
+ * 摘要分隔符
+ *
+ * @default "<!-- more -->"
+ */
+ separator?: string
+
+ /**
+ * 摘要的长度
+ *
+ * @description 摘要的长度会尽可能的接近这个值
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * 被认为是自定义元素的标签
+ *
+ * @description 用于判断一个标签是否是自定义元素，因为在摘要中，所有的未知标签都会被移除。
+ */
+ isCustomElement?: (tagName: string) => boolean
+
+ /**
+ * 是否保留页面标题 (第一个 h1)
+ *
+ * @default false
+ */
+ keepPageTitle?: boolean
+
+ /**
+ * 是否保留代码块的标签，诸如行号和高亮行
+ *
+ * @default false
+ */
+ keepFenceDom?: boolean
+}
+
+export const getPageExcerpt: (
+ app: App,
+ page: Page,
+ options?: PageExcerptOptions,
+) => string
+获取页面纯文本。
export interface PageTextOptions {
+ /**
+ * 是否将文字转换成单行内容
+ *
+ * @default false
+ */
+ singleLine?: boolean
+
+ /**
+ * 文字的长度
+ *
+ * @description 文字的长度会尽可能的接近这个值
+ *
+ * @default 300
+ */
+ length?: number
+
+ /**
+ * 需要移除的标签
+ *
+ * @description 默认情况下表格和代码块会被移除
+ *
+ * @default ['table', 'pre']
+ */
+ removedTags?: string[]
+}
+
+export const getPageText: (
+ app: App,
+ page: Page,
+ options?: PageTextOptions,
+) => string
+以下函数在 Node.js 和客户端上均可用。
此方法在 MarkdownIt 插件中很有用。有些时候你可能需要在 Markdown 插件中生成组件，并将复杂的数据写入到组件属性中，一个通常做法是使用 JSON.stringify + encodeURIComponent，并在客户端 decodeURIComponent + JSON.parse。但如果内容包含很多特殊字符，转换结果会很长。
所以我们提供 encodeData 和 decodeData 来压缩和编码内容。
export const encodeData: (
+ data: string,
+ level: DeflateOptions['level'] = 6,
+) => string
+
+export const decodeData: (compressed: string) => string
+const content = `
+{
+ "type": "bar",
+ "data": {
+ "labels": ["Red", "Blue", "Yellow", "Green", "Purple", "Orange"],
+ "datasets": [
+ {
+ "label": "# of Votes",
+ "data": [12, 19, 3, 5, 2, 3],
+ "backgroundColor": [
+ "rgba(255, 99, 132, 0.2)",
+ "rgba(54, 162, 235, 0.2)",
+ "rgba(255, 206, 86, 0.2)",
+ "rgba(75, 192, 192, 0.2)",
+ "rgba(153, 102, 255, 0.2)",
+ "rgba(255, 159, 64, 0.2)"
+ ],
+ "borderColor": [
+ "rgba(255, 99, 132, 1)",
+ "rgba(54, 162, 235, 1)",
+ "rgba(255, 206, 86, 1)",
+ "rgba(75, 192, 192, 1)",
+ "rgba(153, 102, 255, 1)",
+ "rgba(255, 159, 64, 1)"
+ ],
+ "borderWidth": 1
+ }
+ ]
+ },
+ "options": {
+ "scales": {
+ "y": {
+ "beginAtZero": true
+ }
+ }
+ }
+}
+`
+
+const prop = encodeData(content) // "eJyNUsFOwzAMve8rrHABKZqWlg5WxAE4cARxAMHEIV1NmQhNlaaCCe3fcdKtW0sLWGpjxy/v+UV512mlcIyfhTa2hHP4GgHYVYExsEQaxqlMpZWxbwAomaAqY5izO0wZB3apKnTrIyqlP1x2bRBzl9xWplC+eWNkniF7dmw1X4nWsfgaNtwNP2kfgH6Be22x9CPUUQ8yFwEHMeMQcog4UBFuiF0kcvGWGV3l6ZVW2uw0XDCTJfIwiOjYjAhESIcn4+BoT2MLio6pP6V+EBJ6AOSZgsmUwyl9A6ATwoiZn3lYTkTkRkycnuP8TU9ENPqUxuuA9i9BmxTNPy9A/G2/F9I23wtpW++FdIwPKzW2W5Afph+WqX2NQWz313XicT7XhV3qnB5f/ejKhVTYVACrXUqUmC3zC/uERsdgTYUdVr/Qb302+gZxe7S/"
+
+decodeData(prop) // will be the original content
+
+// if you use `encodeURIComponent`, it will be much longer
+encodeURIComponent(content) // '%0A%7B%0A%20%20%22type%22%3A%20%22bar%22%2C%0A%20%20%22data%22%3A%20%7B%0A%20%20%20%20%22labels%22%3A%20%5B%22Red%22%2C%20%22Blue%22%2C%20%22Yellow%22%2C%20%22Green%22%2C%20%22Purple%22%2C%20%22Orange%22%5D%2C%0A%20%20%20%20%22datasets%22%3A%20%5B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%22label%22%3A%20%22%23%20of%20Votes%22%2C%0A%20%20%20%20%20%20%20%20%22data%22%3A%20%5B12%2C%2019%2C%203%2C%205%2C%202%2C%203%5D%2C%0A%20%20%20%20%20%20%20%20%22backgroundColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%200.2)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%200.2)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderColor%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%2099%2C%20132%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(54%2C%20162%2C%20235%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20206%2C%2086%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(75%2C%20192%2C%20192%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(153%2C%20102%2C%20255%2C%201)%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22rgba(255%2C%20159%2C%2064%2C%201)%22%0A%20%20%20%20%20%20%20%20%5D%2C%0A%20%20%20%20%20%20%20%20%22borderWidth%22%3A%201%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%0A%20%20%7D%2C%0A%20%20%22options%22%3A%20%7B%0A%20%20%20%20%22scales%22%3A%20%7B%0A%20%20%20%20%20%20%22y%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22beginAtZero%22%3A%20true%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A'
+isDef(x): 判断 x 是否定义。isBoolean(x): 判断 x 是否为布尔值。isString(x): 判断 x 是否为字符串。isNumber(x): 判断 x 是否为数字。isPlainObject(x): 判断值是否为纯对象。isArray(x): 判断 x 是否为数组isFunction(x): 判断 x 是否为函数。isRegExp(x): 判断 x 是否为正则表达式startsWith(a, b): 判断字符串 a 是否以指定字符串 b 开头endsWith(a, b): 判断字符串 a 是否以指定字符串 b 结尾当 a 不是字符串时返回 false
keys(x): 以数组形式返回对象 x 的键
values(x): 以数组形式返回对象 x 的值
entries(x): 将对象 x 转换为键值对数组。
fromEntries(x): 将键值对数组 x 转换为对象。
deepAssign(x, y, ...): Object.assign 的深度版本。
// or @vuepress/helper/client
+import { deepAssign } from '@vuepress/helper'
+
+const defaultOptions = {
+ optionA: {
+ optionA1: 'defaultOptionA1',
+ optionA2: 'defaultOptionA2',
+ optionA3: 'defaultOptionA3',
+ },
+ optionB: true,
+ optionC: 'optionC',
+}
+
+const userOptions = {
+ optionA: {
+ optionA1: 'optionA1',
+ optionA2: 'optionA2',
+ },
+ optionB: false,
+}
+
+deepAssign(defaultOptions, userOptions)
+// {
+// optionA: {
+// optionA1: "optionA1",
+// optionA2: "optionA2",
+// optionA3: "defaultOptionA3",
+// },
+// optionB: false,
+// optionC: "optionC",
+// }
+getDate(x): 将输入 x 转换为日期，可以支持 Date，时间戳，日期字符串。日期字符串的支持度以环境的 Date.parse 支持度为准。当不能转换为日期时返回 null
getDate('2021-01-01') // a Date object represents 2021-01-01
+getDate(1609459200000) // a Date object represents 2021-01-01
+getDate('2021-01-01T00:00:00.000Z') // a Date object represents 2021-01-01
+getDate('2021/01/01') // a Date object represents 2021-01-01 (might be null in some browsers)
+getDate('invalid date') // null
+getDate(undefined) // null
+getDate(-32) // null
+dateSorter: 将可转换为日期的值从新到旧排序，不能转换为日期的值会在最后。
const arr = [
+ '2020-01-01',
+ 1609459200000,
+ '2022-01-01T00:00:00.000Z',
+ '2023/01/01',
+ 'invalid date',
+ undefined,
+ -32,
+]
+
+arr.sort(dateSorter)
+// [
+// '2023/01/01',
+// '2022-01-01T00:00:00.000Z',
+// 1609459200000,
+// '2020-01-01',
+// 'invalid date',
+// undefined,
+// -32,
+// ]
+isLinkHttp(x): x 是否是有效的 HTTP URL。isLinkWithProtocol(x): x 是否是有效的带有协议的 URL。isLinkExternal(x): x 是否是有效的外部 URL。isLinkAbsolute(x): x 是否是有效的绝对 URL。ensureEndingSlash(x): 确保 x 以斜杠结尾。ensureLeadingSlash(x): 确保 x 以斜杠开头。removeEndingSlash(x): 确保 x 不以斜杠结尾。removeLeadingSlash(x): 确保 x 不以斜杠开头。