Hard peer dependency on React 18 prevents usage with React 19+

[nogoodusername]

Issue

The current peer dependency configuration restricts usage to React 18 only:

"peerDependencies": {
    "@razorpay/i18nify-js": "^1.0.0",
    "react": "^18.2.0",
    "react-dom": "^18.2.0"
}

This prevents @razorpay/i18nify-react from being used in projects running React 19 or above, which blocks adoption in newer projects and prevents existing projects from upgrading to React 19.

Impact

This affects packages that depend on @razorpay/i18nify-react, such as @razorpay/blade, which cannot be used in React 19+ projects due to this hard dependency constraint.

Requested Change

If there is no hard dependency on React 18-specific features, please update the peer dependency configuration to support React 19 and future versions:

"peerDependencies": {
    "@razorpay/i18nify-js": "^1.0.0",
    "react": "^18.2.0 || ^19.0.0",
    "react-dom": "^18.2.0 || ^19.0.0"
}

Or use a more flexible range if the package is compatible:

"peerDependencies": {
    "@razorpay/i18nify-js": "^1.0.0",
    "react": ">=18.2.0",
    "react-dom": ">=18.2.0"
}

This would allow the package to be used with React 19 and future React versions without blocking upgrades.

[Anubhav-Chauhan3367]

Hi, I'd like to take a stab at this.

My plan:

• Update peerDependencies in package.json to support "react": "^18.2.0 || ^19.0.0" and "react-dom": "^18.2.0 || ^19.0.0"
• Verify no React 18-specific APIs (like ReactDOM.render) are used in the codebase that would break under React 19
• Run the existing test suite against both React 18 and React 19
• Update the README to note React 19 compatibility

Can I take this? Happy to open a draft PR once I've done the initial investigation.