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

cereal

v0.2.3

Published

Serialisation library for JavaScript that understands object graphs

Downloads

14

Readme

Cereal

Serialisation Library for JavaScript that respects object aliases.

Can be used either client-side or in NodeJS.

What does it solve?

Aliases

var x = {};
var y = {a: x, b: x};

If you take the above and then do JSON.parse(JSON.stringify(y)) then you will lose the alias to x: what you'll get back will be {a: {}, b: {}}.

If you instead do Cereal.parse(Cereal.stringify(y)) then you'll get back the correct object shape, with both a and b pointing to the same object.

Loops

JSON can't cope with cyclical data structures. Cereal can.

var x = {};
x.x = x;

JSON will blow up if you try to stringify(x). Cereal will work correctly.

Anything else?

JSON invokes toJSON on an object before encoding it. Analogously to this, Cereal invokes invoking a cerealise function if it exists and encoding what is returned from that.

Note that Cereal first rewrites the object structure to something without loops or aliases (but from which the loops and aliases can be reconstructed) and then it just uses normal JSON encoding on the result. And vice-versa.

As a result, Cereal will ignore everything that JSON would ignore too. Thus as normal, you lose functions, prototypes etc etc.