Advanced Configuration

Specify Directory

If your demo file and your .md file are not in the same directory, the relative path to reference the demo may be long. You can specify the directory where the demo is located through the demoDir property to simplify the import path.

For example, the following directory structure:

docs
├─ .vitepress
│  └─ config.ts
├─ guide
│  └─ start.md
└─ demos
   ├─ base
   |  └─ demo.html
   ├─ demo.tsx
   └─ demo.vue

Add following code into config.ts：

import { defineConfig } from 'vitepress';
import { vitepressDemoPlugin } from 'vitepress-demo-plugin';
import path from 'path';

export default defineConfig({
  // other configs...
  markdown: {
    config(md) {
      md.use(vitepressDemoPlugin, {
        demoDir: path.resolve(__dirname, '../demos'), 
      });
    },
  },
});

Before Configuring The Specified Directory

Before configuring the specified directory, in start.md, we import demo via a relative path:

<demo
  vue="../demos/demo.vue"
  react="../demos/demo.tsx"
  html="../demos/base/demo.html"
/>

After Configuring The Specified Directory

After configuring the specified directory, in start.md, we can simplify the import path to:

<demo vue="demo.vue" react="demo.tsx" html="base/demo.html" />

Display Order And Default Selection

Local Configuration

When multiple syntaxes are displayed in a <demo /> component, the default display order is vue,react,html and the first syntax in the display order is selected by default.

You can specify the display order of demos through the order attribute, and specify the default selected demo through the select attribute.

<demo
  vue="../demos/demo.vue"
  react="../demos/demo.tsx"
  html="../demos/demo.html"
  order="html,react,vue"
  select="react"
/>

The corresponding rendering result is as follows:

loading

Global Configuration

If you want to make it effective for the global <demo /> component, add the tabs configuration in .vitepress/config.ts, for example:

import { defineConfig } from 'vitepress';
import { vitepressDemoPlugin } from 'vitepress-demo-plugin';
import path from 'path';

export default defineConfig({
  // other configs...
  markdown: {
    config(md) {
      md.use(vitepressDemoPlugin, {
        demoDir: path.resolve(__dirname, '../demos'),
        tabs: {

          order: 'html,react,vue', 
          select: 'react', 
        }, 
      });
    },
  },
});

Display Multiple Files Code

Array

If your demo contains multiple files, you can use the vueFiles/reactFiles/htmlFiles property to specify the files and codes of the corresponding type of demo to be displayed. For example:

<demo
  vue="../demos/multiple.vue"
  :vueFiles="['../demos/multiple.vue', '../demos/constant/students.ts']"
/>

The corresponding rendering result is as follows:

loading

Object

By default, vitepress-demo-plugin takes the basename of the file path as the file name when displaying multiple files. You can also specify the file name through the vueFiles/reactFiles/htmlFiles property of the Object type. For example, if you want to use constant/students.ts to reflect the directory hierarchy of the file, you can do it as follows:

<demo
  vue="../demos/multiple.vue"
  :vueFiles="{
    'multiple.vue': '../demos/multiple.vue',
    'constant/students.ts': '../demos/constant/students.ts',
  }"
/>

The corresponding rendering result is as follows:

loading

Custom

You can also use the vueFiles/reactFiles/htmlFiles property to completely customize the files and code to be displayed. For example, if you want to display two formats of a code, typescript and javascript, you can do it as follows:

<demo
  react="../demos/demo.tsx"
  :reactFiles="{
    'Typescript': '../demos/demo.tsx',
    'Javascript': '../demos/demo.jsx',
  }"
/>

The corresponding rendering result is as follows:

loading

🚨 Notice

vitepress-demo-plugin internally treats vueFiles/reactFiles/htmlFiles as a string of type string[] | Record<string, string>, so you can only declare the value of vueFiles/reactFiles/htmlFiles directly, and cannot replace it by referencing variables.

• ❌ Wrong

  const vueFiles = ['../demos/multiple.vue', '../demos/constant/students.ts'];
  
  <demo vue="../demos/multiple.vue" :vueFiles="vueFiles" />

• ✅ Right

  <demo
    vue="../demos/multiple.vue"
    :vueFiles="['../demos/multiple.vue', '../demos/constant/students.ts']"
  />

HTML Local Resource References

To reference local resources via links in HTML tags, you need to place the resource files in the public directory and reference them using absolute paths. Here's an example from demo-link.html:

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Demo With Style Link</title>
    <!-- Reference local resources from the public directory using absolute path -->
    <link rel="stylesheet" href="/style.css" />
  </head>
  <body>
    <div class="title">Html demo with style link</div>
  </body>
</html>

The correct resource structure should be:

my-docs
├── demos
│   └── demo-link.html
└── public
    └── style.css

loading

Style Isolation

Tip

Style isolation is based on raw provided by vitepress itself, but vitepress-demo-plugin has added vp-raw class name to demo, so you don't need to manually add ::: raw or vp-raw class name, otherwise it will affect the style of the code block.

Some built-in CSS styles of vitepress may affect the display of demo. You can refer to the following methods to achieve style isolation:

1. Install postcss:

npm install postcss -D
# or
yarn add postcss -D
# or
pnpm add postcss -D

2. Create a postcss.config.mjs file in the project root directory and add the following content:

import { postcssIsolateStyles } from 'vitepress';

export default {
  plugins: [
    postcssIsolateStyles({
      includeFiles: [/vp-doc\.css/],
    }),
  ],
};

Taking the table component of element-plus as an example, the rendering result is as follows:

loading

Code Theme

The code block display of vitepress-demo-plugin is based on Shiki, so you can use all themes supported by Shiki. For a list of themes, please refer to the Shiki - Bundled Themes.

You can specify the code block themes in light mode and dark mode respectively through lightTheme (default is github-light) and darkTheme (default is github-dark). Add the following code in config.ts:

import { defineConfig } from 'vitepress';
import { vitepressDemoPlugin } from 'vitepress-demo-plugin';
import path from 'path';

export default defineConfig({
  // other configs...
  markdown: {
    config(md) {
      md.use(vitepressDemoPlugin, {
        lightTheme: 'github-light', 
        darkTheme: 'github-dark', 
      });
    },
  },
});

Internationalization

You can configure the internationalization text of the code display component through the locale parameter. locale is a key-value pair object, where the key corresponds to the lang attribute configured in your vitepress multilingual settings, and the value can be either 'zh-CN' | 'en-US' | LocaleText.

Example:

import { defineConfig } from 'vitepress';
import { vitepressDemoPlugin } from 'vitepress-demo-plugin';
import path from 'path';

export default defineConfig({
  // other configs...
  locales: {
    root: {
      lang: 'zh',
      // ...other config
    },
    en: {
      lang: 'en-US',
      // ...other config
    },
    ja: {
      lang: 'ja',
      // ...other config
    },
  },
  markdown: {
    config(md) {
      md.use(vitepressDemoPlugin, {
        // key corresponds to the lang above
        locale: {
          zh: 'zh-CN', // zh-CN represents using built-in Chinese text
          'en-US': 'en-US', // en-US represents using built-in English text
          // Customize other languages:
          ja: {
            openInStackblitz: 'Stackblitz で開く',
            openInCodeSandbox: 'Codesandbox で開く',
            openInGithub: 'GitHub で開く',
            openInGitlab: 'GitLab で開く',
            collapseCode: 'コードを折りたたむ',
            expandCode: 'コードを展開する',
            copyCode: 'コードをコピーする',
          },
        },
      });
    },
  },
});

For the LocaleText type definition that needs to be configured, please refer to text.ts