[v5] Add support for React 16 and 17

[jo-arroyo]

No description provided.

[Copilot]

Pull request overview

Updates @azure/msal-react v5 metadata, docs, and CI configuration to advertise and validate compatibility with React 16.8+ and React 17 (in addition to React 18/19).

Changes:

• Extend @azure/msal-react peer dependency range for react to >=16.8.0 <20.0.0.
• Update msal-react documentation to reflect React 16/17 support and provide React 16/17 rendering guidance.
• Add a compatibility E2E pipeline matrix intended to run samples against multiple React majors.

Reviewed changes

Copilot reviewed 11 out of 12 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
samples/msal-react-samples/typescript-sample/package.json	Broaden React/ReactDOM dependency ranges in the TS sample
samples/msal-react-samples/react-router-sample/package.json	Broaden React/ReactDOM dependency ranges in the router sample
samples/msal-react-samples/b2c-sample/package.json	Broaden React/ReactDOM dependency ranges in the B2C sample
package-lock.json	Update lockfile to reflect peer/dependency range changes
lib/msal-react/package.json	Update react peer dependency range for msal-react v5
lib/msal-react/docs/migration-guide-v4-v5.md	Document updated React support and peer dependency meaning
lib/msal-react/docs/getting-started.md	Update React support statement and add React 16/17 render example
lib/msal-react/README.md	Update supported React version table for v5
lib/msal-react/AGENTS.md	Update supported environments guidance for contributors
change/@azure-msal-react-fc1bd3a1-c1c1-43f6-b654-5934d367b063.json	Beachball changefile for msal-react peer dependency update
.pipelines/templates/msal-react-compat-e2e.yml	New/updated matrix pipeline template for React version compatibility runs
.pipelines/3p-e2e.yml	Wire up the new compat template into 3P E2E pipeline

Comments suppressed due to low confidence (3)

.pipelines/templates/msal-react-compat-e2e.yml:30

• The compatibility matrix includes React 16, but the samples being tested depend on MUI v5, which (per package-lock) declares peerDependencies requiring React ^17/^18/^19. Running the E2E jobs with React 16 is therefore expected to hit peer dependency resolution issues unless additional dependency adjustments are made. Consider removing React 16 from the default matrix for these samples, or splitting the matrix so React 16 is only used with samples/dependency sets that actually support it.
  .pipelines/templates/msal-react-compat-e2e.yml:94
• The override step sets react/react-dom/@types/* overrides at the repo root and reruns npm install. The repo currently uses @testing-library/react@16.3.0, which has peerDependencies on React 18/19 (see package-lock), so forcing React 16/17 is likely to cause npm install resolution failures. Consider scoping the overrides to the sample workspace only, or also overriding dev/test dependencies (e.g., @testing-library/react) to versions compatible with the targeted React major for these compatibility jobs.
  .pipelines/templates/msal-react-compat-e2e.yml:145
• The screenshot folder creation uses backslashes in the path (replace(..., '/', '\') plus \test\...). On linux agents (the default in this template), backslashes are treated as literal characters, so this will create a different directory than later steps reference (which use forward slashes). Consider using $(samplePath)/test/screenshots/react${{ rv.version }} on linux and a separate windows-specific path if needed.

[Copilot]

Pull request overview

Copilot reviewed 122 out of 126 changed files in this pull request and generated 10 comments.

[Copilot]

Pull request overview

Copilot reviewed 119 out of 123 changed files in this pull request and generated 11 comments.

[tnorling]

I think all of this can actually just be removed from the migration guide as there's no longer a breaking change between v4 and v5