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

@ayame/usage

v0.2.0

Published

Usage tag parser for Ayame framework

Downloads

5

Readme

@ayamejs/usage

Parses usage strings like <target:user> [reason:string...] into a JavaScript object like [{ name: "target", type: "user", required: true, rest: false, options: null, literal: false }, { name: "reason", type: "string", required: false, rest: true, options: null, literal: false }]

Used internally by the Ayame Framework but anyone can use it.

Join our Discord Server for support and more.

Install

$ npm install @ayamejs/usage

If you are using Ayame then ignore this, it's already a dependency of Ayame and is used internally, this guide is for interested users who would like to use them in their own custom bots.

TypeScript typings included.

Usage

const usage = require("@ayamejs/usage");

// Parse a usage string.
usage.parse("<target:user> [reason:string...]");
// =>
// [
//   { name: 'target', type: 'user', required: true, rest: false, options: null, literal: false },
//   { name: 'reason', type: 'string', required: false, rest: true, options: null, literal: false }
// ]

// Clean the types to make it more user friendly on discord.
// Use this e.g in your help command.
usage.format("<target:user> [reason:string...]");
// => <target> [reason...]

// Or if you have a seperator.
usage.format("<username:string> <repository:string>", "/");
// => <username> / <repository>

Explanations on each returned property:

  • name This is the tag name, a name is always available.
  • type This is the type followed after the name, always available.
  • required If true the tag was constructed with <> meaning it is required.
  • rest if true the tag was constructed with ... meaning to parse the rest of the input. Only on the last tag.
  • options Array of options if the tag used the | seperator. Available on type union it would signify the user meant to try parsing as different types (<target:member|user> try parsing as member if failed try user)
  • literal If true it means the union types are rather literal options (<action::add|remove|list> action can be either add, remove or list) This is true if the user used :: double colons to seperate the union.

Prefixes

Instead of repeating the same name for the type we have some aliases.

e.g instead of <user:user> you can use <@user>

Aliases:

  • @ user
  • @@ member
  • # channel

The output format does not change, you can still treat it as if the full <user:user> was passed.

More aliases will be added if needed.

Changelog

v0.2.0

  • Added support for # prefix tags for channels.
  • Add seperator option for usage.format to make it clear to the user about the seperator.

v0.1.0

  • Initial release.

License

@ayamejs/usage is released under the terms of MIT LICENSE