Safely serialize JavaScript expressions to a superset of JSON, which includes Dates, BigInts, and more.
Important
This is a fork of superjson. It is maintained in
eridu-tech/superjson and published to npm as
@eridu-tech/superjson.
In this fork the API is asynchronous: stringify, parse, serialize and deserialize return
Promises and must be awaited. See Async API.
- 🍱 Reliable serialization and deserialization
- 🔐 Type safety with autocompletion
- 🐾 Negligible runtime footprint
- 💫 Framework agnostic
At Blitz, we have struggled with the limitations of JSON. We often find ourselves working with Date, Map, Set or BigInt, but JSON.stringify doesn't support any of them without going through the hassle of converting manually!
Superjson solves these issues by providing a thin wrapper over JSON.stringify and JSON.parse.
Superjson logo by NUMI:
Install the library with your package manager of choice, e.g.:
yarn add @eridu-tech/superjson
Unlike upstream superjson, the public API in this fork is
asynchronous. stringify, parse, serialize and deserialize all return Promises:
| Method | Returns |
|---|---|
serialize(value) |
Promise<SuperJSONResult> |
deserialize(payload, options?) |
Promise<T> |
stringify(value) |
Promise<string> |
parse(string) |
Promise<T> |
import superjson from '@eridu-tech/superjson';
const json = await superjson.stringify({ date: new Date(0) });
const value = await superjson.parse<{ date: Date }>(json);The registration methods (registerClass, registerSymbol, registerCustom, allowErrorProps) remain
synchronous. Custom transformers may be asynchronous too: isApplicable, serialize and deserialize
can return either a value or a Promise.
The easiest way to use Superjson is with its stringify and parse functions. If you know how to use JSON.stringify, you already know Superjson!
Easily stringify any expression you’d like:
import superjson from '@eridu-tech/superjson';
const jsonString = await superjson.stringify({ date: new Date(0) });
// jsonString === '{"json":{"date":"1970-01-01T00:00:00.000Z"},"meta":{"values":{date:"Date"}}}'And parse your JSON like so:
const object = await superjson.parse<
{ date: Date }
>(jsonString);
// object === { date: new Date(0) }For cases where you want lower level access to the json and meta data in the output, you can use the serialize and deserialize functions.
One great use case for this is where you have an API that you want to be JSON compatible for all clients, but you still also want to transmit the meta data so clients can use superjson to fully deserialize it.
For example:
const object = {
normal: 'string',
timestamp: new Date(),
test: /superjson/,
};
const { json, meta } = await superjson.serialize(object);
/*
json = {
normal: 'string',
timestamp: "2020-06-20T04:56:50.293Z",
test: "/superjson/",
};
// note that `normal` is not included here; `meta` only has special cases
meta = {
values: {
timestamp: ['Date'],
test: ['regexp'],
}
};
*/All of the methods below are asynchronous and return Promises. See Async API.
Serializes any JavaScript value into a JSON-compatible object.
const object = {
normal: 'string',
timestamp: new Date(),
test: /superjson/,
};
const { json, meta } = await serialize(object);Returns json and meta, both JSON-compatible values.
Deserializes the output of Superjson back into your original value.
const { json, meta } = await serialize(object);
await deserialize({ json, meta }, { inPlace: true });Options
inPlace: boolean- Default:
false - Mutate the input json object in place instead of returning a deep copy
inPlace: truewill be much more performant on large objects if it's safe to mutate it
- Default:
Returns your original value.
Serializes and then stringifies your JavaScript value.
const object = {
normal: 'string',
timestamp: new Date(),
test: /superjson/,
};
const jsonString = await stringify(object);Returns string.
Parses and then deserializes the JSON string returned by stringify.
const jsonString = await stringify(object);
await parse(jsonString);Returns your original value.
Superjson supports many extra types which JSON does not. You can serialize all these:
| type | supported by standard JSON? | supported by Superjson? |
|---|---|---|
string |
✅ | ✅ |
number |
✅ | ✅ |
boolean |
✅ | ✅ |
null |
✅ | ✅ |
Array |
✅ | ✅ |
Object |
✅ | ✅ |
undefined |
❌ | ✅ |
bigint |
❌ | ✅ |
Date |
❌ | ✅ |
RegExp |
❌ | ✅ |
Set |
❌ | ✅ |
Map |
❌ | ✅ |
Error |
❌ | ✅ |
URL |
❌ | ✅ |
SuperJSON by default only supports built-in data types to keep bundle-size as low as possible. Here are some recipes you can use to extend to non-default data types.
Place them in some central utility file and make sure they're executed before any other SuperJSON calls.
In a Next.js project, _app.ts would be a good spot for that.
import { Decimal } from 'decimal.js';
SuperJSON.registerCustom<Decimal, string>(
{
isApplicable: (v): v is Decimal => Decimal.isDecimal(v),
serialize: v => v.toJSON(),
deserialize: v => new Decimal(v),
},
'decimal.js'
);Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
Other libraries that aim to solve a similar problem:
- Serialize JavaScript by Eric Ferraiuolo
- devalue by Rich Harris
- next-json by Daniele Ricci


