node-red-contrib-telegrambot 18.0.0

V18.0.0

on Node.js NPM

V18.0.0 🎉

First stable release of the V18 line. Migrates the underlying node-telegram-bot-api from v0.66 (CJS, request, bluebird) to v1.x (dual ESM+CJS, native fetch/undici, TypeScript). Promoted from beta to the latest dist-tag — Manage Palette will now offer it as the current version.

⚠️ Read MIGRATION.md before upgrading. Existing V17 flows keep working via a built-in legacy-options compatibility shim, but there are behavioural notes worth knowing.

Requirements

• Node.js ≥ 20.

What changed since V17

• New library core: native fetch/undici transport; dropped bluebird and socks-proxy-agent; added undici and fetch-socks. Dependency floor node-telegram-bot-api@^1.1.2.
• Per-bot undici dispatcher — restores per-bot connection-pool / proxy isolation (SOCKS via fetch-socks), with per-bot keep-alive-pool rebuild on recovery.
• Synchronous require() of the library (v1.1.2 restored CommonJS) — no dynamic-import bridge.
• callApi raw-API escape hatch — msg.payload.type = "callApi" reaches any Bot API method without a dedicated type. See README → Calling the raw Bot API.
• editMessageMedia uploads local files / Buffers / streams natively.
• Legacy-options shim transparently rewrites deprecated msg.payload.options forms (reply_to_message_id, thumb, disable_web_page_preview, keyboard string-shorthand, allow_sending_without_reply) with one-time deprecation warnings.
• Carries forward all V17.4.13–V17.4.17 polling-recovery and queue-wedge fixes.

Upgrade

cd ~/.node-red
npm install node-red-contrib-telegrambot@latest
node-red-restart

Full detail in CHANGELOG.md (18.0.0 + the beta.1–beta.4 entries) and #448.

Thanks to everyone who tested the betas — petermeter69, WJ4IoT, ajanulis, and others.