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

@stepcode/textmate

v2.0.0

Published

TextMate grammars for StepCode, generated from keyword profiles (Shiki, VS Code)

Readme

@stepcode/textmate

TextMate grammars for StepCode, generated from @stepcode/profiles. Keywords are profile data, so the grammar is too: es, en and pseint ship ready-made, and any resolved profile can get its own.

import { createHighlighter } from 'shiki'
import { grammars } from '@stepcode/textmate'

const highlighter = await createHighlighter({ langs: [...grammars], themes: ['github-light'] })
highlighter.codeToHtml(source, { lang: 'stepcode', theme: 'github-light' })

| Export | Fence / lang | Scope | |---|---|---| | stepcode | stepcode | source.stepcode (the es profile) | | stepcodeEn | stepcode-en | source.stepcode.en | | stepcodePseint | stepcode-pseint | source.stepcode.pseint |

The same three are available as JSON: @stepcode/textmate/grammars/stepcode.json and so on.

Astro (astro.config.mjs):

import { grammars } from '@stepcode/textmate'

export default defineConfig({
  markdown: { shikiConfig: { langs: [...grammars] } },
})

A custom profile:

import { builtinProfiles, resolveProfile } from '@stepcode/profiles'
import { generateGrammar } from '@stepcode/textmate'

const grammar = generateGrammar(
  resolveProfile({ id: 'clase', extends: 'es', keywords: { if: ['Cuando'] } }, builtinProfiles),
  { name: 'stepcode-clase', scopeName: 'source.stepcode.clase' },
)

Scopes

Control keywords keyword.control, definition keywords storage.type, Por Referencia / Por Valor storage.modifier, input and output keyword.other.io, word operators keyword.operator.word, booleans constant.language.boolean, types support.type.primitive, builtins support.function.builtin, numbers constant.numeric.{integer,real}, strings string.quoted.{double,single}, comments comment.line, symbol operators keyword.operator.{assignment,comparison,arithmetic}, punctuation punctuation.*, subprogram and program names entity.name.function, call names entity.name.function.call, names in a Definir list variable.other.definition, other identifiers variable.other. Every scope ends in .stepcode.

Limits

The grammar is line-based: a multi-word keyword split across lines is not matched. Accent folding covers the Latin-1 marks (á, è, ô, ü, ç…). Calls and definitions are heuristics (an identifier before (, the names after Definir); there are no folding markers. A type or builtin spelling must contain a letter to be highlighted; symbolic spellings are supported only for operators and for the word-operator keywords (&, |, ~, %).

See docs/superpowers/specs/2026-09-06-textmate-design.md for the design.