Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Evaluate Twinkleplop for local UI JSON highlighting

Open
#1,632 1 comment 2 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@MathurAditya724 is already working on this.

Since Sep 24, 2026.

Assessment

This issue has not been assessed yet.

Description

jared

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.

  • JsonView currently uses Shiki's JS engine, JSON grammar and GitHub light/dark themes, highlighting after expansion. It does not load WASM.
  • Isolated minified/gzipped browser entries measured 15.6 kB for Twinkleplop JSON versus 58.3 kB for the current Shiki engine/grammar/two-theme configuration. Twinkleplop's figure excludes theme CSS; these are not production application bundle deltas.
  • Compatibility concerns include light/dark styling, malformed-input fallback, escaping, copy behavior and CSS/tests tied to .shiki. The timing comparison used one Shiki theme rather than the component's dual-theme configuration.
  • Evaluation is limited to the local UI; terminal rendering and SQL formatting are separate concerns.

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]

Dominant language
TypeScript
Stars
121
Forks
14
Avg merge
1d 1h
Merged PRs (30d)
92

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/cli

All issues in getsentry/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.