
Security News
Another Round of TEA Protocol Spam Floods npm, But It’s Not a Worm
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.
@botpress/chat
Advanced tools
npm install @botpress/chat # for npm
yarn add @botpress/chat # for yarn
pnpm add @botpress/chat # for pnpm
The @botpress/chat package exports a Client class that can be used to interact with the Botpress Chat API.
import _ from 'lodash'
import * as chat from '@botpress/chat'
const main = async () => {
/**
* You can find your webhook id in the the Botpress Dashboard.
* Navigate to your bot's Chat Integration configuration. Look for:
* https://webhook.botpress.cloud/$YOUR_WEBHOOK_ID
*/
const webhookId = process.env.WEBHOOK_ID
if (!webhookId) {
throw new Error('WEBHOOK_ID is required')
}
// 0. connect and create a user
const client = await chat.Client.connect({ webhookId })
// 1. create a conversation
const { conversation } = await client.createConversation({})
// 2. send a message
await client.createMessage({
conversationId: conversation.id,
payload: {
type: 'text',
text: 'hello world',
},
})
// 3. sleep for a bit
await new Promise((resolve) => setTimeout(resolve, 2000))
// 4. list messages
const { messages } = await client
.listMessages({
conversationId: conversation.id,
})
.then(({ messages }) => ({
messages: _.sortBy(messages, (m) => new Date(m.createdAt).getTime()),
}))
const botResponse = messages[1]
console.log("Bot's response:", botResponse.payload)
}
void main()
.then(() => {
console.log('done')
process.exit(0)
})
.catch((err) => {
console.error(err)
process.exit(1)
})
You can also listen for messages and events in real-time.
// ...
const listener = await client.listenConversation({
id: conversation.id,
})
const botResponse = await new Promise<chat.Message>((resolve) => {
const onMessage = (ev: chat.Signals['message_created']) => {
if (ev.userId === client.user.id) {
// message created by my current user, ignoring...
return
}
listener.off('message_created', onMessage)
resolve(ev)
}
listener.on('message_created', onMessage)
})
console.log("Bot's response:", botResponse.payload)
The Client class does not automatically reconnect to the server if the connection is lost. This allow's you to handle reconnection in a way that makes sense for your application. To be notified when the connection is lost, you can listen for the error event:
const state = { messages } // your application state
const onDisconnection = async () => {
try {
await listener.connect()
const { messages } = await client.listMessages({ conversationId: conversation.id })
state.messages = messages
} catch (thrown) {
console.error('failed to reconnect, retrying...', thrown)
setTimeout(onDisconnection, 1000) // consider using a backoff strategy
}
}
listener.on('error', (err) => {
console.error('connection lost', err)
void onDisconnection()
})
FAQs
Botpress Chat API Client
We found that @botpress/chat demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.

Security News
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.