fix(react): enable React Compiler for hooks

[joshblack]

Follow up to the React Compiler migration work. This PR enables React Compiler for the remaining hook utilities under packages/react/src/hooks.

Changelog

New

• Add an internal dependency-list effect helper used by hook utilities that expose dependency-list APIs.

Changed

• Update hook utilities to avoid React hook-rule suppressions while preserving the existing public hook APIs.
• Remove hook files from the React Compiler unsupported list.

Removed

• Remove React Compiler exclusions for useAnchoredPosition, useFocusTrap, useFocusZone, useMenuInitialFocus, useOnEscapePress, useResizeObserver, and useSafeTimeout.

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

This keeps the published API the same and updates our internal compiler compatibility for hooks.

Testing & Reviewing

Would love a review on the dependency tracking changes in the hook utilities, especially useFocusTrap and useAnchoredPosition, since those preserve existing dependency-list behavior while avoiding React Compiler skips.

Verified with:

• npm run build
• npm test -- --run
• npm run type-check
• npm run lint
• npm run lint:css
• npm run format:diff
• packages/react/node_modules/.bin/tsx script/react-compiler-migration-status.mts
• Direct React Compiler transform check for the enabled hook files

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-ui (Learn more about how to run integration tests)

[changeset-bot]

🦋 Changeset detected

Latest commit: f9a6462

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	Patch

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]

⚠️ Action required

👋 Hi, this pull request contains changes to the source code that github/github-ui depends on. If you are GitHub staff, test these changes with github/github-ui using the integration workflow. If this doesn't work, you can also use the original workflow here. Check the integration testing docs for step-by-step instructions. Or, apply the integration-tests: skipped manually label to skip these checks.

To publish a canary release for integration testing, apply the Canary Release label to this PR.

[joshblack]

@copilot be specific about the hooks changed.

[Copilot]

Updated in 73cd1b5 — changeset now lists each hook by name.

[joshblack]

@copilot I'm not a big fan of this approach. Let's find something better

[Copilot]

Totally open to a different approach here. The core problem is that these hooks expose a caller-supplied DependencyList which React Compiler can't track statically, so I reached for a manual comparison wrapper. What direction were you thinking? For example: dropping the dep-list override entirely, converting to a callback-based API, or something else? Happy to implement once the direction is clear.

[joshblack]

@copilot I'm not a big fan of the useDependencyList approach. Let's try something else

[Copilot]

@copilot I'm not a big fan of the useDependencyList approach. Let's try something else

Happy to change direction. Before I implement something, which of these would you prefer?

1. Inline the comparison logic — replace useDependencyListEffect with a useRef-based comparison directly inside each hook (same semantics, no shared abstraction)
2. Stable callback pattern — instead of accepting a DependencyList, these hooks accept a () => void effect callback (caller stabilizes it with useCallback); the hook just calls it in a regular useEffect([callback])
3. Remove the dependencies parameter — drop it from the public API and always compute dependencies inside the hook (potential behavior change for existing callers)
4. Keep the eslint-disable pattern and leave these hooks in the React Compiler exclusion list — revert to the original code, just not compiler-compatible yet

Or if you have a different approach in mind, let me know and I'll implement that.