fix: addon detection in automigrations on windows

[mrginglymus]

Addon detection is done by sniffing the value returned by getAddonNames, which pulls values from storybook config.

However, the wrap-require automation wraps addon references in an absolute path resolver.

On windows this means that addons are now reported as e.g. @storybook\\addon-a11y, which defeats detection

Closes #31936

What I did

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 section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

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 canary-release-pr.yml --field pr=<PR_NUMBER>

Greptile Summary

Fixed addon detection in Storybook automigrations for Windows environments by normalizing path separators.

• Modified code/core/src/common/utils/get-addon-names.ts to handle Windows-style backslash path separators
• Fixed issue where addons like @storybook\addon-a11y weren't being properly detected on Windows
• Ensures consistent addon path handling across different operating systems
• Maintains compatibility with the wrap-require automation system

[greptile-apps]

LGTM

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit e0e4a3d

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

---

☁️ Nx Cloud last updated this comment at 2025-07-08 20:35:15 UTC

[mrginglymus]

Whoops, didn't actually fix getAddonNames correctly. the addonA11yAddonTest checks has

const hasA11yAddon = !!addons.find((addon) => addon.includes('@storybook/addon-a11y'));

which threw me off. It presumably should be

const hasA11yAddon = addons.includes('@storybook/addon-a11y');

[storybook-pr-benchmarking]

Package Benchmarks

^{Commit: e0e4a3d, ran on 8 July 2025 at 20:25:15 UTC}

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

@storybook/cli

	Before	After	Difference
Dependency count	217	217	0
Self size	582 KB	582 KB	0 B
Dependency size	94.81 MB	93.66 MB	🎉 -1.16 MB 🎉
Bundle Size Analyzer	Link	Link

@storybook/codemod

	Before	After	Difference
Dependency count	186	186	0
Self size	31 KB	31 KB	0 B
Dependency size	78.91 MB	77.76 MB	🎉 -1.16 MB 🎉
Bundle Size Analyzer	Link	Link