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

@rbxts/command

v0.0.1

Published

Very simple command/argument management system.

Downloads

3

Readme

Command

A simple command registration and execution management system including some utilities to parse arguments and disect command strings. This library is meant to be used with player centric commands, every command must have a player sender, this may not be for you if that's not what you want.

Example

A simple example demonstrating argument parsing, command registration and command execution.

class TargetParser implements ArgumentValueParser<Player> {
	private players = game.GetService('Players');

	public parse(value: string) {
		// TODO you can implement more robust and advanced
		// player parsing, such as checking for a player's
		// name, their ID, whether the name includes the
		// value, etc...

		return this.players.GetPlayers().find((player) => {
			return player.Name.lower() === value.lower();
		});
	}
}

class NumberParser implements ArgumentValueParser<number> {
	public parse(value: string) {
		// TODO you can implement more robust and advanced
		// number parsing, such as a configuration to
		// enable clamping, rounding, etc...

		return tonumber(value);
	}
}

const commander = new Commander();

// Commands can be functions or classes, up to you and your coding style.
commander.registerCommand({ identifier: 'hurt' }, (sender, args) => {
	// Take a look at the doc comments of ArgumentParser and ArgumentDescriptor
	// to find more about how to declaratively parse arguments like this.
	const [target, damage] = args.describe().then(new TargetParser()).then(new NumberParser()).compile();

	const char = target.get(sender).Character;
	if (!char) return;

	const hum = char.FindFirstChildOfClass('Humanoid');
	if (!hum) return;

	hum.Health = hum.Health - damage.get(hum.Health);
});

commander.executeName(game.GetService('Players').LocalPlayer, 'hurt', ['xzyrakia', '5']);