> ## Documentation Index
> Fetch the complete documentation index at: https://flex-fields.bjanczak.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Examples target Filament 5. Verify optional dependencies before configuring integrations.
> Upload transfer completion, permanent storage and record acceptance are separate milestones. Native and Spatie image conversions retain the original.

# Publish & diagnose assets

> Publish the prebuilt FLEX assets and inspect release consistency and component dependency requirements.

FLEX ships prebuilt CSS and JavaScript. Publish the files after installing or updating the package; a frontend build is not required for ordinary application use.

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
php artisan filament:assets
```

Deploy the PHP package and its matching browser assets together. Keep earlier release files while existing pages or application nodes still use them. See [Updating & deployment](https://flex-fields.bjanczak.com/docs/updating.md) for the complete rollout.

## Verify a deployment or investigate a control

The included components declare their resource requirements for you. Use these
commands to verify a release during deployment or investigate a specific setup
issue; they are not steps you repeat when adding each field.

```bash Published release theme={"theme":{"light":"github-light","dark":"github-dark"}}
php artisan fff:assets:doctor --published --json
```

```bash Component dependencies theme={"theme":{"light":"github-light","dark":"github-dark"}}
php artisan fff:assets:explain select-field
```

**Doctor answers “Do these published files match the installed release?”**
**Explain answers “Why does this component need these resources?”** Use the
component identifier from its registration, such as `select-field` above.

For a particular open field or dialog, the [instance inspector](https://flex-fields.bjanczak.com/docs/extensions/diagnostics.md)
shows retained resources and initialization states. Start with
[Troubleshooting](https://flex-fields.bjanczak.com/docs/troubleshooting.md) if you need help choosing the right check.

Versioned asset identities support repeat visits and cache reuse. Preserve compatible releases while open documents or application nodes still refer to them; [Updating & deployment](https://flex-fields.bjanczak.com/docs/updating.md) explains the release workflow.

For CDN origins, integrity and restrictive policies, use [asset delivery](https://flex-fields.bjanczak.com/docs/extensions/asset-delivery.md).

## Continue reading

[Asset Manager overview](https://flex-fields.bjanczak.com/docs/asset-loading.md) · [Resource sharing](https://flex-fields.bjanczak.com/docs/assets/sharing.md) · [Activation & cleanup](https://flex-fields.bjanczak.com/docs/assets/lifecycle.md) · [Performance](https://flex-fields.bjanczak.com/docs/assets/performance.md) · [Publish & diagnose](https://flex-fields.bjanczak.com/docs/assets/deployment.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.