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

@iftt/tryte-buffer

v1.3.0

Published

Efficiently enocode predefined datasets to trytes.

Downloads

14

Readme

tryte-buffer travis npm downloads JavaScript Style Guide

About

Tryte buffers are designed to be language-neutral, platform-neutral, extensible mechanism for serializing structured data to the tryte schema used by the IOTA tangle. You define your structure once in JSON and this module will take care of encoding all future object data to trytes and back again.

Find the encoding/decoding module here

Install

# npm
npm install --save tryte-buffer

# yarn
yarn add tryte-buffer

Example

// import package
// ES5
const TryteBuffer = require('@iftt/tryte-buffer').default;
// ES6
import TryteBuffer from '@iftt/tryte-buffer';

const tryteBuffer = new TryteBuffer(addressProtocol);

const testInput   = {
  name: 'Craig O\'Connor',
  aliases: ['CTO', 'Craiggles', 'Goober'],
  id: 76543456,
  phone: '+8005555555',
  phoneType: 'work'
};

let tryteEncoding = tryteBuffer.encode(testInput);
let decodedTrytes = tryteBuffer.decode(tryteEncoding);

// tryteEncoding === '99AAMBFDPCXCVCEAYBLAMBCDBDBDCDFD9C999FMBCCYB999RMBFDPCXCVCVC9DTCGD999LQBCDCDQCTCFD9EI9UWV999XPAVAXAXA9BWAZAZAYAVAYABB9A'
// decodedTrytes === { name: 'Craig O\'Connor', aliases: ['CTO', 'Craiggles', 'Goober'], id: 76543456, phone: '+8005555555', phoneType: 'work' }

Debug

if you need to debug use the string tryte-buffer

DEBUG=tryte-buffer node x

Encoding guidelines

You define the protocol using JSON, as this is web friendly and supported by almost every common language in use today. The keys define the name of future input data:

{
  name: ...,
  age: ...,
  height: ...
}

The encoding/decoding options are as follows:

{
  type: 'string' | 'int8' | 'uint8' | 'int16' | 'uint16' | 'int32' | 'uint32' | 'bool' | 'date',
  repeat: boolean, // is the data an array?
  enum: array<string | number>, // an array of all possible values
  precision: 2 // this is only for number types and defines how many decimal places you want to keep
}

Example protocol

Although this is not an exhaustive list of possible use cases, it is relatable data.

let addressProtocol = {
  "name": {
    "type": "string"
  },
  "aliases": {
    "type": "string",
    "repeat": true
  },
  "id": {
    "type": "uint32"
  },
  "phone": {
    "type": "string"
  },
  "phoneType": {
    "type": "string",
    "enum": ["mobile", "work", "home"]
  }
}

API

type Protocol

type Protocol = {
  [string]: { // key
    [string]: any // key is type, enum, repeat, precision, or any user defined variables
  }
}

new TryteBuffer(protocol: Protocol, [tryteLimit: number = 2187])

  • tryteLimit: number; defaults to 2187. If you specify 0 then there is no limit
  • overTryteLimit: boolean;
  • lastEncodingSize: number;
  • protocol: Protocol;
  • [string]: { ['encode' | 'decode']: function }; the keys with encoding and decoding prepared from the protocol

encode(input: ProtocolInput): string

  • input: an object containing the same keys and values as described by the protocol submitted on instantiation
  • output: encoded trytes

decode(trytes: string): { [string]: any }

  • trytes: a string of encoded trytes
  • output: a decoded object with the same keys and values as submitted by the protocol buffer

ISC License (ISC)

Copyright 2019 Copyright (c) 2004-2010 by Internet Systems Consortium, Inc. ("ISC") Copyright (c) 1995-2003 by Internet Software Consortium

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.