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-csv

v1.0.5

Published

text/csv mimetype handler for plurnk-service. Homebrew RFC 4180 tokenizer; no parser dependency.

Readme

@plurnk/plurnk-mimetypes-text-csv

text/csv mimetype handler for the plurnk ecosystem.

install

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

what it does

  • validate(content) walks all records with the bundled RFC 4180 tokenizer; throws on unbalanced quotes or non-uniform column count.
  • extractRaw(content) emits one field symbol per header column (the first record), at line 1.

CSV's structural signal is the header row's column names — that's what surfaces in symbols. The actual data body is best previewed via the framework's raw-content fallback.

why no parser dependency

CSV is the textbook case where RFC 4180 fits in <100 LOC of careful hand-rolled tokenizer and the available libraries all carry transitive dependencies that don't earn their keep for header extraction. The tokenizer (parseAll) is exported for re-use.

license

MIT.