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

gen-proto

v0.0.1

Published

Generates protobuf files from json

Readme

gen-proto

A tool for generating protobuf files from json descriptions

Installation

npm install -g gen-proto

Usage

gen-proto some/json/file.json

or

require('gen-proto')('some/json/file.json')

File Format

{
  filename: String,           // file name
  syntax: Number,             // by default 3 (should be protobuf version 2 or 3)
  package: String,            // package name
  options: {},                // string to string mapping of options
  imports: [                  // all the import statements
    {
      filename: String,
      public: Boolean         // public import?
    },
    ...
  ],
  messages: [                 // TODO: allow for nesting of message types later
    {
      name: String,           // name of message type
      description: String,    // comment to write above the message type definition
      schema: [               // message type definition
        {
          type: String,       // type of data
          name: String,       // name of field
          key: Number,        // number of field (otherwise default enumeration)
          repeated: Boolean,  // array?
        },
        ...
      ]
    },
    ...
  ],
  services: [                 // services to include
    {
      name: String,           // name of service
      methods: [              // methods to include in service
        {
          name: String,       // name of rpc method
          req: String,        // name of request message type
          res: String,        // name of response message type
        },
        ...
      ]
    },
    ...
  ]
}

Example

Input

{
  "filename": "test/test-output.proto",
  "syntax": 2,
  "package": "some.package",
  "options": {
    "some_option": "some_string/some_string"
  },
  "imports": [
    {
      "filename": "some/path/to/a/publicly/imported/file",
      "public": true
    },
    {
      "filename": "some/path/to/an/imported/file"
    }
  ],
  "messages": [
    {
      "name": "SomeMessageType",
      "description": "A simple description of the message type below",
      "schema": [
        {
          "type": "string",
          "name": "field1"
        },
        {
          "type": "int32",
          "name": "field2",
          "repated": true
        },
        {
          "type": "some_type",
          "name": "field3",
          "repated": true
        },
        {
          "type": "another_type",
          "name": "field4",
          "key": 777
        }
      ]
    }
  ],
  "services": [
    {
      "name": "SomeService",
      "methods": [
        {
          "name": "SomeMethod",
          "req": "SomeMessageType",
          "res": "AnotherMessageType"
        }
      ]
    },
    {
      "name": "AnotherService",
      "methods": [
        {
          "name": "AnotherMethod",
          "req": "CrazyMessageType",
          "res": "CrazierMessageType"
        },
        {
          "name": "LastMethod",
          "req": "CraziestMessageType",
          "res": "CraziesterMessageType"
        }
      ]

    }
  ]
}

Output

syntax = "proto2";
package some.package;

option some_option = "some_string/some_string";

import public "some/path/to/a/publicly/imported/file";
import "some/path/to/an/imported/file";

// A simple description of the message type below
message SomeMessageType {
  string field1 = 1;
  int32 field2 = 2;
  some_type field3 = 3;
  another_type field4 = 777;
}

service SomeService {
  rpc SomeMethod(SomeMessageType) returns (AnotherMessageType);
}

service AnotherService {
  rpc AnotherMethod(CrazyMessageType) returns (CrazierMessageType);
  rpc LastMethod(CraziestMessageType) returns (CraziesterMessageType);
}