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

@contextrie/parsers

v0.1.2

Published

Node-based file parsers that return Contextrie core source instances.

Readme

@contextrie/parsers

Node-based file parsers for turning local .txt, code/text files, .md, and .csv files into @contextrie/core source instances.

Install

npm install @contextrie/parsers @contextrie/core

Usage

import {
  parseCsvFileSource,
  parseMarkdownFileSource,
  parseReferenceTextFileSource,
  parseTextFileSource,
} from "@contextrie/parsers";

const csvSource = await parseCsvFileSource("./examples/example.csv");
const codeSource = await parseTextFileSource("./examples/example.ts");
const markdownSource = await parseMarkdownFileSource("./examples/example.md");
const textSource = await parseTextFileSource("./examples/example.txt");
const referenceSource = await parseReferenceTextFileSource("./examples/example.ts");

console.log(csvSource.kind, csvSource.path, csvSource.getContent());
console.log(codeSource.kind, codeSource.path, codeSource.getContent());
console.log(markdownSource.kind, markdownSource.path, markdownSource.getContent());
console.log(textSource.kind, textSource.path, textSource.getContent());
console.log(referenceSource.kind, referenceSource.path);

API

  • parseTextFileSource(path): Promise<DocumentSource>
  • parseReferenceTextFileSource(path, options?): Promise<ReferenceDocumentSource>
  • supportsTextFileSource(path): boolean
  • parseMarkdownFileSource(path): Promise<DocumentSource | ListSource>
  • parseCsvFileSource(path): Promise<ListSource>

Parsers return:

  • parseTextFileSource: DocumentSource
  • parseReferenceTextFileSource: ReferenceDocumentSource
  • parseMarkdownFileSource: DocumentSource | ListSource
  • parseCsvFileSource: ListSource

All file-based sources set source.path to the input file path.

parseReferenceTextFileSource returns a lazy file-backed source and also sets source.path.

Parsing behavior

  • parseTextFileSource supports .txt plus common code/text extensions such as .ts, .js, .json, .yaml, .xml, .html, .css, .sh, and more
  • text/code files stay as DocumentSource
  • .md: prose-like content becomes DocumentSource; heading-heavy or list-heavy content becomes ListSource
  • .csv: rows are returned as ListSource items

Notes

  • File reading uses node:fs/promises and node:path
  • Source IDs are generated per parsed source
  • An executable example lives in parsers/example/index.ts