If the build directory we defined is empty, try to detect the actual build output directory from the Storybook build log and warn about it.
Show a user-friendly error message if we still don't find any Storybook files to publish.
We now read package.json using pkgUp, so theoretically you can run chromatic from a subdirectory.
Added the --output-dir (-o) flag to use instead of a temp dir.
Added buildScript to the error json output so we won't have to ask for it in support every time.
Added a global promise rejection handler, in case we accidently forget to catch them.
Added a user-friendly error message when build-storybook fails.
Fixed the --debug flag so it actually prints something.
Fixed the --only flag.
Fixed issue with node-loggly-bulk when using Yarn 2.

5.1.0-alpha.4

published 5.1.0-alpha.4 • 5 years ago

5.1.0-alpha.3

published 5.1.0-alpha.3 • 5 years ago

published 5.1.0-alpha.2 • 5 years ago

published 5.1.0-alpha.1 • 5 years ago

published 5.1.0-alpha.0 • 5 years ago

published 5.0.0 • 5 years ago

Changelog

Completely overhauled the CLI, with improved UX and better error handling
Removed JSDOM and its shims to avoid a whole category of issues with broken builds
Added a version upgrade check that warns when a new major update is available
Added --junit-report to generating build reports for integration with other tools
Changed --only to accept a simple glob
Moved documentation to the Chromatic website