React 19 Support Timeline - NPM Package

[rgonca]

Context

We're evaluating Cognigy Webchat v3 for integration into our Next.js application.

We noticed in the official documentation that the npm package currently requires React < 19:

Restrictions: If your app uses React, the React version must be earlier than 19.0; 19.0 isn't allowed.

Our Situation

We're building on:

• Next.js: 15.5.4
• React: 19.1.0
• Project: Enterprise application with existing React 19 dependency

The hosted script method works perfectly with React 19, which is great! However, for our production environment, we prefer the npm package approach for:

• Version pinning and reproducible builds
• Better integration with our CI/CD pipeline
• TypeScript support
• Dependency management via package.json

Questions

We'd love to understand:

1. Is React 19 support planned for the npm package?

   • If yes, is there a tentative timeline or target release?

2. What are the main blockers preventing React 19 compatibility?

   • Are they related to React 19 API changes, peer dependency constraints, or other factors?

3. Should we plan on using the hosted script for React 19 projects long-term?

   • Or is it worth waiting for npm package compatibility?

4. Would the team be open to community contributions to help with React 19 support?

   • We'd be happy to test beta versions or help with compatibility testing

Our Current Approach for Spike

For our technical evaluation, we're documenting both methods:

• ✅ Hosted Script: Works with React 19 (current recommendation)
• ⚠️ NPM Package: Blocked by React 19 (documented limitation)

Use Case

This information will help us make an informed decision for our production integration and properly document the approach in our technical specifications.

Thank you for your time and for maintaining clear documentation about these requirements!

---

Additional Info:

• Next.js 15 with App Router
• TypeScript project

[msenklogicjoe]

The current NPM package at 3.30.1 already has a peer dependency of:

"peerDependencies": {
	"react": "^18.3.0 || ^19.0.0",
	"react-dom": "^18.3.0 || ^19.0.0"
}

thereby supporting installation into react 19 projects. But it was updated 2 days ago. Maybe recheck if it works for you :-)

[rgonca]

I tested v3.30.1 with the updated peer dependencies in a Next.js 15 + React 19 environment.

TypeError: Cannot read properties of undefined (reading '__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED')

The issue appears to be in the pre-bundled webchat.esm.js file, which expects React 18's structure. React 19 has restructured these internal APIs, causing the bundled code to fail at runtime.

I've tried Webpack alias configurations to force a single React instance, npm overrides and transpilePackages

The pre-compiled bundle can't be transpiled post-installation, so these approaches don't resolve the issue.

Current workaround: The hosted script method works perfectly with React 19. But we can study it again after newer versions