Skip to content

Conversation

@ndelangen
Copy link
Member

@ndelangen ndelangen commented Nov 14, 2025

See #32644
Telescopes on #32799

What I did

  • I've moved the source-code of @storybook/addon-onboarding into the storybook package.
  • Specifically the preset code is moved to common-preset.
  • The manager code is now registered always (TBD if that needs changing) from common-manager (where the other built-in addons are also added)
  • The CLI init command no longer adds it to projects.
  • references to addon-onboarding have been removed from docs and code.

After this merge, users should un-install addon-onboarding.
We should likely do a follow-up PR, with an auto-migration, removing it.

This is the easy first step, long term we'd want to incorporate the addon further into the manager-ui (core/src/manager) directly; we want to do that with all built-in addons.

Checklist for Contributors

Testing

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

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

This should make the installation of addon-onboarding no longer needed, in fact, we should ensure it's no longer installed.

The CLI should never install addon-onboarding, would be a change worth manually verifying.

There should be no regressions/changes in how onboarding functions.

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>

});

export default [
onboardingManager,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we need to make this optional?

If that's indeed needed, we can go about it in a few ways.
Considering the UI code is already all lazy-loaded, maybe we can do it at runtime, or maybe we don't inject here, based on a global we inject via the common-preset?

@nx-cloud
Copy link

nx-cloud bot commented Nov 14, 2025

View your CI Pipeline Execution ↗ for commit 1f59bf5

Command Status Duration Result
nx run-many -t build --parallel=3 ✅ Succeeded 43s View ↗

☁️ Nx Cloud last updated this comment at 2025-11-26 16:23:19 UTC

available: ({ index }) =>
!!index &&
'example-button--primary' in index &&
addons.experimental_getRegisteredAddons().includes('@storybook/addon-onboarding'),
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just removed the condition checking if onboarding is installed/added.

On a side-note, can we please not use this broken API?
If you need to detect an addon presence at runtime, add a global variable or something, this API will hold us back from properly refactoring the addon system.

* Testing tools (e.g. [Jest](https://jestjs.io/), [Vitest](https://vitest.dev/), [Playwright](https://playwright.dev/)).
* Package manager information (e.g., `npm`, `yarn`).
* Monorepo information (e.g., [NX](https://nx.dev/), [Turborepo](https://turborepo.org/)).
* In-app events (e.g., [Storybook guided tour](https://github.com/storybookjs/addon-onboarding), [UI test run](../writing-tests/integrations/vitest-addon.mdx#storybook-ui)).
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The link no-longer makes any sense, as it's not an addon, there's no readme.

@storybook-app-bot
Copy link

storybook-app-bot bot commented Nov 14, 2025

Package Benchmarks

Commit: 1f59bf5, ran on 26 November 2025 at 16:15:16 UTC

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

storybook

Before After Difference
Dependency count 39 39 0
Self size 19.64 MB 19.91 MB 🚨 +265 KB 🚨
Dependency size 16.40 MB 16.40 MB 🎉 -14 B 🎉
Bundle Size Analyzer Link Link

@storybook/cli

Before After Difference
Dependency count 173 173 0
Self size 773 KB 773 KB 🎉 -35 B 🎉
Dependency size 66.61 MB 66.87 MB 🚨 +265 KB 🚨
Bundle Size Analyzer Link Link

@storybook/codemod

Before After Difference
Dependency count 166 166 0
Self size 30 KB 30 KB 🎉 -14 B 🎉
Dependency size 65.18 MB 65.44 MB 🚨 +265 KB 🚨
Bundle Size Analyzer Link Link

create-storybook

Before After Difference
Dependency count 40 40 0
Self size 999 KB 999 KB 🎉 -144 B 🎉
Dependency size 36.04 MB 36.31 MB 🚨 +265 KB 🚨
Bundle Size Analyzer node node

Base automatically changed from checklist-tasks to onboarding-checklist November 14, 2025 16:47
@ghengeveld ghengeveld marked this pull request as ready for review November 14, 2025 20:54
Base automatically changed from onboarding-checklist to next November 21, 2025 08:14
@github-actions github-actions bot added the Stale label Dec 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants