Allow users to configure custom link component

[virginiacc]

This PR adds the ability for users to globally configure the DSR to use their router's link component.

Changes

• Adds DSR Context that accepts a LinkComponent value. Defaults to a BaseLink component that outputs an anchor element.
• Updates Link component to output the LinkComponent value from the DSR context
• Updates Breadcrumbs component to use Link instead of anchor element
• Removes react-router dependency

Breaking changes

• Updates Link, Header, SecondaryNav, and Breadcrumb components to use to prop instead of href for compatibility with external link components

How to test this PR

1. Wrap app in DSR context provider and pass it a custom link component:

<YourRouterProvider>
  <DSRContext value={{LinkComponent: YourLinkComponent}} >
    // App code
  </DSRContext>

2. Update instances of Link, Breadcrumbs, SecondaryNav, and Header to use to instead of href
3. Check that the component passed in the context is output anywhere the Link component is used

To do

• Add documentation

[github-actions]

PR Preview Action v1.8.1
🚀 View preview at https://cfpb.github.io/design-system-react/pr-previews/pr-563/
Built to branch gh-pages at 2026-05-06 16:58 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[flacoman91]

The null is unnecessary here since the custom type returns that.

Suggested change

	}: CustomLinkProperties): JSXElement | null => {
	}: CustomLinkProperties): JSXElement => {

[virginiacc]

Removed in bbf6a8c

[flacoman91]

we should probably remove the null from the public type OR fallback to BaseLink

[virginiacc]

Removed in bbf6a8c

[flacoman91]

Suggested change

	import { createContext, use } from 'react'
	import { ComponentType, createContext, use } from 'react';

[virginiacc]

Updated in bbf6a8c

[flacoman91]

Suggested change

	LinkComponent: React.ComponentType<BaseLinkProperties> | null;
	LinkComponent: ComponentType<BaseLinkProperties> | null;

[virginiacc]

Updated in bbf6a8c