CodeVetter · Repo Unpack · Feature catalog
chromaui/chromatic-cli
Publishing supports locally built web Storybooks and prebuilt output, with hosted verification and visual-result reporting. Users can constrain stories, apply branch policies, initialize archive integrations, or build React Native artifacts. Auxiliary commands expose dependency tracing and manifest inspection, while Node consumers can reserve temporary share URLs. Diagnostics, metadata, and JUnit output provide operational visibility alongside terminal messages and Action outputs.
- The main publishing path runs the discovered build script or a custom buildCommand; storybookBuildDir bypasses the web build and sends existing artifacts through preparation and upload.
- Options expose branch-scoped auto acceptance, exit-zero-on-changes, exit-once-uploaded, skip, force-rebuild, patch builds, and story file/name filters; incompatible filter combinations and malformed patch pairs are rejected.
- TurboSnap's onlyChanged mode selects affected story files, with externals and untraced controls; background v2 hash collection also runs when onlyChanged is unset unless explicitly disabled.
- chromatic init offers Storybook, Playwright, Cypress, and Vitest setup, adds a chromatic package script, and installs framework archive dependencies for the three archive integrations; buildCommand selection routes E2E options through getE2EBuildCommand.
- React Native publishing can reuse artifacts plus manifest.json or build missing artifacts and generate the manifest; standalone react-native-build and generate-manifest commands expose those operations, and initialization rejects TurboSnap for native apps.
- JUnit reporting substitutes {buildNumber}, queries tests in 1,000-item pages, and writes XML; diagnostics and uploadMetadata provide local context output and hosted debugging files.
- Utility commands include trace for changed-file dependency paths, trim-stats-file for simplified stats JSON, and turbosnap-manifest for serialized v2 hashes on stdout; trace rejects package manifests because it cannot diff their contents.
- Programmatic run returns build URLs and test/capture counts that the Action exports; share returns a reserved URL and optional expiry with progress/error/cancellation callbacks, while isChromatic detects the browser user agent or chromatic=true URL marker.