@nginxui/plugin-sdk

TypeScript SDK for NGINX UI browser plugin bundles: the types the host runtime exposes on window.NginxUI, a Vite preset that builds a compliant IIFE bundle, and a tiny helper for zero-build iframe pages.

A plugin webapp bundle runs inside the host page and shares its Vue, Vue Router, Pinia and antdv-next instances rather than shipping its own copies. This package has no runtime dependency on any of them for that reason: it only describes their shapes.

Install

bun add -d @nginxui/plugin-sdk

@nginxui/plugin-sdk — types and runtime helpers

import { defineNginxUIPlugin, registerPlugin, useShared } from '@nginxui/plugin-sdk'
import MySlot from './MySlot.vue'

const plugin = defineNginxUIPlugin({
  setup(registry) {
    registry.registerSlot('certificate.challenge.form:dns01', MySlot)
    registry.registerTranslations('zh_CN', { 'My Setting': '我的设置' })
  },
})

registerPlugin('io.github.example.myplugin', plugin)

useShared() returns window.NginxUI.shared (vue, vueRouter, pinia, antdvNext, antdvIcons, vueuse, gettext, the host http client, and the versions map), typed but without importing any of those packages.

Log page slots

The nginx log pages and the site log actions take components through registerSlot. The context types are exported:

Slot	Context type	Options read
nginx_log.view:{key}	NginxLogViewContext (path, type)	label (name of the view mode)
nginx_log.list.toolbar	NginxLogListToolbarContext (type)
nginx_log.list.column:{key}	NginxLogRowContext (row); when gets NginxLogColumnWhenContext (type)	label (column title), sortValue, filters
nginx_log.list.row.actions	NginxLogRowContext (row)
site.log.actions	SiteLogActionsContext (accessLogPath, accessLogInherited, errorLogPath, errorLogInherited, siteName)

registry.registerSlot('nginx_log.list.column:status', StatusCell, {
  label: 'Index Status',
  sortValue: row => statusRank(row.path),
  filters: [{ label: 'Indexed', value: 'indexed', match: row => isIndexed(row.path) }],
})

label texts are English source strings; ship their translations with registerTranslations. The host sorts and filters plugin columns in the browser.

A column's when decides on the list, not on a row: it receives { type } (access or error) once per list, and a column it rejects has no header and no cells. Register an access log only column once and let when hide it on the error list:

registry.registerSlot('nginx_log.list.column:index_status', StatusCell, {
  label: 'Index Status',
  when: ctx => ctx.type === 'access',
})

For site.log.actions, a path is the site's own log directive, else the nginx default log the site falls back to, else an empty string. The matching accessLogInherited or errorLogInherited is true for the fallback, whose file may hold the traffic of other sites, so an action that is about one site should say so or hide itself.

WebSockets

A browser WebSocket cannot send request headers, so the host authenticates it with credentials in the URL. Ask the registry for that URL instead of building it, and feature-detect the method:

const socket = registry.wsUrl ? new WebSocket(registry.wsUrl('/events')) : undefined

wsUrl(path) returns an absolute ws: or wss: URL for a path under the plugin's http capability. The host removes the credentials from the request before it reaches the plugin.

On-demand chunks

Keep the entry small and load heavy code when a page needs it. Declare the chunks in webapp.chunks (the Vite preset writes them into manifest.webapp.json), then load one with registry.loadChunk:

registry.registerRoute({
  path: 'log-analytics/dashboard',
  component: defineAsyncComponent(async () => {
    const chunk = await registry.loadChunk!<{ Dashboard: Component }>('dashboard')
    return chunk.Dashboard as never
  }),
})

loadChunk loads a declared chunk once and resolves with the exports the chunk handed to the host; an undeclared name rejects. A chunk file exports its components and nothing else. When you build it with the chunk preset below, the registerChunk call is added for you; with another build tool, call the helper yourself at the end of the chunk:

import { registerChunk } from '@nginxui/plugin-sdk'

registerChunk('io.github.example.myplugin', 'dashboard', { Dashboard })

@nginxui/plugin-sdk/vite — build preset

// vite.config.ts
import vue from '@vitejs/plugin-vue'
import { nginxUiPlugin } from '@nginxui/plugin-sdk/vite'
import { defineConfig } from 'vite'

export default defineConfig({
  plugins: [
    vue(),
    nginxUiPlugin({ id: 'io.github.example.myplugin' }),
  ],
})

Or, for a project with nothing else to configure, use the ready-made config:

// vite.config.ts
import { defineNginxUiPluginConfig } from '@nginxui/plugin-sdk/vite'

export default defineNginxUiPluginConfig({ id: 'io.github.example.myplugin' })

nginxUiPlugin(options):

Option	Default	Meaning
id	required	Plugin id from plugin.json. Used to derive the IIFE global name.
entry	src/main.ts	Bundle entry point, relative to the project root.
outDir	dist	Build output directory, relative to the project root.
root	Vite's own root	Directory to resolve node_modules and package.json from when computing shared versions.

bun run build (i.e. vite build) with this plugin produces:

• dist/main.js — one IIFE, vue, vue-router, pinia, antdv-next, @antdv-next/icons, @vueuse/core, vue3-gettext and @uozi-admin/request externalized onto window.NginxUI.shared.*.

• dist/style.css — extracted styles, always under this fixed name.

• dist/manifest.webapp.json — the fragment your plugin.json generator merges into webapp:

  {
    "bundle_path": "webapp/dist/main.js",
    "style_path": "webapp/dist/style.css",
    "shared": {
      "vue": ">=3.5.42 <4",
      "vue-router": ">=5.3.1 <6",
      "pinia": ">=4.0.3 <5",
      "antdv-next": "~1.5",
      "@vueuse/core": ">=15.0.0"
    }
  }

  The ranges are computed from the versions actually installed in node_modules (falling back to the range declared in your own package.json when a library is not installed) so that the manifest always reflects what the bundle was really built against. bundle_path and style_path assume the Vite project lives in a directory named webapp inside the plugin repository — the convention used by the official plugins.

Chunks

nginxUiPlugin({ id, chunks: ['dashboard'] }) lists the chunks in manifest.webapp.json as chunks, each at webapp/dist/chunks/<name>.js. Build each chunk with its own config, after the entry build (the chunk build keeps dist/):

// vite.dashboard.config.ts
import { defineNginxUiChunkConfig } from '@nginxui/plugin-sdk/vite'

export default defineNginxUiChunkConfig({
  id: 'io.github.example.myplugin',
  name: 'dashboard',
  entry: 'src/dashboard.ts',
})

"build": "vite build && vite build -c vite.dashboard.config.ts"

The chunk is one IIFE with the shared runtime externalized, like the entry. Its styles are folded into the script as a style element, and the registerChunk call is appended, so the entry module only exports.

@nginxui/plugin-sdk/page — zero-build iframe pages

For a webapp.pages entry (a static HTML page with no build step), served inside the host's iframe wrapper:

<script type="module">
  import { requestToken, watchTheme } from 'https://esm.sh/@nginxui/plugin-sdk/page'

  const token = await requestToken()
  watchTheme(theme => console.log('host theme is now', theme))
</script>

Export	Behavior
requestToken()	Sends { type: 'nginx-ui:token' } to window.parent, resolves with the auth token.
requestTheme()	Sends { type: 'nginx-ui:theme' }, resolves with 'light' | 'dark' and sets data-theme on <html>.
watchTheme(onChange?)	Applies every unsolicited theme push the host sends afterwards. Returns an unsubscribe function.

The built file is dist/page.js, kept under 2 KB with no dependencies.

Development

bun install
bun run build      # emits dist/index.js, dist/vite.js, dist/page.js and .d.ts files
bun test           # unit tests for the semver range and chunk helpers
bun run typecheck

License

AGPL-3.0. See LICENSE.