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

@plurnk/plurnk-mimetypes-text-typescript

v0.3.3

Published

text/typescript and text/javascript mimetype handler for plurnk-service. ANTLR-backed extraction; the TS grammar handles plain JS as a subset.

Readme

@plurnk/plurnk-mimetypes-text-typescript

text/typescript AND text/javascript mimetype handler for the plurnk ecosystem.

One ANTLR-backed parser serves both mimetypes — the TypeScript grammar is a superset that handles plain JavaScript as well. The framework constructs separate handler instances per registered mimetype; extraction policy is identical for both.

install

npm i @plurnk/plurnk-mimetypes-text-typescript

plurnk-service auto-discovers this handler and routes .ts/.tsx/.mts/.cts to text/typescript and .js/.mjs/.cjs/.jsx to text/javascript.

what it extracts

| Kind | Source | |---|---| | function | Top-level function and generator-function declarations (with params) | | class | Class declarations + class expressions (top-level) | | method | Constructors, methods, getter/setter accessors (inside classes) | | field | Class field declarations | | interface | TS interface declarations | | variable | Module-scope const/let/var that is exported |

Imports, local variables inside function bodies, and unexported module-scope variables are excluded per SPEC §3.

known grammar limitations

The vendored grammar (antlr/grammars-v4/javascript/typescript) doesn't disambiguate certain TypeScript-only constructs at the statement level:

  • type X = ...; parses as a variable statement.
  • enum X { ... } parses as an expression statement.

The visitor wiring is in place; fixing requires reordering alternatives in TypeScriptParser.g4. Tracked as a known limitation; PRs welcome upstream.

development

npm install
npm run build     # antlr-ng → src/generated, then tsc → dist
npm test

Grammar source: grammar/TypeScriptLexer.g4 + grammar/TypeScriptParser.g4. Vendored base classes in src/generated/{TypeScriptLexerBase,TypeScriptParserBase}.ts (committed; the rest of src/generated/ is build output).

license

MIT.