Bug in fetchMessages, throws error

[yairyairyair]

code is:

bot.onDirectMessage(async (thread, message) => {
  console.log('New direct message received:', message);
  const messagesFromThread = await thread.adapter.fetchMessages(thread.id, { limit: 10 }); // this throws an error
  const aiMessages = await toAiMessages(messagesFromThread.messages);
  const response = await streamText({
    model: gateway('google/gemini-2.5-flash-lite'),
    messages: aiMessages,
  })

  const responseFromThread = await thread.post(response.fullStream);
});

[mikipalet]

Thanks for the clear repro 🙏 Root cause confirmed and fixed in #4 (shipping in v0.3.0).

What was happening: fetchMessages piped the REST GET /messages response straight into the internal parseMessage(). The REST endpoint returns a flat message shape (senderId / message / createdAt), but parseMessage() expects the webhook shape (sender.id / text / sentAt), so it threw TypeError: Cannot read properties of undefined (reading 'id') on raw.sender.id. (Our own test masked it by mocking the webhook shape.)

Fixed:

• fetchMessages now normalizes the REST shape before parsing, so it no longer throws.
• It also honors the options you passed ({ limit: 10 }) plus cursor / direction, and returns a real nextCursor for pagination. Default direction: 'backward' returns the most recent N, oldest-first within the page.

While in there we fixed two more things you flagged in support:

• thread.post(stream) now delivers the full streamed response on WhatsApp (it was only sending the first chunk, because streaming relied on message edits which WhatsApp doesn't support; non-editable platforms now buffer and post once).
• onReaction now fires for WhatsApp/Telegram reactions instead of them coming through as onDirectMessage (new reaction.received webhook event). After upgrading, subscribe your webhook to reaction.received to receive them.

Closing as resolved by #4. It'll be on npm once v0.3.0 publishes.