chore(_VisuallyHidden): Convert internal component _VisuallyHidden to CSS module styling

[jonrohan]

Changelog

New

Changed

Convert internal component _VisuallyHidden to CSS module styling

Removed

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; if selected, include a brief description as to why

Testing & Reviewing

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

[changeset-bot]

🦋 Changeset detected

Latest commit: 9e02a81

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@primer/react	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks!

[github-actions]

size-limit report 📦

Path	Size
packages/react/dist/browser.esm.js	95.24 KB (-0.03% 🔽)
packages/react/dist/browser.umd.js	95.29 KB (-0.03% 🔽)

[Copilot]

Pull Request Overview

This PR replaces the styled‐component implementation of the internal _VisuallyHidden component with a CSS module and updates snapshots to use the new InternalVisuallyHidden class.

• Migrates _VisuallyHidden from styled.span to a BoxWithFallback + CSS module.
• Introduces _VisuallyHidden.module.css with the visually‐hidden styles.
• Regenerates snapshots across several components to reference the new CSS class.

Reviewed Changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/react/src/_VisuallyHidden.tsx	Replaced styled‐component implementation with CSS module and BoxWithFallback.
packages/react/src/_VisuallyHidden.module.css	New CSS module defining the .InternalVisuallyHidden styles.
packages/react/src/Token/tests/snapshots/Token.test.tsx.snap	Updated snapshot spans to use InternalVisuallyHidden class.
packages/react/src/TextInput/snapshots/TextInput.test.tsx.snap	Updated snapshot spans to use InternalVisuallyHidden class.
packages/react/src/CircleBadge/snapshots/CircleBadge.test.tsx.snap	Snapshot class names updated (unrelated styled-component change).
.changeset/smooth-steaks-hug.md	Adds a changeset for the minor version bump.

Comments suppressed due to low confidence (3)

packages/react/src/_VisuallyHidden.tsx:19

• [nitpick] There are no unit tests covering the new _VisuallyHidden component; consider adding tests for both visible and hidden states to ensure the CSS module is applied correctly.

<BoxWithFallback as={as} className={clsx(...

packages/react/src/_VisuallyHidden.tsx:11

• You reference React.ElementType and React.HTMLAttributes but never import React; please add import React from 'react' or import type {React} from 'react' to satisfy the type usage.

function VisuallyHidden({

packages/react/src/CircleBadge/snapshots/CircleBadge.test.tsx.snap:5

• [nitpick] These CircleBadge snapshot updates seem unrelated to the _VisuallyHidden change—you may want to verify they’re intentional or revert to avoid introducing noisy snapshot diffs.

  class="sc-fUnMCh kvrJCk"

[primer-integration]

👋 Hi from github/github! Your integration PR is ready: https://github.com/github/github/pull/379060

[primer-integration]

🟢 golden-jobs completed with status success.

[github-actions]

👋 Hi, there are new commits since the last successful integration test. We recommend running the integration workflow once more, unless you are sure the new changes do not affect github/github. Thanks!

[github-actions]

👋 Hi, there are new commits since the last successful integration test. We recommend running the integration workflow once more, unless you are sure the new changes do not affect github/github. Thanks!