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

@helium/proto

v2.2.0

Published

Helium protobuf definitions compiled to JS with TypeScript types

Downloads

3,455

Readme

lint workflow rust workflow node.js workflow erlang workflow cpp workflow

Using this repository requires protobuf's protoc to be installed. The package to be installed differs per host platform.

Contributing

  • Protobuf message definitions live in either:
    • src/service/*.proto if only used in gRPC service definitions, or
    • src/*.proto if used by service-free code or shared across gRPC services
  • Avoid float in Protobufs because representations differ across hardware architectures
    • There are many floating point representations from IEEE, plus others
    • i.e., some range of interior digits are random per float spec
  • Frequency should use uint32 and should be in Hz
  • rssi or signal is always negative, thus use sint32 and is in deci-dbm (aka ddbm) which is dbm * 10
  • snr is signal-to-noise ratio and should be uint32
  • Fetch and share time in nanos, then truncate to appropriate granularity as needed
    • e.g., get from OS in nanos
  • Reject any PR unless units are documented inline within Protobuf definition
  • Document units of fields
  • When exceptions to the above occur, please explain why within comments