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-api-bindings

v0.2.0

Published

The Typescript definitions for the Amazon Q for command line API.

Downloads

137

Readme

TS API Bindings

The Typescript definitions for the Amazon Q for command line API.

Note: The protobuf definitions are updated automatically whenever withfig/proto-api is changed.

Documenting the API

We use TSDocs to comment the exported namespaces of the API.

See docs-generators/fig-api folder in public-site-nextjs repo for reference.

Supported TSDoc tags and custom TSDoc tags

  • @param: The params of an exported function, the format MUST be @param <name of the param> <some description>. It can be provided multiple times for different params.
    /**
     * @param notification some description for the notification param
     */
    export function subscribe(notification) {}
  • @returns: An explanation of what is returned by an exported function.
  • @remarks: Further details about the implementation of the method, use cases...etc. This data will appear in the Discussion section.
  • @example: Provide examples about the usage of the API object. It is repeatable.
  • @prop: Provide a description for one property of the exported object, the format MUST be @prop <name of the property> - <some description>. It can be provided multiple times for different properties.
    /**
     * @prop subscribe - a description
     * @prop unsubscribe - a description
     */
    export const didChange = {
      subscribe: (notification) => {},
      unsubscribe: (notification) => {},
    };
  • @excluded: To exclude some symbol from the docs. It should not be used.
  • @deprecated: Mark an API as deprecated providing an optional message about the deprecation.
    /**
     * @deprecated This message is optional
     */
    export const didChange = {
      subscribe: (notification) => {},
    };

What will appear in the documentation?

Our API bindings export a list of named namespace objects each one exporting a group of Symbols. In our docs file we document each of the exported symbols grouped according to their namespace.

Publishing

This package will be published automatically when pushed to any branch of this repo.