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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@paulll/ascii-separated-values

v1.0.3

Published

ASCII (\x1f, \x1e)-separated values file streaming parser/writer

Downloads

8

Readme

ascii-separated-values

ASCII (\x1f, \x1e)-separated values file streaming parser/writer.

Since almost any CSV parser/writer implementation is different (just look at jqnatividad/qsv: there are different supported syntaxes per command, no consistency at all!), I think there's time for brand new standard.

xkcd about standards

Just kidding, it isn't even something new, there's always been a Delimiter-Separated Values format, so ASV files should work with any DSV/CSV parser that allows custom field/row delimiters. There are special reserved symbols 'RECORD SEPARATOR' aka \x1e and 'FIELD SEPARATOR' aka \x1f in almost any text encoding, but for some unknown reason everyone just proposes their new standards with complex escaping rules, or even without escaping assuming that there will never be text with their uncommon separator like '|'. Also there are people who also faced such escaping problem, but again offer crutch solutions like using \00 as field separator.

Format

In terms of common CSV/DSV settings:

{
    "quote":      "never",
    "escape":     "never",
    "delimiter":  "\x1f",
    "terminator": "\x1e"
}