@telixon/core bundle size

What @telixon/core adds to a consumer's initial download, measured from a real Vite production build. The app imports the entire public API, including the input controller, which makes the initial figure a ceiling for any real application.
Engine compiled from Google's libphonenumber source at github.com/google/libphonenumber@ba2a029.
Generated 2026-10-18T01:29:07.035Z.

21.8 KB

initial bundle

the entry chunk gzipped, holding the public API and the loader with no metadata

83.3 KB

engine, 4 lazy chunks

fetched by ensureEngineReady() after first paint

105.1 KB

what an analyzer reports

bundlephobia and Import Cost inline the lazy chunks, reporting initial plus engine as one number

initial bundle (21.8 KB) engine, lazy (83.3 KB). One bar, gzipped bytes to scale. The green slice is everything that ships before the engine is needed.

Chunks

Every JavaScript file the build emitted, gzipped at level 9 and brotli-compressed at quality 11. The engine's four base64-of-gzip modules are referenced through dynamic import(), which makes the bundler split each into its own lazy chunk.

Chunk	Role	Raw	Gzip	Brotli
`index-DNH4LL3_.js`	initial	66.5 KB	21.8 KB	19.0 KB
`walk.bin-BIqcpGql.js`	engine, lazy	33.2 KB	25.0 KB	25.0 KB
`metadata.bin-CY9nY_7D.js`	engine, lazy	31.1 KB	23.5 KB	23.5 KB
`scope.bin-Bc-7Kyxu.js`	engine, lazy	25.5 KB	19.3 KB	19.2 KB
`verdict.bin-DryRyNCP.js`	engine, lazy	20.6 KB	15.5 KB	15.5 KB
Total on disk		176.9 KB	105.1 KB	102.2 KB

How analyzers count this

bundlephobia and the Import Cost editor extension estimate size by inlining every import() back into the entry, since neither models code-splitting. For a library that ships its data through lazy chunks, that collapses the initial bundle and the on-demand engine into one figure (105.1 KB).

A production bundler keeps the split. The engine layers download in parallel, off the critical path, when ensureEngineReady() runs. The entry chunk is what reaches a user on first paint, at 21.8 KB gzipped.

Reproduce

git clone https://github.com/martsinlabs/telixon
cd telixon && pnpm install
pnpm --filter @telixon/core build
pnpm --filter @telixon/example-core-bundle-size build

The build prints the same chunk sizes as the table above. The engine splits because it loads through dynamic import(), exactly as it does in a consumer's build.