> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Function Library Resources Reference

## Article: Function Library Resources Reference

## Article Link: https://dev.wix.com/docs/site-extensions/function-libraries/function-library-resources-reference.md

## Article Content:

# Function Library Resources Reference

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.

## Example

The following example points to the implementation for a generated price-formatting library:

```ts
resources: {
  client: {
    url: './extensions/site/function-libraries/my-function-library/my-function-library.ts',
  },
}
```

## Resources fields

A `resources` section has the following fields:

| Field | Required | Description |
| --- | --- | --- |
| `client` | Yes | The library's [implementation](#client-resource). |
| `moduleSpecifier` | No | Module identifier for the library. |

The `moduleSpecifier` is one of the following:

- If your library isn't published as an npm package, set `moduleSpecifier` to `<codeIdentifier>-<library-name>`, where `<codeIdentifier>` is `companionApp`, the same identifier that prefixes the manifest's `type`.
- If your library is published as an npm package, set `moduleSpecifier` to that package's name.

## Client resource

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`. |

## See also

- [About Function Libraries](https://dev.wix.com/docs/site-extensions/function-libraries/about-function-libraries.md)
- [Function Libraries](https://dev.wix.com/docs/overview/extensions-framework/site-extensions/function-libraries.md)
- [About Function Libraries in Studio Two](https://dev.wix.com/docs/studio-two/code-your-site/code-model/function-libraries/about-function-libraries.md)
- [About the Function Library Manifest](https://dev.wix.com/docs/site-extensions/function-libraries/about-the-function-library-manifest.md)
- [Function Reference](https://dev.wix.com/docs/site-extensions/function-libraries/function-reference.md)