CLI: Explicitly tell whether smoke tests passed or failed

[Sidnioulz]

What I did

Ensured smoke test output is clear and legible, especially when no problems are found.

This helps agents run smoke tests and conclude all is well.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

ø

Manual testing

Run storybook dev --smoke-test on the monorepo

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>

Summary by CodeRabbit

• Bug Fixes

  • Improved smoke-test reporting: failures now emit an error and detailed logs, while successful runs show a clear success message.

• Chores

  • Standardized build output formatting to ensure a consistent outro/message is printed for both pass and fail outcomes.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 513b3c2

Command	Status	Duration	Result
nx run-many -t compile,check,knip,test,lint,fmt...	✅ Succeeded	8m 14s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-04-01 08:00:19 UTC

[Copilot]

Pull request overview

Improves the CLI output for --smoke-test runs so it explicitly reports whether smoke tests passed or failed, making results easier to interpret (especially in automated/agent runs).

Changes:

• Add explicit success/failure messaging for smoke test results.
• Use CLI_COLORS formatting and ensure an outro is printed before exiting.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 56aa1e21-44eb-417e-825f-91881d07fe2b

📥 Commits

Reviewing files that changed from the base of the PR and between 0538a15 and 513b3c2.

📒 Files selected for processing (1)

• code/core/src/core-server/build-dev.ts

---

📝 Walkthrough

Walkthrough

Conditionalized smoke-test reporting in buildDevStandalone: failures now log an error and stack traces; successes log a colored success step. A blank logger.outro('') is emitted before process.exit(...). CLI_COLORS was added to the logger imports.

Changes

Cohort / File(s)	Summary
Smoke-test Result Handling code/core/src/core-server/build-dev.ts	Changed smoke-test branch to check problems.length > 0; on failure call logger.error('Smoke tests failed.') and log aggregated stacks, on success call logger.step(CLI_COLORS.success('Smoke Tests passed, exiting.')). Added logger.outro('') before process.exit(...) and imported CLI_COLORS from storybook/internal/node-logger.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[storybook-app-bot]

Package Benchmarks

^{Commit: 513b3c2, ran on 1 April 2026 at 08:01:32 UTC}

The following packages have significant changes to their size or dependencies:

storybook

	Before	After	Difference
Dependency count	50	50	0
Self size	20.51 MB	20.47 MB	🎉 -35 KB 🎉
Dependency size	16.55 MB	16.55 MB	0 B
Bundle Size Analyzer	Link	Link

@storybook/cli

	Before	After	Difference
Dependency count	184	184	0
Self size	782 KB	782 KB	0 B
Dependency size	67.73 MB	67.70 MB	🎉 -35 KB 🎉
Bundle Size Analyzer	Link	Link

@storybook/codemod

	Before	After	Difference
Dependency count	177	177	0
Self size	32 KB	32 KB	🚨 +36 B 🚨
Dependency size	66.26 MB	66.22 MB	🎉 -35 KB 🎉
Bundle Size Analyzer	Link	Link

create-storybook

	Before	After	Difference
Dependency count	51	51	0
Self size	1.04 MB	1.04 MB	🚨 +72 B 🚨
Dependency size	37.06 MB	37.03 MB	🎉 -35 KB 🎉
Bundle Size Analyzer	node	node

[yannbf]

LGTM!