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

@aws/amazon-q-developer-cli-proto

v0.2.0

Published

We use [protocol buffers](https://developers.google.com/protocol-buffers/) as a message format for inter process communication.

Downloads

160

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

nosovskynosovskyaws-sdk-teamaws-sdk-teamamzn-ossamzn-ossaws-sdk-botaws-sdk-botawsxrayawsxrayaws-iot-sdkaws-iot-sdkaws-amplify-opsaws-amplify-opszheallanzheallanmohit0193mohit0193rishabh6788rishabh6788weicongsweicongssayaligaikawadsayaligaikawadpeterzhuamazonpeterzhuamazonmattsb42-awsmattsb42-awsforrest-not-gumpforrest-not-gumpcaybloodcaybloodevertonfragaevertonfragaosa-publishosa-publishamazon-q-cli-botamazon-q-cli-bot

Keywords

Readme

Proto

We use protocol buffers as a message format for inter process communication.

This folder defines three main protocols:

  1. local.proto - Protocol for communication from local processes like figterm and the fig CLI to the desktop app
  2. fig.proto - Protocol for communication between client Fig.js apps like autocomplete and the desktop app
  3. figterm.proto - Protocol for sending commands from the CLI to figterm
  4. remote.proto - Protocol for sending between figterm and the desktop app, intended to be secure for remote machines

Setup

For any client, you must install the protobuf compiler:

brew install protobuf

Client Installations

| Client | Command | | ---------- | -------------- | | typescript | pnpm install | | rust | N/A* |

* The rust build process handles the installation of the proto toolchain.

Installation/Usage

To compile protos, run:

./build-ts.sh

Deprecating an Amazon Q API

  1. Edit fig.proto and add the [deprecated=true] annotation to the relevant fields
  2. Add an inline comment specifying the version when this was changed applies using the following format: //deprecated: 1.2.3

Contributing

Adding to protos

Just edit the appropriate proto file.