Skip to main content
Prefer the generated build and compiler. This reference explains their portable output so you can extend your package’s build without inventing a second protocol. Import PHP types from Bjanczak\FilamentFlexFields\Support\Assets\Manifest.

AssetManifest

The manifest format is 1. Its release is derived from canonical complete build metadata. Portable metadata excludes deployment URLs and installed source roots. Paths cannot collide case-insensitively, traverse directories or refer to missing outputs. Keep artifact IDs and logical component/root IDs separate.

AssetArtifact

Use type declarations for resources the bundler cannot infer. Do not label a classic script as a module or assume a worker is a normal eagerly executed entry.

AssetPackage

sourcePath($artifact) resolves a safe existing installed output. publicDirectory($prefix = '') describes its immutable publication namespace; moduleIdentity($artifact) supplies a package-scoped asset identity. sameInstallationAs() compares package, release and installed root.

Esbuild declaration

The compiler’s declaration contains the following root fields:
This is an input declaration, not the final generated manifest. Follow the complete build example for workers and WASM, CLI arguments, metafile handling and output validation. Do not hand-edit generated content hashes.
Last modified on October 16, 2026