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

kvin

v1.2.14

Published

Rich serialization library for JavaScript

Downloads

1,050

Readme

KVIN - A rich serialization library for JavaScript.

TLDR;

const KVIN = require('kvin');
let s = KVIN.stringify(complexType);
let x = KVIN.parse(s);

Overview

KVIN - pronounced "Kevin" - serializes (and deserializes) JavaScript types for transmission over a network or storage to disk in a way that co-exists peacefully with JSON, but it supports many more data types, including:

  • undefined, null, NaN, Infinity, -Infinity, -0
  • Typed Arrays (Float64Array, Int64Array, etc)
  • Object graphs with cycles
  • Arrays with enumerable, non-numeric properties
  • Sparse Arrays
  • Date
  • URL
  • Error
  • BigInt
  • Regular Expressions
  • Instances of user-defined classes
  • Boxed primitives (excluding Symbol)
  • Functions (including enumerable properties)
  • Promises which always resolve to any of the above

This library is safe to use on user-supplied data and has no dependencies.

Supported Platforms

  • Browser (no framework needed)
  • Node.js
  • BravoJS
  • Probably every >= ES5 environment

Examples

Simple

const KVIN = require('kvin');
const obj = {};

obj.foo = "hello, world";

var obj_string = KVIN.serialize(obj);
var obj2 = KVIN.deserialize(obj_string);

console.log(obj2.foo);

Object With Cycle

const KVIN = require('kvin');
const obj = {};

obj.foo = "hello, world";
obj.bar = obj; /* make a circular reference */

var obj_string = KVIN.serialize(obj);
var obj2 = KVIN.deserialize(obj_string);

console.log(obj2.bar.bar.bar.bar.foo);

Float64Array (Typed Array)

const KVIN = require('kvin');
const obj = new Float64Array([1.0, 2.0, Math.PI, NaN, Infinity, -Infinity]);

var obj_string = KVIN.serialize(obj);
var obj2 = KVIN.deserialize(obj_string);

console.log(obj2);

Details

The basic implementation strategy is to marshal to an intermediate format, called a 'prepared object', that can be used to recreate the original object, but can also be serialized with JSON. We track a list objects we have seen and their initial appearance in the object graph. We rely on the /de-facto/ enumeration order of properties in vanilla objects that has been present in all popular browsers since the dawn of time; namely, that enumeration order is object insertion order. This could cause bugs with objects with cycles in less-common interpreters, such as Rhino and the NJS/NGS ES3 platform by Brian Basset.

There may be different ways to encode the same data when marshaling; these techniques can sometimes be chosen by heuristic or performance tuning properties, but every possible encoding can be decoded by the unmarshal code.

Typed Arrays are encoded by encoding the direct underlying bits into 8-bit characters which then wind up as UTF-8 strings. There is vestigial support for a more efficient UTF-16 encoding, however we have found practical problems related to networking stacks rewriting unpaired surrogates as "invalid" codepoints. This may be revisited in the future, as it should shrink eventual payload size.

Compression

We recommend transmitting all data over the network compressed at the network layer (e.g. content-transfer-encoding: gzip). The serializer, in certain modes, will do a sort of "run length limited" encoding on Typed Array data; specifically, the islz "Islands of Zero" encoding is optimized for mostly-empty blocks of memory (our initial use for this library was for images in an astrophysics application).

Interoperation with JSON

KVIN and JSON go together like peas and carrots. If you are creating a payload object which will be stringified by JSON in the future, do NOT use kvin.serialize(); instead, use kvin.marshal(). This will get you all the benefits of Kvin without the cost of double-stringification. Similarly, at the receiving end, use kvin.unmarshal() to reconstruct your data.

Substitution for JSON

const JSON = require('./kvin');

Loading

Browser

global KVIN object:

<script src="/path/to/kvin.js"></script>
<script>
  KVIN.stringify({my: "object"});
</script>

Node.js

const kvin = require('kvin');
kvin.serialize(foo: "bar"});

No Module System

const code = "the contents of kvin.js";
const kvin = eval(code);
kvin.serialize({foo: "bar"});

Module Exports

API Functions

| Function | Argument | Behaviour |----------------|--------------|------------------------------------------------------------- | serialize | any | returns a string representing the argument | serializeAsync | any | returns a Promise which resolves to a string representing the argument. Any Promises encountered while traversing the object graph (argument) will be awaited, and their resolved values will be serialized. Deserialization will generate Promises which resolve to these values. | deserialize | string | returns a facsimile of the argument passed to serialize | stringify | any | alias for serialize | parse | any | alias for deserialize | marshal | any | like serialize, but returns a JSON-compatible object | marshalAsync | any | like serializeAsync, but returns a JSON-compatible object | unmarshal | object | like deserialize, but operates on marshaled objects instead of strings | kvin | object | constructor to create a custom KVIN instance, with its own tuning parameters and Standard Classes.

KVIN Instance Properties

| Property | Default | Description |-------------------------|---------|--------------------------------------------------------- | allowConstructorList | | Array which is a list of non-standard constructors that KVIN will try to deserialize | userCtors | {} | Dictionary; keys are constructor names, values are constructor functions for user-defined classes | makeFunctions | false | When true allows Kvin to deserialize Functions

Tuning Values

| Property | Default | Description |-------------------------|---------|--------------------------------------------------------- | tune | | Set to "speed" for fast operation, or "size" for small operation. Default value, undefined, balances both. | typedArrayPackThreshold | 8 | When to start trying to use islands-of-zeros encoding; bigger numbers mean faster encoding/decoding but longer strings. | scanArrayThreshold | 8 | When to start trying to use sparse-array representation for Arrays; bigger numbers mean faster encoding/decoding but longer strings.

Advanced Topics

Custom Contexts

The KVIN object has a variety of tuning and extensibility parameters. When writing non-trivial programs or library code that need specific KVIN features, it is advisable to instantiate a KVIN context to avoid accidentally altering a default behaviour of KVIN upon which another developer may be depending.

const KVIN = new (require('kvin').KVIN)();
KVIN.tune = "speed";

const s = KVIN.stringify(myObject);
console.log(KVIN.parse(s));

Custom Classes

Serializing Custom Classes

KVIN can be used to serialize instances of custom classes, however in many cases, KVIN will need some help understanding hidden internal state.

The algorithm KVIN uses to prepare myObject when it is an instance of a custom class is as follows:

  1. Memoize the constructor's name (myObject.constructor.name) as the ctr property of the prepared object
  2. If the object has a toKVIN method, invoke it and merge the return value with the prepared object. Stop (do not perform steps 3-5).
  3. If the object has a toJSON method, invoke it and memoize the return value as the arg property of the prepared object.
  4. If the object has a toString method, invoke it and memoize the return value as the arg property of the marshaled object.
  5. If the object has an ownProperty method, enumerate the own properties of the object and store them in marshaled format in the object which is the ps property of the marshaled object.
toKVIN(o, kvin)

toKVIN must be infallible and return an object. It is invoked with two arguments:

  • o - this is the object to serialize (also this when using a heavy-weight toKVIN function)
  • kvin - this is the instance of KVIN doing the serialization
toJSON()

toJSON must be infallible and return a string or an object which can be serialized with JSON.

Deserializing Custom Classes

The algorithm KVIN uses to deserialize instances of custom classes is as follows:

  1. Lookup the constructor function on this (instance of KVIN) .userCtors based on the name propery of the marshaled object.
  2. Run the constructor, with the arguments in args property or the argument which is the arg property of the marshaled object.
  3. Unmarshal and copy any properties found in the ps property of the marshaled object.

Strategies for Serializing Custom Classes

  1. Naive: don't do anything; KVIN marshal based on the constructor's name and enumerable properties. When it comes time to unmarshal, KVIN will apply these to the newly-constructed object during unmarshaling, and use the function in KVIN.userCtors which matches constructor's name as the constructor.
  2. toJSON: If an object has a toJSON function, KVIN will marshal the result of this function, and pass the unmarshaled value to the same-named constructor during unmarshaling. This is how KVIN supports the Date() class.
  3. toKVIN: If an object has a toKVIN function, KVIN will merge the results of this function with the marshaled object (containing the constructor name); this merge object will be used as-is in the unmarshal phase, and KVIN will not try to marshal the properties. The most useful properties of this return value are args, which is an Array of arguments to pass to the constructor during unmarshaling, and ps, which is an object of properties to apply to the instance after construction.

Examples

This example passes no arguments into the constructor during deserialization, and restores properties after construction by assignment:

const KVIN = require('kvin');

function Person(firstName, lastName) {
  this.firstName = firstName;
  this.lastName  = lastName;
  this.random    = Math.random();
}
KVIN.userCtors.Person = Person;

const bob = new Person('bob', 'weir');
const bob_s = KVIN.stringify(bob);
const bob_o = KVIN.parse(bob_s);
console.log(bob.random === bob_.random,  bob === bob_o); /* outputs "true false" */

This example passes one argument to the constructor during deserialization, and restores properties after construction by assignment:

const KVIN = require('kvin');

class Person {
  #firstName;
  #lastName;

  constructor(arg) {
    this.#firstName = arg.firstName;
    this.#lastName = arg.lastName;
  }
  get name() {
    return this.#firstName + ' ' + this.#lastName;
  }
  toJSON() {
    return { firstName: this.#firstName, lastName: this.#lastName };
  }
}
KVIN.userCtors.Person = Person;

const bob = new Person({ firstName: 'bob', lastName: 'weir' });
const bob_s = KVIN.stringify(bob);
const bob_o = KVIN.parse(bob_s);
console.log(bob.name, bob_o.name, bob === bob_o); /* outputs "bob weir bob weir false" */

This example serializes an own-property method of a custom class which has access to the variable rando by closure. The toKVIN function creates an arguments array which is applied to the MyClass constructor when it is instantiated during deserialization.

KVIN.makeFunctions = true;

function MyClass(rando)
{
  if (typeof rando === 'undefined')
    rando = Math.random();
  this.bar = function() {
    return rando;
  }
}
MyClass.prototype.hello = 'world';
MyClass.prototype.toKVIN = function toKVIN() {
  return {args: [this.bar()]}; /* ctor knows what to do with arg */
};

const foo = new MyClass();
const s_foo = KVIN.stringify(foo);
const p_foo = KVIN.parse(s_foo);

assert(foo.bar() === p_foo.bar());
assert(p_foo instanceof foo.constructor);