Skip to main content
Validation and build are not a substitute for rendering through a portal host. Complete both automated and interactive checks before publication. The package worker must start through startWidgetPackage before its generated runtime can load.

​
Validate a standalone package

Build writes generated artifacts under .fluid/widget-dist/. Inspect manifest.json, runtime assets, CSS, and referenced files, but do not edit or commit generated output. Publish a reviewed Droplet package:
Increment the manifest’s semantic version before publishing a changed package. Published versions are immutable.

​
Validate a company package

From its portal project:
Publish reviewed company widget artifacts:
Portal deploy does not push Portal Definition JSON or activate a portal version.

​
Inspect behavior

Render every widget through a portal or builder host. Verify defaults, malformed inputs, keyboard behavior, focus, theme modes, reduced motion, responsive layout, and runtime cleanup.

​
Recover from build failure

Fix the first reported source or metadata error. If a clean retry is necessary, remove only generated .fluid/widget-build/, .fluid/tmp/, or .fluid/widget-dist/ content. Preserve author source and configuration.