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

protolint

v0.50.5

Published

A pluggable linter and fixer to enforce Protocol Buffer style and conventions.

Downloads

10,100

Readme

protolint

Protolint is a go based linter for .proto files for google protobuf und gRPC. It follows the best practices at the protobuf.dev (and ff.). Please note, that this should be a dev-dependency.

The npm package provides a wrapper around the executables protolint and protoc-gen-protolint. During installation process, it will download the binaries matching the version and your operating system and CPU architecture from github.

If your behind a proxy, you can add the PROTOLINT_PROXY environment variable including the HTTP basic authentication information like username and password. NOTE that this will take precedence of the system HTTP_PROXY/HTTPS_PROXY environment variables. If these variables should be used, do not use PROTOLINT_PROXY. If a proxy server is set that should not be used, set PROTOLINT_NO_PROXY to non-zero value.

If your running an airgapped environment, you can add the following environment variables:

PROTOLINT_MIRROR_HOST: The basic url you are using to serve the binaries. Defaults to https://github.com PROTOLINT_MIRROR_REMOTE_PATH: The relative path on the mirror host. Defaults to yoheimuta/protolint/releases/download/

Within the remote path, make sure, that a folder v<version> exists containing the files downloaded from the github releases.

If you are required to authenticate against your mirror, use the following environment variables:

PROTOLINT_MIRROR_USERNAME: The user name. Defaults to an empty string. PROTOLINT_MIRROR_PASSWORD: The password or identifaction token. Defaults to an empty string.

For node based projects, you can add the protobuf configuration to your package.json using a node called protolint.

For more information about protolint, its parameters and command-line arguments refer to the original ReadMe in the github repository.