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

@bxpb/protoc-plugin

v1.0.1

Published

Complier plugin for `protoc` to generate TypeScript client/service definitions for protocol buffers.

Downloads

1

Readme

@bxpb/protoc-plugin

The compiler plugin for protoc which generates client and service TypeScript code for BXPB.

Usage

Start by installing protoc. You can use grpc_tools_node_protoc from grpc-tools if you want something installable from NPM.

Then run (replace protoc with grpc_tools_node_protoc if necessary):

protoc --plugin=protoc-gen-bxpb=node_modules/.bin/bxpb-protoc-plugin --bxpb_out=generated/ greeter.proto

This will compile greeter.proto in the current directory and generate TypeScript definitions for BXPB under the generated/ directory. This will output:

generated/greeter_bxpb_service.d.ts
generated/greeter_bxpb_service.js
generated/greeter_bxpb_client.d.ts
generated/greeter_bxpb_client.js

The first two files contain definitions to run the proto service, while the last two files contain definitions to call the service.

Local Development

Build and Run

To build this package, run from the repository root:

npm run -- lerna run build --stream --scope @bxpb/protoc-plugin --include-dependencies

Output files are in the dist/ directory, while the binary can be invoked with:

npm run -- lerna run start --stream --scope @bxpb/protoc-plugin

Test

Build and run unit tests with this command (run from the repository root):

npm run -- lerna run build --stream --scope @bxpb/protoc-plugin --include-dependencies &&
    npm run -- lerna run test --stream --scope @bxpb/protoc-plugin

You can debug tests in VSCode with the "@bxpb/protoc-plugin - Test Debug" launch configuration.

Sourcemaps seem to work fine, though breakpoints are finicky; sometimes they trigger and sometimes not. The debugger; statement is the most reliable way to break in the file.

You can also test with any other Node inspector by using:

npm run -- lerna run build --stream --scope @bxpb/protoc-plugin --include-dependencies &&
    npm run -- lerna run test:debug --stream --scope @bxpb/protoc-plugin

And then connecting to Node debug port exposed in your preferred debugger. For Chrome, this is done by visiting chrome://inspect and clicking "Open dedicated DevTools for Node".

Place a debugger; statement at the top of the file you are interested in, and then hit "continue" until you reach that file. You should then be able to place and use breakpoints as desired.