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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@parseysharp/parseyscript

v1.0.2

Published

TypeScript parsing library for turning less-structured data into typed values with path-aware errors.

Readme

parseyscript

A small TypeScript parsing library for going from less-structured inputs to more-structured types, with cursor-based navigation and path-aware error reporting.

You can think of it as an alternative to Zod: instead of declaring the entire shape of the source data, you describe only the values you want to extract. You navigate someone else's structure on your own terms, without having to model every intermediate field just because it exists in the input.

It provides:

  • Parse<A>: composable parsers for values of type A (strings, numbers, booleans, dates, etc.).
  • Cursor-based navigation via at / maybeAt using a Navigator over arbitrary input shapes.
  • Optional values via a simple Maybe type.
  • Result values via ParseResult, with success/failure, mapping, and sequencing helpers.

Installation

This is a plain TypeScript project. You can install dependencies with:

npm install

Usage

The library is re-exported from src/index.ts, so you can import everything as:

import * as P from "./src";

Example: parsing a nested object with some required and optional fields:

const parser = P.Parse.zip4(
  P.Parse.string().maybeAt("some", ["nested", "path"]),
  P.Parse.dateTimeOffsetFlex({ epochIsMilliseconds: true }).at("some", [
    "other",
    "path",
  ]),
  P.Parse.bool().at("the", ["flag"]),
  P.Parse.floatFlex().at("the", ["number"])
).map(([a, b, c, d]) => ({ a, b, c, d }));

const input = {
  the: {
    number: 23,
    flag: "false",
  },
  some: {
    other: { path: "1762912054467" },
    nested: { path: "hello" },
  },
};

const result = parser.parse(P.Navigator.unknown(), P.Maybe.fromNullable(input));
console.log(result);

Errors are accumulated as ParseError values with human-readable messages and a dot-separated path.

Running tests

Tests are written with Vitest and live in tests/.

npm test

This runs Vitest against the TypeScript sources.