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

to-safe-json

v1.0.3

Published

Converts any JavaScript value into a JSON string, safely

Downloads

362

Readme

to-safe-json

Converts any JavaScript value into a JSON string, safely — never throws, even on circular references or BigInt.

Installation

npm install to-safe-json

Usage

const toSafeJson = require('to-safe-json');

toSafeJson([1, 2, 3]);              // '[1,2,3]'
toSafeJson({ a: 1, b: 2 });         // '{"a":1,"b":2}'
toSafeJson('[1,2,3]');              // '[1,2,3]'        (already valid JSON, passed through)
toSafeJson('hello');                // '"hello"'        (plain string, encoded as JSON literal)
toSafeJson(42);                     // '42'
toSafeJson(null);                   // 'null'
toSafeJson(undefined);              // 'null'           (fallback)
toSafeJson(NaN);                    // 'null'           (fallback, JSON has no NaN)

const circular = {};
circular.self = circular;
toSafeJson(circular);               // '{}'             (circular field dropped, not thrown)

toSafeJson(undefined, '{}');        // '{}'             (custom fallback)

Works well with to-safe-array

Both packages are designed to be inverses of each other:

const arr = [1, 2, 3];
const json = toSafeJson(arr);       // '[1,2,3]'
// toSafeArray(json) would give back [1, 2, 3]

Why not just JSON.stringify(value)?

  • JSON.stringify throws on circular references — this library drops the circular field instead of crashing.
  • JSON.stringify throws a TypeError on BigInt — this library converts it to a number (if safe) or a string.
  • JSON.stringify(undefined) returns undefined (not a string) — this library always returns a string, falling back to 'null'.
  • A string that's already valid JSON is passed through as-is, instead of being double-encoded into an escaped string.

API

toSafeJson(value: any, fallback?: string = 'null'): string

Takes any value and always returns a valid JSON string — never throws.

  • fallback — string returned when value can't be meaningfully converted (undefined, NaN, Infinity, a top-level function/symbol, or a fully circular value). Must itself be a string; otherwise it's silently reset to 'null'.

License

MIT © Toby Maxham