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

jettison

v0.6.3

Published

Encode JavaScript binary data into strings to send over the network.

Downloads

7

Readme

jettison Build Status

jettison helps you encode binary JavaScript data into strings, so you can send it over things like WebSockets.

Getting Started

To use jettison, you need to define a shared schema on the client and server. Within the schema, you define a set of packets, each with a name and a set of properties for the packet. These schemas need to match between the client and the server because the packets are identified by integers. If they don't match, packets sent by one side won't correspond to the correct definition on the other side.

Here's an example schema with two packets:

var schema = jettison.createSchema();

// This packet is sent when a new object is created.
schema.define('spawn', [
  {key: 'id', type: 'uint32'},
  {key: 'x', type: 'float64'},
  {key: 'y', type: 'float64'},
  {key: 'color', type: 'uint32'},
  {key: 'health', type: 'int32'},
  {key: 'points', type: 'array', valueType: 'float64'}
]);

// This packet is sent when an object's position changes.
schema.define('position', {
  {key: 'id', type: 'uint32'},
  {key: 'x', type: 'float64'},
  {key: 'y', type: 'float64'}
});

Types that are currently supported are:

| Type | Description | | ------- | ----------- | | boolean | 1 byte true or false. | | int8 | 1 byte signed integer. Range is -128 to 127 (inclusive). | | int16 | 2 byte signed integer. Range is -32768 to 32767. | | int32 | 4 byte signed integer. Range is -2147483648 to 2147483647. | | uint8 | 1 byte unsigned integer. Range is 0 to 255. | | uint16 | 2 byte unsigned integer. Range is 0 to 65535. | | uint32 | 4 byte unsigned integer. Range is 0 to 4294967295. | | float32 | 4 byte floating point number. Note that normal JavaScript numbers will be rounded to fit this size, so decoded values will only approximately equal the originals. | | float64 | 8 byte floating point number. Normal JavaScript numbers are stored in this format, so these will be transmitted without rounding. | | array | A variable length array of another type. When you use this type, you must also specify a valueType field, which will specify the type of value in the array. | | string | A variable length string. JavaScript's UTF-16 strings are encoded to UTF-8 for transmission. |

Note that values out of range will be truncated (so a value of 256 encoded as a uint8 will be truncated to 255, and a value of -1 will be truncated to 0).

Once you have a schema, you can use it to encode and decode objects like so:

var string = schema.stringify('spawn', {
  id: 1,
  x: 123.456,
  y: 789.012,
  color: 0x00ffff,
  health: 100,
  points: [
    0.1, 0.2,
    0.3, 0.4,
    0.5, 0.6
  ]
});

var parsed = schema.parse(string);
console.log(parsed.key);   // "spawn"
console.log(parsed.data);  // {"id": 1, "x": 123.456, ...}