hunk.code_window: /**
    * Transform Monaco code block to component
    */
   export function transformHighlighter(md: string) {
     return md.replace(/^```(\w+?)\s*{([\d\w*,\|-]+)}[\s\n]*([\s\S]+?)^```/mg, (full, lang = '', rangeStr: string, code: string) => {
       const ranges = rangeStr.split(/\|/g).map(i => i.trim())
  
hunk.labels: keep keep keep keep replace keep
hunk.after_edit:   return md.replace(/^```(\w+?)\s*{([\d\w*,\|-]+)}\s*({.*?})[\s\n]*([\s\S]+?)^```/mg, (full, lang = '', rangeStr: string, options = '', code: string) => {
  
hunk.file_path: packages/slidev/node/plugins/markdown.ts
hunk.type: replace
file: # Directory Structure
  
  Slidev employs some directory structure conventions to minimize the configuration surface and to make the functionality extensions flexible and intuitive.
  
  The basic structure is as follows:
  
  ```bash
  your-slidev/
    ├── components/       # custom components
    ├── layouts/          # custom layouts
    ├── public/           # static assets
    ├── setup/            # custom setup / hooks
    ├── styles/           # custom style
    ├── index.html        # injections to index.html
    ├── slides.md         # the main slides entry
    ├── vite.config.ts    # extending vite config
    └── windi.config.ts   # extending windicss config
  ```
  
  All of them are optional.
  
  ## Components
  
  Conventions: `./components/*.{vue,js,ts,jsx,tsx}`
  
  Components inside this directory can be directly used in the slides Markdown with the same component name as the file name.
  
  For example:
  
  ```bash
  your-slidev/
    ├── ...
    └── components/
        ├── MyComponent.vue
        └── HelloWorld.ts
  ```
  
  ```md
  <!-- slides.md -->
  
  # My Slide
  
  <MyComponent :count="4"/>
  
  <!-- both namings work -->
  
  <hello-world foo="bar">
    Slot
  </hello-world>
  ```
  
  This feature is powered by [`vite-plugin-components`](https://github.com/antfu/vite-plugin-components), learn more there.
  
  Slidev also provides some [built-in components](/builtin/components) for you to use.
  
  ## Layouts
  
  Conventions: `./layouts/*.{vue,js,ts,jsx,tsx}`
  
  ```
  your-slidev/
    ├── ...
    └── layouts/
        ├── cover.vue
        └── my-cool-theme.vue
  ```
  
  You can use any filename for your layout. You then reference your layout in you YAML header using the filename.
  
  ```yaml
  ---
  layout: my-cool-theme
  ---
  ```
  
  If the layout you provide has the same name as a built-in layout or a theme layout, your custom layout will take precedence over the built-in/theme layout. The priority order is `local > theme > built-in`.
  
  In the layout component, use `<slot/>` for the slide content. For example:
  
  ```html
  <!-- default.vue -->
  <template>
    <div class="slidev-layout default">
      <slot />
    </div>
  </template>
  ```
  
  ## Public
  
  Conventions: `./public/*`
  
  Assets in this directory will be served at root path `/` during dev, and copied to the root of the dist directory as-is. Read more about [Vite's `public` directory](https://vitejs.dev/guide/assets.html#the-public-directory).
  
  ## Style
  
  Conventions: `./style.css` | `./styles/index.{css,js,ts}`
  
  Files following this convention will be injected to the App root. If you need to import multiple css entries, you can create the following structure and managing the import order yourself.
  
  ```bash
  your-slidev/
    ├── ...
    └── styles/
        ├── index.ts
        ├── base.css
        ├── code.css
        └── layouts.css
  ```
  
  ```ts
  // styles/index.ts
  
  import './base.css'
  import './code.css'
  import './layouts.css'
  ```
  
  Styles will be processed by [Windi CSS](http://windicss.org/) and [PostCSS](https://postcss.org/), so you can use css nesting and [at-directives](https://windicss.org/features/directives.html) out-of-box. For example:
  
  ```less
  .slidev-layout {
    @apply px-14 py-10 text-[1.1rem];
  
    h1, h2, h3, h4, p, div {
      @apply select-none;
    }
  
    pre, code {
      @apply select-text;
    }
  
    a {
      color: theme('colors.primary');
    }
  }
  ```
  
  [Learn more about the syntax](https://windicss.org/features/directives.html).
  
  ## `index.html`
  
  Conventions: `index.html`
  
  The `index.html` provides the ability to inject meta tags and/or scripts to the main `index.html`
  
  For example, for the following custom `index.html`:
  
  ```html
  <!-- ./index.html -->
  <head>
    <link rel="preconnect" href="https://fonts.gstatic.com">
    <link href="https://fonts.googleapis.com/css2?family=Fira+Code:wght@400;600&family=Nunito+Sans:wght@200;400;600&display=swap" rel="stylesheet">
  </head>
  
  <body>
    <script src="./your-scripts"></script>
  </body>
  ```
  
  The final hosted `index.html` will be:
  
  ```html
  <!DOCTYPE html>
  <html lang="en">
  <head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <link rel="icon" type="image/png" href="https://raw.githubusercontent.com/slidevjs/slidev/main/assets/favicon.png">
    <!-- injected head -->
    <link rel="preconnect" href="https://fonts.gstatic.com">
    <link href="https://fonts.googleapis.com/css2?family=Fira+Code:wght@400;600&family=Nunito+Sans:wght@200;400;600&display=swap" rel="stylesheet">
  </head>
  <body>
    <div id="app"></div>
    <script type="module" src="__ENTRY__"></script>
    <!-- injected body -->
    <script src="./your-scripts"></script>
  </body>
  </html>
  ```
  