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

tsbuffer-cli

v1.3.3

Published

TSBuffer CLI Tools

Downloads

30

Readme

TSBuffer CLI Tools

EN / 中文

CLI utilities for TSBuffer

Install

npm i -g tsbuffer-cli

Usage

Generate proto

tsbuffer proto -i **/*.ts -o proto.json

Encode Test

tsbuffer encode -p proto.json -s a/b/c/TypeName "{value: 1}"
tsbuffer encode -p proto.json -s a/b/c/TypeName "{value: 1}" -o buf.bin

Decode Test

tsbuffer decode -p proto.json -s a/b/c/TypeName "01 0A 01"
tsbuffer decode -p proto.json -s a/b/c/TypeName -i buf.bin -o output.js

Validate Test

tsbuffer validate -p proto.json -s a/b/c/TypeName "{value: 1}"
tsbuffer validate -p proto.json -s a/b/c/TypeName -i xxx.js

Show buffer

tsbuffer show buf.bin

CLI Reference

tsbuffer proto <options>                Generate proto file
    -i, --input <file>                  Input TS file (support glob expression)
                                        It would generate all exported types
    -o, --output <file>                 Output file (or print to CLI)
    -c, --compatible <file>             Compatible mode, compatible to old proto (=output by default)
    -n, --new                           Generate fresh new proto (no compatible)
    -u, --ugly                          Output as ugly JSON (no indent and smaller)
    -v, --verbose                       Show debug info

tsbuffer encode <options> [exp]         Encode a JS expression or a file (content is JS expression)
    [exp]                               Expression to encode (e.g. "123" "new Uint8Array([1,2,3])")
    -p, --proto <file>                  Proto file to use
    -s, --schema <id>                   SchemaID (filePath/TypeName)
    -i, --input <file>                  Input file path, alternative to [exp]
    -o, --output <file>                 Output file path (or print to CLI)
    -v, --verbose                       Show debug info
                                        
tsbuffer decode <options> [binstr]      Decode buffer
    [binstr]                            Buffer to decode, hex string, like "0F A2 E3"
    -p, --proto <file>                  Proto file
    -s, --schema <id>                   SchemaID (filePath/TypeName)
    -i, --input <file>                  Input file path, alternative to [binstr]
    -o, --output <file>                 Output file path (or print to CLI)
    -v, --verbose                       Show debug info

tsbuffer validate <options> [exp]       Validate if a JS expression is valid to a schema
    [exp]                               Expression to validate (e.g. "123" "new Uint8Array([1,2,3])")
    -p, --proto <file>                  Proto file to use
    -s, --schema <id>                   SchemaID (filePath/TypeName)
    -i, --input <file>                  Input file path, alternative to [exp]

tsbuffer show <file>                    Show a binary file as hex string