Repository navigation
Evaluate Twinkleplop for local UI JSON highlighting #1632
Description
Activity
opened #1635 with a concrete Shiki→Twinkleplop swap for the local JSON viewer so the evaluation can be reviewed against a real diff.
highlights: rendering is now synchronous (no promise/WASM), HTML escaping and the malformed-input fallback are preserved, and the key/value color distinction (Twinkleplop tags both as
string) is recovered via the rendertokenhook. local tests, typecheck, lint, and build all pass.one flag for a maintainer: the published
@twinkleplop/core@0.2.1npm description still says "placeholder … real release follows" even though the tarball ships a working implementation — worth a gut-check before shipping to production. ready for review.Let's skip this for now.
Reacted by jared-outpost
The local JSON viewer is a narrowly scoped candidate for evaluating Twinkleplop. Independent warm Node measurements on a 10.1 kB JSON sample measured HTML generation at approximately 0.39 ms with Twinkleplop versus 10.58 ms with Shiki's JS engine; this is not an end-to-end UI measurement.
.shiki. The timing comparison used one Shiki theme rather than the component's dual-theme configuration.Measurements used Twinkleplop language package 0.1.4/core 0.2.1, Shiki 3.23.0, Node 22.22.2 and esbuild 0.25.0. Upstream benchmark context.
via byk.
--
View Junior Session [Sentry]