React components for TalkJS

The @talkjs/react library makes it easy to use TalkJS inside a React web application by providing React components for our pre-built chat UIs.

@talkjs/react encapsulates talkjs, the framework-independent TalkJS JavaScript SDK. For anything related to data manipulation, such as synchronizing user data, or creating and joining conversations, use the JavaScript SDK.

TypeScript bindings are included.

If you encounter any problems with @talkjs/react, please open an issue. If you have a problem with TalkJS itself, or if you're not sure where the problem lies, it's better to open a chat for support. TalkJS support is staffed by engineers.

Prerequisites

- A TalkJS account. TalkJS provides a ready-to-use chat client for your application. Your account gives you access to TalkJS's free development environment.
- A React app that you will add TalkJS to

Documentation

- Getting started guide
- React SDK reference docs
- Team chat tutorial and example code

Examples

The following examples use the Session and Chatbox components from the React SDK to create a chatbox UI.

For both examples, you'll first need to install both @talkjs/react and the talkjs JavaScript package:

``sh
npm install talkjs @talkjs/react


or


yarn add talkjs @talkjs/react
`

$3

This example demonstrates how to create a TalkJS session with an existing user and view a chatbox UI with an existing conversation. We'll use a sample user and conversation that are already included in your test environment.

Add the following code to your React app. Replace the with your test environment App ID from the Settings tab of the TalkJS dashboard:

`jsx
import { Session, Chatbox } from "@talkjs/react";

function ChatComponent() {
return (

conversationId="sample_conversation"
style={{ width: "100%", height: "500px" }}
>

);
}

export default ChatComponent;
`

$3

This example demonstrates how to sync a user and conversation that you create with the JavaScript SDK.

Add the following code to your React app:

`jsx
import { useCallback } from "react";
import Talk from "talkjs";
import { Session, Chatbox } from "@talkjs/react";

function ChatComponent() {
const syncUser = useCallback(
() =>
return new Talk.User({
id: "nina",
name: "Nina",
email: "nina@example.com",
photoUrl: "https://talkjs.com/new-web/avatar-7.jpg",
welcomeMessage: "Hi!",
role: "default",
}),
[],
);

const syncConversation = useCallback((session) => {
// JavaScript SDK code here
const conversation = session.getOrCreateConversation("welcome");

const other = new Talk.User({
id: "frank",
name: "Frank",
email: "frank@example.com",
photoUrl: "https://talkjs.com/new-web/avatar-8.jpg",
welcomeMessage: "Hey, how can I help?",
role: "default",
});
conversation.setParticipant(session.me);
conversation.setParticipant(other);

return conversation;
}, []);

return (

syncConversation={syncConversation}
style={{ width: "100%", height: "500px" }}
>

);
}

export default ChatComponent;
`

For more details and explanation, see our getting started guide.

Contributing

This library is open-source and permissively licensed (MIT).

To contribute a PR, we require that you fill out a contributor license agreement (CLA) so that we (TalkJS) retain ownership over this repository. Pick the Corporate CLA or the individual CLA. Note that you do not need to sign anything to be able to fork this repository and make changes for your own use.

Should you want to contribute, please take note of the design notes below.

Design notes

This library has been designed to be maximally forward-compatible with future TalkJS features. The talkjs package is a peer dependency, not a direct dependency, which means you can control which TalkJS version you want to be on. It also means you won't need to wait for a new version of @talkjs/react to be published before you can get access to new TalkJS features.

From our (TalkJS) perspective, it means we have a lower maintenance burden: we can ship new JS features without having to update (and test and verify) @talkjs/react.

This works because vanilla TalkJS is fully backward compatible and has a very consistent design: all UI components are instantiated and mutated in the same way. The React components simply treats any prop that looks like an event (name starts with "on") like an event. Also, barring some props unique to the react components (such as syncConversation, style and loadingComponent), all remaining props are simply assumed to be valid options to pass to createChatbox and its sister methods.

This way, if TalkJS eg adds support for a new event or a new option, this will Just Work without updating @talkjs/react. Modern TypeScript features (notably, template literal types) let us do this in a fully type-safe manner: If you upgrade talkjs, then your invocations to @talkjs/react` components will allow new props.

Any future changes should follow this same design: they should be maximally forward compatible.