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 🙏

© 2025 – Pkg Stats / Ryan Hefner

hacklight

v1.1.0

Published

A lightweight, pragmatic syntax highlighter that's good enough™

Readme

Hacklight

A lightweight, pragmatic syntax highlighter that's good enough™.

What It Is

Hacklight is a simple tokenizer/syntax highlighter that aims to correctly parse ~95% of real-world code in the 8 most popular languages. It's designed to be:

  • Small - Single file, minimal dependencies
  • Fast - Simple regex-based tokenization
  • Browser-friendly - Works anywhere JavaScript runs
  • Pragmatic - Handles the common cases well, doesn't sweat the edge cases

What It Isn't

This is not a perfect parser. It will get some things wrong, especially:

  • Complex nested template literals
  • Exotic regex patterns
  • Language-specific edge cases
  • Mixed-language contexts beyond HTML/CSS/JS

If you need 100% accuracy, use a proper AST parser. If you need something that works well for 95% of code you'll encounter and fits in a single file, this might be for you.

Supported Languages

  • JavaScript (including JSX, modern ES2024 features)
  • TypeScript
  • HTML (with embedded CSS/JS)
  • CSS (including CSS variables, at-rules)
  • Python
  • Java
  • C/C++
  • Go

Usage

const { tokenize } = createTokenizer('auto');  // auto-detects HTML or JS
const tokens = tokenize(sourceCode);

// Convert to HTML with syntax highlighting
const html = tokensToHtml(tokens);

Token Types

  • keyword - Language keywords (if, for, class, etc.)
  • identifier - Variables, function names, etc.
  • string - String literals
  • number - Numeric literals
  • comment - Comments
  • operator - Operators (+, -, =, etc.)
  • punctuation - Brackets, semicolons, etc.
  • regex - Regular expressions (JS)
  • html_tag - HTML tags
  • attr_name / attr_bool - HTML attributes
  • css_selector - CSS selectors
  • css_variable - CSS custom properties
  • css_at - CSS at-rules (@media, etc.)
  • error_string - Unterminated strings
  • whitespace / newline - Formatting

Philosophy

Perfect is the enemy of good. This tokenizer makes practical trade-offs:

  1. Speed over correctness - Uses regex instead of full parsing
  2. Simplicity over completeness - One file, minimal state machine
  3. Common cases over edge cases - Handles typical code patterns well
  4. Pragmatism over purity - Some heuristics and "good enough" decisions

Known Limitations

  • Regex literals vs division operators use heuristics that can be fooled
  • Template literal interpolations are tokenized as one string
  • HTML/CSS/JS context switching is simplified
  • No semantic understanding (can't distinguish types from variables)
  • Some exotic syntax constructs may tokenize incorrectly

License

MIT

Contributing

This is intentionally kept simple. Bug fixes welcome, but feature additions that add complexity will likely be declined. The goal is to stay small and "good enough".