@bpinternal/thicktoken

中文文档
3.1.0发布于 2026/07/23ISCTypeScriptESM + CJS零依赖构建来源已验证近 30 天下载 3.1万

A bundled cl100k tokenizer (Rust→WASM) with count/truncate/split helpers

原始使用文档
文档目录3 节
  1. Variants (edge / size-sensitive targets)
  2. Cloudflare Workers (workerd)
  3. Disclaimer ⚠️

ThickToken

A bundled cl100k tokenizer with added helper functions (count / truncate / split), powered by our own Rust→WASM build (see wasm/, engine: tokie, MIT © Chonkie, Inc. — see NOTICE). Historically backed by tiktoken — the API is unchanged.

  • count(text, { approximate }) — approximate by default on large inputs (statistical sampling, within a few %, ~100× faster); pass { approximate: false } for exact.
  • truncate(text, n) — exact; keeps the first n tokens (negative n removes from the end). Only tokenizes the window it needs, so it's fast on huge inputs.
  • split(text) / splitAndSlice(text) — per-token strings / sliceable collection.

Variants (edge / size-sensitive targets)

Same API, smaller vocab (truncated cl100k merges — valid BPE by prefix-closure). One shared wasm engine; each entry bundles only its own vocab asset. Regenerate assets with node wasm/scripts/gen-assets.mjs.

importvocabtotal gz (ESM)initcounts vs cl100k
@bpinternal/thicktokencl100k (full)~647 KB~60 msexact
@bpinternal/thicktoken/litecl50k~392 KB~25 msovercounts ~+3-7%
@bpinternal/thicktoken/microcl25k~275 KB~13 msovercounts ~+8-20%

Truncated variants only ever overcount — safe for budget enforcement (they trim a bit more, never overflow a window). Do not use them for billing math or exact window packing; inflation is content-dependent (worst on emoji/unicode-dense text).

Cloudflare Workers (workerd)

workerd bans runtime WASM compilation (new WebAssembly.Module(bytes)), so the default builds — which inline the engine WASM as base64 and compile it at import time — can't run there. Two mechanisms handle this:

  1. workerd export condition (zero-config). Bundlers/runtimes that honor the workerd condition (wrangler does) resolve every entry to a *.workerd.mjs build in which the engine .wasm ships as a separate dist file and stays a static import — workerd compiles it at deploy time and hands the module to initSync precompiled. On workerd, the root @bpinternal/thicktoken entry resolves to the micro (cl25k) asset — the smallest footprint, and prompt budgeting doesn't need exact cl100k counts. Use @bpinternal/thicktoken/full if you really need exact cl100k counts on Workers.

  2. getWasmTokenizer({ wasmModule }) (explicit injection). Pass your own precompiled WebAssembly.Module (e.g. from a static .wasm import) and the engine skips runtime compilation entirely:

    import { getWasmTokenizer } from '@bpinternal/thicktoken/micro'
    import wasmModule from '@bpinternal/thicktoken/engine.wasm' // static import
    const tokenizer = await getWasmTokenizer({ wasmModule })
    

The vocab .gz assets are plain data (inflated inside the WASM engine) and stay inlined in every build — only the engine .wasm needs the special handling.

Disclaimer ⚠️

This package is published under the @bpinternal organization. All packages of this organization are meant to be used by the Botpress team internally and are not meant for our community. Since the packages are catered to our own use-cases, they might have less stable APIs, receive breaking changes without much warning, have minimal documentation and lack community-focused support. However, these packages were still left intentionally public for an important reason : We Love Open-Source. Therefore, if you wish to install or fork this package feel absolutely free to do it. We strongly recommend that you tag your versions properly.

The Botpress Engineering team.

版本与发布记录

@bpinternal/thicktoken 共发布 11 个版本,首次发布于 2025/01/07;过去 12 个月发布了 6 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
3.1.0latest2026/07/233 个月前
3.0.02026/07/024 个月前
2.0.02026/02/108 个月前
1.2.12026/02/108 个月前
1.2.02026/02/079 个月前
1.1.02026/02/079 个月前

关于 @bpinternal/thicktoken 的常见问题

@bpinternal/thicktoken 是什么?

A bundled cl100k tokenizer (Rust→WASM) with count/truncate/split helpers

如何安装 @bpinternal/thicktoken?

在项目目录运行 npm install @bpinternal/thicktoken,或使用 pnpm add / yarn add / bun add。

@bpinternal/thicktoken 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@bpinternal/thicktoken 支持 ESM 还是 CommonJS?

同时提供 ES Module 与 CommonJS 入口,import 和 require() 都可以使用,打包工具会自动选择合适的版本。

@bpinternal/thicktoken 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=16.0.0。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@bpinternal/thicktoken 可以商用吗?

@bpinternal/thicktoken 使用 ISC 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@bpinternal/thicktoken 的下载量有多少?

根据 npm 官方下载统计,@bpinternal/thicktoken 在 2026/10/09 – 2026/11/07 这 30 天内被下载 31,498 次,日均约 1,050 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@bpinternal/thicktoken 还在维护吗?

最新版本 3.1.0 发布于 2026/07/23(3 个月前);至今共发布 11 个版本,其中过去 12 个月发布了 6 个;首次发布于 2025/01/07。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。