fix(cc-widgets): externalize react/jsx-runtime to prevent bundling Re…

[cmullenx]

COMPLETES #. https://jira-eng-sjc12.cisco.com/jira/browse/CAI-7686

Ability of epic-app to consume the widgets

When webex/cc-widgets is consumed by a Vite-based application the bundled react/jsx-runtime and react/jsx-dev-runtime modules inside cc-widgets cause an error. This happens because webpack bundles a separate copy of React's jsx-runtime into the cc-widgets output, which then conflicts with the host application's React instance during Vite's esbuild pre-bundling. Vite cannot deduplicate React when jsx-runtime is embedded inside the webpack bundle rather than declared as an external dependency.

Updating the webpack externals for cc-widgets
Added react/jsx-runtime and react/jsx-dev-runtime to the externals configuration in packages/contact-center/cc-widgets/webpack.config.js. This ensures webpack generates require("react/jsx-runtime") calls instead of bundling the jsx-runtime code, allowing the consuming bundler (Vite/esbuild) to resolve these to the host application's single React instance.

This update also had to be made in the cc-digital-interactions package

< DESCRIBE THE CONTEXT OF THE ISSUE >

Vite based application could not use latest version of widgets

Updated webpack build

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Tooling change
• Internal code refactor

The following scenarios were tested

• The testing is done with the amplify link
  Verified that the original npm webex/cc-widgets@1.28.0-next.27 (without this fix) reproduces the ReactCurrentOwner error in a Vite-based app (epic-app)
  Rebuilt cc-widgets with the jsx-runtime externals, copied dist to epic-app, cleared Vite cache, and confirmed the ReactCurrentOwner error is resolved
  All existing unit tests pass (pre-commit hook ran successfully: cc-store, cc-components, cc-digital-channels, cc-widgets, cc-station-login, cc-task, cc-ui-logging, cc-user-state, test-fixtures)

The GAI Coding Policy And Copyright Annotation Best Practices

• GAI was not used (or, no additional notation is required)
• Code was generated entirely by GAI
• GAI was used to create a draft that was subsequently customized or modified
• Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
• Tool used for AI assistance (GitHub Copilot / Other - specify)
  • Github Copilot
  • Other - Please Specify
• This PR is related to
  • Feature
  • Defect fix
  • Tech Debt
  • Automation

Checklist before merging

• I have not skipped any automated checks
• All existing and new tests passed
• I have updated the testing document
• I have tested the functionality with amplify link

---

Make sure to have followed the contributing guidelines before submitting.

[aws-amplify-us-east-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-635.d1b38q61t1z947.amplifyapp.com