mtcute/packages/html-parser

@mtcute/html-parser

HTML entities parser for MTCute

This package implements formatting syntax based on HTML, similar to the one available in the Bot API (documented here)

NOTE: The syntax implemented here is not entirely compatible with Bot API HTML.

Please read Syntax below for a detailed explanation

Usage

import { TelegramClient } from '@mtcute/client'
import { HtmlMessageEntityParser } from '@mtcute/html-parser'

const tg = new TelegramClient({ ... })
tg.registerParseMode(new HtmlMessageEntityParser())

tg.sendText(
    'me',
    'Hello, <b>me</b>! Updates from the feed:\n' +
        HtmlMessageEntityParser.escape(
            await getUpdatesFromFeed()
        )
)

Syntax

@mtcute/html-parser uses htmlparser2 under the hood, so the parser supports nearly any HTML. However, since the text is still processed in a custom way for Telegram, the supported subset of features is documented below:

Inline entities

Inline entities are entities that are in-line with other text. We support these entities:

Name	Code	Result (visual)
Bold	<b>text</b>	text
Italic	<b>text</b>	text
Underline	<u>text</u>	text
Strikethrough	<s>text</s>	text
Monospace (code)	<code>text</code>	text
Text link	<a href="https://google.com">Google</a>	Google
Text mention	<a href="tg://user?id=1234567">Name</a>	N/A

Note

: <strong>, <em>, <ins>, <strike>, <del> are not supported because they are redundant

Note

In most cases, you can only use IDs of users that were seen by the client while using given storage.

Alternatively, you can explicitly provide access hash like this: <a href="tg://user?id=1234567&hash=abc">Name</a>, where abc is user's access hash written as a base-16 unsigned integer. Order of the parameters does matter, i.e. tg://user?hash=abc&id=1234567 will not be processed as expected.

Block entities

The only block entity that Telegram supports is <pre>, therefore it is the only tag we support too.

Optionally, language for <pre> block can be specified like this:

<pre language="typescript">export type Foo = 42</pre>

However, since syntax highlighting hasn't been implemented in official Telegram clients, this doesn't really matter 🤷‍♀️

Code	Result (visual)
<pre>multiline\ntext</pre>	multiline text
<pre language="javascript"> export default 42 </pre>	export default 42

Nested and overlapped entities

HTML is a nested language, and so is this parser. It does support nested entities, but overlapped entities will not work as expected!

Overlapping entities are supported in unparse(), though.

Code	Result (visual)
<b>Welcome back, <i>User</i>!</b>	Welcome back, User!
<b>bold <i>and</b> italic</i>	bold and italic ⚠️ word "italic" is not actually italic!
<b>bold <i>and</i></b><i> italic</i> ⚠️ this is how unparse() handles overlapping entities	**
bold and** italic

Escaping

Escaping in this parser works exactly the same as in htmlparser2.

This means that you can keep <>& symbols as-is in some cases. However, when dealing with user input, it is always better to use HtmlMessageEntityParser.escape