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

@ferrow/structured-output-parser

v1.0.0

Published

Extract and repair JSON from LLM text output, with a fallback option

Readme

Structured Output Parser

CI

Extract JSON from LLM text output, with a fallback if it can't be parsed.

const parser = new StructuredParser();
const result = parser.parse(llmOutput);

Why

LLMs sometimes wrap JSON in prose, markdown fences, or return slightly malformed JSON. Manually handling that on every call is annoying.

What it does

  • Tries JSON.parse() on the raw text first.
  • If that fails, looks for the first {...} or [...] block in the text and tries parsing that.
  • If both fail and you passed a fallback option, returns the fallback instead of throwing.
  • If both fail and there's no fallback, throws an Error with the original text.

What it does NOT do

  • It does not validate against a schema. The schema argument to .parse() is accepted but currently unused — pass it if you want (e.g. for your own future integration), but nothing in this library checks the parsed data against it.
  • No Zod integration, despite earlier versions of this README claiming one. If you want schema validation, run the parsed result through your own validator (Zod, Ajv, etc.) after calling .parse().

Example

const parser = new StructuredParser();
const text = 'Sure, here you go: {"name": "John", "age": 30}';
const data = parser.parse(text); // { name: "John", age: 30 }

// with a fallback
const safe = parser.parse('not json at all', undefined, { fallback: {} }); // {}

License: MIT


Sponsored by Ferrow


Part of the ferrow-toolkit collection · Sponsored by Ferrow