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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@veksa/protobuf-codec

v0.0.2

Published

Protocol Buffers codec implementation for @veksa/transport messaging layer

Readme

@veksa/protobuf-codec

npm version npm downloads license

Protocol Buffers codec implementation for @veksa/transport messaging layer

Installation

@veksa/protobuf-codec requires TypeScript 5.8 or later.

Using npm or yarn

# npm
npm install @veksa/protobuf-codec

# yarn
yarn add @veksa/protobuf-codec

Features

  • Protocol Buffers encoding/decoding for @veksa/transport
  • Efficient binary serialization and deserialization
  • Support for all Protocol Buffers data types
  • Type-safe message handling with TypeScript
  • Customizable field definitions through simple arrays
  • Lightweight implementation with minimal dependencies
  • Full integration with @veksa/transport messaging system

Basic Usage

import { createProtobufCodec } from '@veksa/protobuf-codec';

// Define message field structures as arrays
const userMessageFields = [
  [1, 'id', 'uint32', 1],
  [2, 'name', 'string', 1],
  [3, 'email', 'string', 0],
  [4, 'active', 'bool', 0]
];

const settingsMessageFields = [
  [1, 'theme', 'string', 1],
  [2, 'notifications', 'bool', 1]
];

// Create a codec with a map of message types to field definitions
const codec = createProtobufCodec({
  1: userMessageFields,     // User message type
  2: settingsMessageFields  // Settings message type
});

// Encode a message
const encodedMessage = codec.encode({
  payloadType: 1,  // User message
  payload: {
    id: 123,
    name: 'John Doe',
    email: '[email protected]',
    active: true
  },
  clientMsgId: 'msg-123'
});

// Decode a message
const decodedMessage = codec.decode(encodedMessage);

API Reference

createProtobufCodec(apiMap)

Creates a new Protocol Buffers codec that implements the ITransportCodec interface.

  • apiMap (Record<number, FieldItem[]>): A map of payload types to field definitions

Returns an ITransportCodec object with the following methods:

  • encode(message: IMessage): ArrayBuffer | string | undefined
  • decode(buffer: ArrayBuffer | string): IMessage | undefined

FieldItem Format

Field items are defined as arrays with the following structure:

// [tag, name, type, required, oneof?, anyof?]
type FieldItem = [number, string, FieldType, 0 | 1, string?, string?];

Where:

  • tag (number): The field number
  • name (string): The field name
  • type (FieldType): The field type (e.g., 'string', 'uint32')
  • required (0 | 1): Whether the field is required (1) or optional (0)
  • oneof (string?): Optional oneof group name
  • anyof (string?): Optional anyof group name

Supported Field Types

  • Simple types: 'string', 'int32', 'uint32', 'bool', 'bytes', etc.
  • Maps: ['map', keyType, valueType]
  • Repeated fields: ['repeated-simple', fieldType] or ['repeated-packed', fieldType]
  • Wrapped fields: ['wrapper', simpleType]
  • Nested messages: FieldItem[]

Contributing

This project welcomes contributions and suggestions.

License

MIT