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

fractalpop

v0.2.0

Published

Lightweight, Svelte-first syntax highlighting with first-class indented Sass. Returns HTML without a DOM.

Downloads

0

Readme

fractalpop

fractalpop is the engine. It highlights a string of source code and returns an HTML string — no DOM, no runtime dependencies. Use it directly on any platform, or through one of the adapter packages.

Install

npm install fractalpop

Quick start

Call highlight() with your code and a language. The result is a string of nested <span> elements that you drop into a <pre><code> block.

import { highlight } from 'fractalpop'

const html = highlight('const ready = true', { lang: 'ts' })
// <span class="fp__line"><span class="fp__token--keyword" style="color:var(--fp-keyword)">const</span> …

The output is HTML-encoded, so it is safe to inject with innerHTML, {@html}, or dangerouslySetInnerHTML.

highlight(code, options)

highlight takes the source string and an options object. It returns an HTML string.

| Option | Type | Default | Purpose | | --- | --- | --- | --- | | lang | string | 'typescript' | Language id, extension, or alias (see Languages). | | cx | Partial<Record<TokenType, string>> | — | Extra class name to add per token type. | | mark | (token: MarkToken) => void | — | Mutate a single token before it renders. | | markLine | (line: MarkLine) => void | — | Mutate a whole line before it renders. |

cx, mark, and markLine are the only customization hooks, and they control performance. When you pass none of them, render takes a fast path: it concatenates strings with no per-token object allocation. Passing any hook switches to the slower path that builds mutable token and line objects so the hooks can run. If you do not need customization, pass no hooks.

Emphasis with cx

cx appends a class to every token of a given type. This is the Tailwind- friendly way to emphasize tokens without writing selectors.

highlight(code, {
  lang: 'sass',
  cx: { keyword: 'font-bold', comment: 'italic opacity-70' },
})

Line highlighting with markLine

Each line exposes its zero-based index. Add a class when the line is one you want to highlight.

const active = new Set([2, 3]) // 1-based line numbers

highlight(code, {
  lang: 'ts',
  markLine(line) {
    if (active.has(line.index + 1)) line.className += ' fp__line--highlighted'
  },
})

Theming

fractalpop does not ship colors. Every token renders with class="fp__token--<type>" and an inline style="color:var(--fp-<type>)", so a theme is a block of CSS variables you set on any ancestor.

:root {
  --fp-identifier: #354150;
  --fp-keyword: #f47067;
  --fp-string: #00a99a;
  --fp-class: #8d85ff;
  --fp-property: #4e8fdf;
  --fp-entity: #665ac7;
  --fp-jsxliterals: #bf7db6;
  --fp-sign: #8996a3;
  --fp-comment: #a19595;
}

.fp__line--highlighted {
  background: #fff8c5;
}

For dark mode, redefine the same variables under a selector or media query — for example :root[data-theme='dark'] or @media (prefers-color-scheme: dark).

Token types

Token types are a small, fixed list. Keeping it stable keeps themes portable.

| Type | CSS variable | Typical meaning | | --- | --- | --- | | identifier | --fp-identifier | Plain identifiers and default text. | | keyword | --fp-keyword | Language keywords. | | string | --fp-string | Strings, regex literals, template text. | | class | --fp-class | Capitalized names, numbers, null, types. | | property | --fp-property | Object/CSS properties, Sass $variables. | | entity | --fp-entity | Function and mixin names. | | jsxliterals | --fp-jsxliterals | JSX text between tags. | | sign | --fp-sign | Punctuation and operators. | | comment | --fp-comment | Comments. |

Two more types, break (newlines) and space (horizontal whitespace), are preserved for faithful output but carry no color.

Languages

fractalpop ships metadata and configs for 32 languages, but the default entry only registers TypeScript and plaintext — the rest stay tree- shakeable. Register what you need yourself, or import fractalpop/full to register all 32 up front. Resolve a name, file extension, or alias to a canonical id with lang().

import { lang, findLanguage, allLanguages } from 'fractalpop/lang'

lang('tsx')     // 'typescript'
lang('.scss')   // 'scss'  (metadata is known; register the config to highlight)
lang('yml')     // 'yaml'
lang('nope')    // undefined

The four languages built with the most care are the ones fractalpop exists for:

  • sass — indented Sass (no braces, no semicolons).
  • scss — the brace dialect, sharing Sass's value coloring.
  • svelte — the composite: <script lang="ts"> + markup + <style lang="sass">.
  • typescript / javascript — a full JS/JSX/TS runtime (regex literals, template interpolation, JSX, and the TS-generic-vs-JSX distinction).

The rest is the general pack: css, html, markdown, diff, plaintext, c, cpp, csharp, go, java, rust, json, shell, sql, yaml, toml, python, ruby, php, kotlin, swift, lua, graphql, hcl, dockerfile, powershell, zig.

Subpath exports

The package exposes several entries so you only bundle what you need.

| Import | Exposes | | --- | --- | | fractalpop | highlight, registry utilities, and the option/token types. Only TypeScript and plaintext are registered by default. | | fractalpop/full | Everything from fractalpop, with all 32 languages registered. | | fractalpop/core | parse, tokenize, render (→ string), generate (→ AST). | | fractalpop/lang | lang, findLanguage, allLanguages. | | fractalpop/lang/<id> | A single language config (tree-shakeable). | | fractalpop/gpu | Async WebGPU highlighting via optional peer gpu-lexer. |

generate returns a hast-like AST, which is what a unified/rehype pipeline consumes. render returns the HTML string that highlight wraps.

import { parse, generate } from 'fractalpop/core'
import { lang, getLanguageConfig } from 'fractalpop/full'

const parsed = parse(code, getLanguageConfig(lang('sass')!))
const tree = generate(parsed) // element/text nodes, one per line and token

Registry utilities

The default fractalpop entry only registers TypeScript and plaintext. Use these utilities to control which languages are available at runtime.

The registry is a single module-level singleton shared by every entry point (fractalpop/full re-exports and mutates the same core as fractalpop), so a registration made through one import path is visible to all others in the same app.

import {
  registerLanguage,
  setDefaults,
  importDefaults,
  canonicalizeLang,
  getRegisteredLanguages,
} from 'fractalpop'

registerLanguage({ id: 'python', extension: 'py', aliases: ['python3'] }, pythonConfig)
setDefaults({ python: pythonConfig, rust: rustConfig })
await importDefaults(['python', 'rust'])
canonicalizeLang('tsx') // 'typescript'

| Function | Purpose | | --- | --- | | registerLanguage(language, config?) | Register one language, optionally with its parse config. | | setDefaults(languagesOrConfigs) | Replace the default set. Accepts Language[] or Record<string, ParseOptions>. | | importDefaults(ids) | Asynchronously import and register languages by id. | | canonicalizeLang(name) | Resolve a name/alias/extension to the canonical id. | | getRegisteredLanguages() | List currently registered languages. |

Related Packages

Benchmarks

fractalpop, Sugar High, PrismJS, highlight.js, and Shiki highlighting the same generated TypeScript files:

Measured 2026-09-13 with Node v24.19.0, darwin arm64, Apple M3 Pro.

| TypeScript | fractalpop 0.1.0 | Sugar High 2.4.0 | PrismJS 1.30.0 | highlight.js 11.12.0 | Shiki 4.4.3 | | --- | ---: | ---: | ---: | ---: | ---: | | Minified (KiB) | 12.35 | 27.29 | 14.57 | 29.49 | 364.20 | | Gzip (KiB) | 5.28 | 10.09 | 5.57 | 11.28 | 72.79 | | 11 KiB | 1.96 | 1.97 | 1.47 | 2.55 | 18.55 | | 100 KiB | 19.75 | 20.50 | 14.68 | 24.11 | 163.34 | | 500 KiB | 97.70 | 101.81 | 100.31 | 127.61 | 858.15 |

Median milliseconds per file; lower is better. 5 timed samples after warmup. Sizes are TypeScript-only browser bundles, minified with Bun; gzip uses level 9. Theme CSS is excluded. Loading and initialization are excluded. Each library highlights the same generated TypeScript into HTML using an explicit language. Grammars and HTML output differ; this is not a measure of highlighting quality or browser rendering speed. Results vary by machine and workload.