The resources section of a function library manifest points to the library's implementation code. On the published site, Wix loads this code and calls a connected function when its slot is triggered.
The following example points to the implementation for a generated price-formatting library:
A resources section has the following fields:
| Field | Required | Description |
|---|---|---|
client | Yes | The library's implementation. |
moduleSpecifier | No | Module identifier for the library. |
The moduleSpecifier is one of the following:
moduleSpecifier to <codeIdentifier>-<library-name>, where <codeIdentifier> is companionApp, the same identifier that prefixes the manifest's type.moduleSpecifier to that package's name.The client field points to the library implementation that runs on the live site:
| Field | Required | Description |
|---|---|---|
url | Yes | Path to the library's implementation file. Each function is a named export matching its key in functions. |
Last updated: 2 November 2026