npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

pretext-editor

v0.4.1

Published

High-performance Canvas-virtualized text editor for large documents

Readme

pretext-editor

High-performance Canvas-virtualized code editor for React, based on pretext. Renders only visible lines via Canvas 2D, so it stays smooth even on very large files.

How it works

| Layer | Technology | |---|---| | Text layout engine | @chenglou/pretext Pure JavaScript/TypeScript library for multiline text measurement | | Rendering | Canvas 2D API — only visible lines are drawn each frame | | Syntax highlighting | Shiki with JavaScript regex engine (no WASM) | | Tokenization cache | Module-level Map — results cached across mounts, useDeferredValue keeps typing fast | | Keyboard / IME input | Hidden <textarea> captures all keyboard events and IME composition |

Installation

npm install pretext-editor

Usage

import { useRef, useState } from 'react'
import { PretextEditor } from 'pretext-editor'
import type { PretextEditorHandle } from 'pretext-editor'

export function Editor() {
  const [code, setCode] = useState('// hello world\n')
  const editorRef = useRef<PretextEditorHandle>(null)

  return (
    <div style={{ height: 600 }}>
      <PretextEditor
        ref={editorRef}
        value={code}
        onChange={setCode}
        language="typescript"
      />
    </div>
  )
}

The component fills its parent — give the parent an explicit height.

Props

| Prop | Type | Default | Description | |---|---|---|---| | value | string | — | Document content (controlled) | | onChange | (value: string) => void | — | Called on every edit | | language | string | undefined | Shiki language id ("typescript", "go", "python" …). Omit to disable highlighting. | | fontSize | number | 14 | Font size in px | | fontFamily | string | 'Menlo, Monaco, "Courier New", monospace' | CSS font-family string | | tabSize | number | 4 | Visual width of \t in spaces. Raw \t is preserved in content. | | className | string | — | Class on the scroll container | | style | CSSProperties | — | Inline style on the scroll container | | ref | Ref<PretextEditorHandle> | — | Imperative handle for scroll control |

Imperative handle

PretextEditor forwards a ref exposing scroll control for host-level coordination (e.g. syncing scroll position when switching between editor and preview modes):

const editorRef = useRef<PretextEditorHandle>(null)

// Get the source line at the top of the viewport
const topLine = editorRef.current?.getTopLine()

// Scroll to a specific source line
editorRef.current?.scrollToLine(42)

| Method | Returns | Description | |---|---|---| | getTopLine() | number | Index of the source line currently at the top of the visible area | | scrollToLine(line) | void | Scroll the viewport so line appears at the top |

Supported languages

Any language bundled with Shiki is supported. Common ones:

typescript · tsx · javascript · jsx · python · rust · go · c · cpp · csharp · java · kotlin · swift · ruby · php · css · scss · html · vue · svelte · json · yaml · toml · markdown · bash · sql · graphql

Pass the extension → language id mapping helper if needed:

import { extToLang } from 'pretext-editor'

const lang = extToLang('ts') // → "typescript"

Keyboard shortcuts

Navigation

| Key | Action | Status | |---|---|---| | Arrow keys | Move cursor | ✅ | | Shift + Arrow | Extend selection | ✅ | | Home / End | Jump to line start / end | ✅ | | Ctrl/⌘ + Home / End | Jump to file start / end | ✅ | | Ctrl/⌘ + ← / → | Jump word left / right | ✅ | | Page Up / Down | Move cursor one page up / down | ✅ |

Editing

| Key | Action | Status | |---|---|---| | Backspace / Delete | Delete character backward / forward | ✅ | | Ctrl/⌘ + Backspace | Delete word backward | ✅ | | Ctrl/⌘ + Delete | Delete word forward | ✅ | | Enter | Insert newline | ✅ | | Ctrl/⌘ + Enter | Insert blank line below | ✅ | | Ctrl/⌘ + Shift + Enter | Insert blank line above | ✅ | | Tab | Indent (multi-line: indent all selected lines) | ✅ | | Shift + Tab | Dedent (multi-line: dedent all selected lines) | ✅ | | Ctrl/⌘ + Shift + K | Delete current line | ✅ | | Alt + ↑ / ↓ | Move line(s) up / down | ✅ | | Alt + Shift + ↑ / ↓ | Copy line(s) up / down | ✅ | | Ctrl/⌘ + / | Toggle line comment | ✅ |

Selection

| Key | Action | Status | |---|---|---| | Ctrl/⌘ + A | Select all | ✅ | | Ctrl/⌘ + L | Select current line | ✅ | | Ctrl/⌘ + D | Select next occurrence of current word/selection | ✅ | | Ctrl/⌘ + Shift + L | Select all occurrences of current word/selection | ✅ |

Clipboard

| Key | Action | Status | |---|---|---| | Ctrl/⌘ + C | Copy | ✅ | | Ctrl/⌘ + X | Cut (cuts current line if no selection) | ✅ | | Ctrl/⌘ + V | Paste | ✅ |

History

| Key | Action | Status | |---|---|---| | Ctrl/⌘ + Z | Undo | ✅ | | Ctrl/⌘ + Shift + Z / Ctrl + Y | Redo | ✅ |

Mouse shortcuts

| Action | Behavior | Status | |---|---|---| | Click | Place cursor | ✅ | | Click + Drag | Select text | ✅ | | Shift + Click | Extend selection to click position | ✅ | | Double-click | Select word under cursor | ✅ | | Triple-click | Select entire line | ✅ | | Alt + Click | Add cursor (multi-cursor) | ✅ | | Alt + Shift + Click | Start column (box) selection | ✅ | | Alt + Shift + Drag | Column (box) selection | ✅ | | Ctrl + Alt + ↑ / ↓ | Add cursor above / below (keyboard multi-cursor) | ✅ |

Performance architecture

Current: line-based virtual rendering

The editor keeps all source lines in memory as a flat string[]. Rendering is already virtual — renderCanvas only draws lines whose Y range intersects the current viewport:

scrollTop ─────────────────┐
                           │  ← only these lines are measured + drawn
scrollTop + viewHeight ────┘

Canvas height is fixed to the viewport; a tall <div> inside the scroll container provides the native scrollbar. This keeps rendering O(visible lines) regardless of total file size.

Planned: 50-line block cache for large files (> 60 KB)

For very large files, even storing charWidth[] per character for every line becomes expensive. The planned optimization splits the document into blocks of ~50 source lines:

  • Each block is laid out independently and its metrics cached.
  • When the user edits a line, only the block containing that line is re-measured; all other blocks reuse their cached metrics.
  • Blocks are loaded progressively using requestIdleCallback with a doubling threshold schedule: 200 → 400 → 800 → 1600 → 3200 → 6400 → 6400 … source lines per batch.
  • A generation counter increments whenever block boundaries change (split when a block exceeds 100 lines, delete when it reaches 0). Idle callbacks capture the generation at dispatch time and discard their result if it no longer matches, preventing stale writes to the cache.

Block size rules:

| Condition | Action | |---|---| | Block grows > 100 lines | Split at line 50 into two blocks | | Block shrinks to 0 lines | Delete the block | | 1 – 100 lines | No structural change, mark dirty | | Edit spans two blocks | Each block shrinks independently; no merge needed |