Readonlyassets: readonly string[]Relative asset paths. Relaxed vs the build PluginManifestSchema (which requires >= 1) because
dev-server manifests list no assets — chunks/styles flow through the dev server on demand.
Optional Readonlyauthor?: stringOptional Readonlydependencies?: { readonly [key: string]: string }Declared dependencies resolved to installed versions at build time (SDK-compat source).
Optional ReadonlydependsOn?: readonly string[]Optional Readonlydescription?: stringOptional ReadonlydevEntry?: stringPresent only for dev-server manifests; points at the unbundled source entry.
Optional ReadonlyhomePage?: stringOptional Readonlyicon?: { hue?: string; key: string }Readonlykey: stringOptional Readonlymodules?: readonly {Every module of a Plugin.config plugin, with its body's URL relative to the manifest. A host builds the plugin from
these alone; a manifest without them (a plugin built from src/plugin.tsx) is loaded through its entry module.
Readonlyname: stringOptional Readonlyscreenshots?: readonly { dark?: string; light?: string }[]Optional Readonlysource?: stringOptional Readonlyspec?: stringOptional Readonlytags?: readonly string[]Readonlyversion: stringPlugin version (semver). Sourced from the publishing project's package.json.
The plugin definition a manifest describes, or
undefinedwhen it lists no modules: itsConfig2.Pluginmetadata, which the manifest carries flat, and its modules.