Plugin API

Wite plugins extends Rollup's well-designed plugin interface with a few extra Wite-specific options. As a result, you can write a Wite plugin once and have it work for both dev and build.

It is recommended to go through Rollup's plugin documentation first before reading the sections below.

Authoring a Plugin

Wite strives to offer established patterns out of the box, so before creating a new plugin make sure that you check the Features guide to see if your need is covered.

When creating a plugin, you can inline it in your wite.config.js. There is no need to create a new package for it.

Conventions

If the plugin doesn't use Wite specific hooks and can be implemented as a Compatible Rollup Plugin, then it is recommended to use the Rollup Plugin naming conventions.

Rollup Plugins should have a clear name with rollup-plugin- prefix.
Include rollup-plugin and wite-plugin keywords in package.json.

This exposes the plugin to be also used in pure Rollup or WMR based projects

For Wite only plugins

Wite Plugins should have a clear name with wite-plugin- prefix.
Include wite-plugin keyword in package.json.
Include a section in the plugin docs detailing why it is a Wite only plugin (for example, it uses Wite specific plugin hooks).

If your plugin is only going to work for a particular framework, its name should be included as part of the prefix

wite-plugin-kdu- prefix for Kdu Plugins
wite-plugin-react- prefix for React Plugins

Plugins config

Users will add plugins to the project devDependencies and configure them using the plugins array option.

// wite.config.js
import witePlugin from 'wite-plugin-feature'
import rollupPlugin from 'rollup-plugin-feature'

export default defineConfig({
  plugins: [witePlugin(), rollupPlugin()]
})

Falsy plugins will be ignored, which can be used to easily activate or deactivate plugins.

plugins also accept presets including several plugins as a single element. This is useful for complex features (like framework integration) that are implemented using several plugins. The array will be flattened internally.

// framework-plugin
import frameworkRefresh from 'wite-plugin-framework-refresh'
import frameworkDevtools from 'wite-plugin-framework-devtools'

export default function framework(config) {
  return [frameworkRefresh(config), frameworkDevTools(config)]
}

// wite.config.js
import { defineConfig } from 'wite'
import framework from 'wite-plugin-framework'

export default defineConfig({
  plugins: [framework()]
})

Simple Examples

TIP

It is common convention to author a Wite/Rollup plugin as a factory function that returns the actual plugin object. The function can accept options which allows users to customize the behavior of the plugin.

Transforming Custom File Types

const fileRegex = /\.(my-file-ext)$/

export default function myPlugin() {
  return {
    name: 'transform-file',

    transform(src, id) {
      if (fileRegex.test(id)) {
        return {
          code: compileFileToJS(src),
          map: null // provide source map if available
        }
      }
    }
  }
}

Importing a Virtual File

See the example in the next section.

Virtual Modules Convention

Virtual modules are a useful scheme that allows you to pass build time information to the source files using normal ESM import syntax.

export default function myPlugin() {
  const virtualModuleId = 'virtual:my-module'
  const resolvedVirtualModuleId = '\0' + virtualModuleId

  return {
    name: 'my-plugin', // required, will show up in warnings and errors
    resolveId(id) {
      if (id === virtualModuleId) {
        return resolvedVirtualModuleId
      }
    },
    load(id) {
      if (id === resolvedVirtualModuleId) {
        return `export const msg = "from virtual module"`
      }
    }
  }
}

Which allows importing the module in JavaScript:

import { msg } from 'virtual:my-module'

console.log(msg)

Virtual modules in Wite (and Rollup) are prefixed with virtual: for the user-facing path by convention. If possible the plugin name should be used as a namespace to avoid collisions with other plugins in the ecosystem. For example, a wite-plugin-posts could ask users to import a virtual:posts or virtual:posts/helpers virtual modules to get build time information. Internally, plugins that use virtual modules should prefix the module ID with \0 while resolving the id, a convention from the rollup ecosystem. This prevents other plugins from trying to process the id (like node resolution), and core features like sourcemaps can use this info to differentiate between virtual modules and regular files. \0 is not a permitted char in import URLs so we have to replace them during import analysis. A \0{id} virtual id ends up encoded as /@id/__x00__{id} during dev in the browser. The id will be decoded back before entering the plugins pipeline, so this is not seen by plugins hooks code.

Note that modules directly derived from a real file, as in the case of a script module in a Single File Component (like a .kdu) don't need to follow this convention. SFCs generally generate a set of submodules when processed but the code in these can be mapped back to the filesystem. Using \0 for these submodules would prevent sourcemaps from working correctly.

Universal Hooks

During dev, the Wite dev server creates a plugin container that invokes Rollup Build Hooks the same way Rollup does it.

The following hooks are called once on server start:

The following hooks are called on each incoming module request:

The following hooks are called when the server is closed:

Note that the moduleParsed hook is not called during dev, because Wite avoids full AST parses for better performance.

Output Generation Hooks (except closeBundle) are not called during dev. You can think of Wite's dev server as only calling rollup.rollup() without calling bundle.generate().

Wite Specific Hooks

Wite plugins can also provide hooks that serve Wite-specific purposes. These hooks are ignored by Rollup.

`config`

Type: (config: UserConfig, env: { mode: string, command: string }) => UserConfig | null | void

Kind: async, sequential

Modify Wite config before it's resolved. The hook receives the raw user config (CLI options merged with config file) and the current config env which exposes the mode and command being used. It can return a partial config object that will be deeply merged into existing config, or directly mutate the config (if the default merging cannot achieve the desired result).

Example:

// return partial config (recommended)
const partialConfigPlugin = () => ({
  name: 'return-partial',
  config: () => ({
    resolve: {
      alias: {
        foo: 'bar'
      }
    }
  })
})

// mutate the config directly (use only when merging doesn't work)
const mutateConfigPlugin = () => ({
  name: 'mutate-config',
  config(config, { command }) {
    if (command === 'build') {
      config.root = 'foo'
    }
  }
})

Note

User plugins are resolved before running this hook so injecting other plugins inside the config hook will have no effect.

`configResolved`

Type: (config: ResolvedConfig) => void | Promise<void>

Kind: async, parallel

Called after the Wite config is resolved. Use this hook to read and store the final resolved config. It is also useful when the plugin needs to do something different based the command is being run.

Example:

const examplePlugin = () => {
  let config

  return {
    name: 'read-config',

    configResolved(resolvedConfig) {
      // store the resolved config
      config = resolvedConfig
    },

    // use stored config in other hooks
    transform(code, id) {
      if (config.command === 'serve') {
        // dev: plugin invoked by dev server
      } else {
        // build: plugin invoked by Rollup
      }
    }
  }
}

Note that the command value is serve in dev (in the cli wite, wite dev, and wite serve are aliases).

`configureServer`

Type: (server: WiteDevServer) => (() => void) | void | Promise<(() => void) | void>
Kind: async, sequential

See also: WiteDevServer

Hook for configuring the dev server. The most common use case is adding custom middlewares to the internal connect app:

const myPlugin = () => ({
  name: 'configure-server',
  configureServer(server) {
    server.middlewares.use((req, res, next) => {
      // custom handle request...
    })
  }
})

Injecting Post Middleware

The configureServer hook is called before internal middlewares are installed, so the custom middlewares will run before internal middlewares by default. If you want to inject a middleware after internal middlewares, you can return a function from configureServer, which will be called after internal middlewares are installed:

const myPlugin = () => ({
  name: 'configure-server',
  configureServer(server) {
    // return a post hook that is called after internal middlewares are
    // installed
    return () => {
      server.middlewares.use((req, res, next) => {
        // custom handle request...
      })
    }
  }
})

Storing Server Access

In some cases, other plugin hooks may need access to the dev server instance (e.g. accessing the web socket server, the file system watcher, or the module graph). This hook can also be used to store the server instance for access in other hooks:

const myPlugin = () => {
  let server
  return {
    name: 'configure-server',
    configureServer(_server) {
      server = _server
    },
    transform(code, id) {
      if (server) {
        // use server...
      }
    }
  }
}

Note configureServer is not called when running the production build so your other hooks need to guard against its absence.

`configurePreviewServer`

Type: (server: { middlewares: Connect.Server, httpServer: http.Server }) => (() => void) | void | Promise<(() => void) | void>
Kind: async, sequential
Same as configureServer but for the preview server. It provides the connect server and its underlying http server. Similarly to configureServer, the configurePreviewServer hook is called before other middlewares are installed. If you want to inject a middleware after other middlewares, you can return a function from configurePreviewServer, which will be called after internal middlewares are installed:
```
const myPlugin = () => ({
  name: 'configure-preview-server',
  configurePreviewServer(server) {
    // return a post hook that is called after other middlewares are
    // installed
    return () => {
      server.middlewares.use((req, res, next) => {
        // custom handle request...
      })
    }
  }
})
```

`transformIndexHtml`

Type: IndexHtmlTransformHook | { enforce?: 'pre' | 'post', transform: IndexHtmlTransformHook }

Kind: async, sequential

Dedicated hook for transforming HTML entry point files such as index.html. The hook receives the current HTML string and a transform context. The context exposes the WiteDevServer instance during dev, and exposes the Rollup output bundle during build.

The hook can be async and can return one of the following:

Transformed HTML string
An array of tag descriptor objects ({ tag, attrs, children }) to inject to the existing HTML. Each tag can also specify where it should be injected to (default is prepending to <head>)
An object containing both as { html, tags }

Basic Example:

const htmlPlugin = () => {
  return {
    name: 'html-transform',
    transformIndexHtml(html) {
      return html.replace(
        /<title>(.*?)<\/title>/,
        `<title>Title replaced!</title>`
      )
    }
  }
}

Full Hook Signature:

type IndexHtmlTransformHook = (
  html: string,
  ctx: {
    path: string
    filename: string
    server?: WiteDevServer
    bundle?: import('rollup').OutputBundle
    chunk?: import('rollup').OutputChunk
  }
) =>
  | IndexHtmlTransformResult
  | void
  | Promise<IndexHtmlTransformResult | void>

type IndexHtmlTransformResult =
  | string
  | HtmlTagDescriptor[]
  | {
      html: string
      tags: HtmlTagDescriptor[]
    }

interface HtmlTagDescriptor {
  tag: string
  attrs?: Record<string, string | boolean>
  children?: string | HtmlTagDescriptor[]
  /**
   * default: 'head-prepend'
   */
  injectTo?: 'head' | 'body' | 'head-prepend' | 'body-prepend'
}

`handleHotUpdate`

Type: (ctx: HmrContext) => Array<ModuleNode> | void | Promise<Array<ModuleNode> | void>
Perform custom HMR update handling. The hook receives a context object with the following signature:
```
interface HmrContext {
  file: string
  timestamp: number
  modules: Array<ModuleNode>
  read: () => string | Promise<string>
  server: WiteDevServer
}
```
- modules is an array of modules that are affected by the changed file. It's an array because a single file may map to multiple served modules (e.g. Kdu SFCs).
- read is an async read function that returns the content of the file. This is provided because on some systems, the file change callback may fire too fast before the editor finishes updating the file and direct fs.readFile will return empty content. The read function passed in normalizes this behavior.
The hook can choose to:
- Filter and narrow down the affected module list so that the HMR is more accurate.
- Return an empty array and perform complete custom HMR handling by sending custom events to the client:
```
handleHotUpdate({ server }) {
  server.ws.send({
    type: 'custom',
    event: 'special-update',
    data: {}
  })
  return []
}
```
  Client code should register corresponding handler using the HMR API (this could be injected by the same plugin's transform hook):
```
if (import.meta.hot) {
  import.meta.hot.on('special-update', (data) => {
    // perform custom update
  })
}
```

Plugin Ordering

A Wite plugin can additionally specify an enforce property (similar to webpack loaders) to adjust its application order. The value of enforce can be either "pre" or "post". The resolved plugins will be in the following order:

Alias
User plugins with enforce: 'pre'
Wite core plugins
User plugins without enforce value
Wite build plugins
User plugins with enforce: 'post'
Wite post build plugins (minify, manifest, reporting)

Conditional Application

By default plugins are invoked for both serve and build. In cases where a plugin needs to be conditionally applied only during serve or build, use the apply property to only invoke them during 'build' or 'serve':

function myPlugin() {
  return {
    name: 'build-only',
    apply: 'build' // or 'serve'
  }
}

A function can also be used for more precise control:

apply(config, { command }) {
  // apply only on build but not for SSR
  return command === 'build' && !config.build.ssr
}

Rollup Plugin Compatibility

A fair number of Rollup plugins will work directly as a Wite plugin (e.g. @rollup/plugin-alias or @rollup/plugin-json), but not all of them, since some plugin hooks do not make sense in an unbundled dev server context.

In general, as long as a Rollup plugin fits the following criteria then it should just work as a Wite plugin:

It doesn't use the moduleParsed hook.
It doesn't have strong coupling between bundle-phase hooks and output-phase hooks.

If a Rollup plugin only makes sense for the build phase, then it can be specified under build.rollupOptions.plugins instead. It will work the same as a Wite plugin with enforce: 'post' and apply: 'build'.

You can also augment an existing Rollup plugin with Wite-only properties:

// wite.config.js
import example from 'rollup-plugin-example'
import { defineConfig } from 'wite'

export default defineConfig({
  plugins: [
    {
      ...example(),
      enforce: 'post',
      apply: 'build'
    }
  ]
})

Path Normalization

Wite normalizes paths while resolving ids to use POSIX separators ( / ) while preserving the volume in Windows. On the other hand, Rollup keeps resolved paths untouched by default, so resolved ids have win32 separators ( \ ) in Windows. However, Rollup plugins use a normalizePath utility function from @rollup/pluginutils internally, which converts separators to POSIX before performing comparisons. This means that when these plugins are used in Wite, the include and exclude config pattern and other similar paths against resolved ids comparisons work correctly.

So, for Wite plugins, when comparing paths against resolved ids it is important to first normalize the paths to use POSIX separators. An equivalent normalizePath utility function is exported from the wite module.

import { normalizePath } from 'wite'

normalizePath('foo\\bar') // 'foo/bar'
normalizePath('foo/bar') // 'foo/bar'

Filtering, include/exclude pattern

Wite exposes @rollup/pluginutils's createFilter function to encourage Wite specific plugins and integrations to use the standard include/exclude filtering pattern, which is also used in Wite core itself.

Client-server Communication

Since Wite 2.9, we provide some utilities for plugins to help handle the communication with clients.

Server to Client

On the plugin side, we could use server.ws.send to broadcast events to all the clients:

// wite.config.js
export default defineConfig({
  plugins: [
    {
      // ...
      configureServer(server) {
        server.ws.send('my:greetings', { msg: 'hello' })
      }
    }
  ]
})

NOTE

We recommend always prefixing your event names to avoid collisions with other plugins.

On the client side, use hot.on to listen to the events:

// client side
if (import.meta.hot) {
  import.meta.hot.on('my:greetings', (data) => {
    console.log(data.msg) // hello
  })
}

Client to Server

To send events from the client to the server, we can use hot.send:

// client side
if (import.meta.hot) {
  import.meta.hot.send('my:from-client', { msg: 'Hey!' })
}

Then use server.ws.on and listen to the events on the server side:

// wite.config.js
export default defineConfig({
  plugins: [
    {
      // ...
      configureServer(server) {
        server.ws.on('my:from-client', (data, client) => {
          console.log('Message from client:', data.msg) // Hey!
          // reply only to the client (if needed)
          client.send('my:ack', { msg: 'Hi! I got your message!' })
        })
      }
    }
  ]
})

TypeScript for Custom Events

It is possible to type custom events by extending the CustomEventMap interface:

// events.d.ts
import 'wite/types/customEvent'

declare module 'wite/types/customEvent' {
  interface CustomEventMap {
    'custom:foo': { msg: string }
    // 'event-key': payload
  }
}

Plugin API #

Authoring a Plugin #

Conventions #

Plugins config #

Simple Examples #

Transforming Custom File Types #

Importing a Virtual File #

Virtual Modules Convention #

Universal Hooks #

Wite Specific Hooks #

config #

configResolved #

configureServer #

configurePreviewServer #

transformIndexHtml #

handleHotUpdate #

Plugin Ordering #

Conditional Application #

Rollup Plugin Compatibility #

Path Normalization #

Filtering, include/exclude pattern #

Client-server Communication #

Server to Client #

Client to Server #

TypeScript for Custom Events #