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

command-maker

v0.3.1

Published

A simple plugin to create custom commands to Cerebro only editing a JSON file

Downloads

4

Readme

cerebro-custom-command

A simple plugin to create custom commands to Cerebro only editing a JSON file

Usage

  • Type settings on cerebro and set a path for a .json file for the commands

  • If the path isn't expecified, the plugin will look for the .json in this path: %appdata%/cerebro-custom-command/config.json
  • In this file add your commands, example of the syntax for a command to open a playlist
{    
    "commands": [
        {
            "name": "Lo-Fi Playlist",
            "icon": "C:/path-to-icon/youtube-icon.png",
            "exec": "start chrome https://www.youtube.com/watch?v=Rhomn5Um9dg&list=RDRhomn5Um9dg&start_radio=1&t=0"
        }
    ]

}

You can also add custom keywords to your command using an array format:

{
    "commands": [
        {
            "name": "Lo-Fi Playlist",
            "icon": "C:/path-to-icon/youtube-icon.png",
            "exec": "start chrome https://www.youtube.com/watch?v=Rhomn5Um9dg&list=RDRhomn5Um9dg&start_radio=1&t=0",
            "keywords": ["lofi", "playlist"]
        }
    ]    
}

The plugin will match the command name or the keywords(if is specified)

You can also use more than one exec script for a command using the options array:

{
    "name": "Command",
    "icon": "C:/path-to-icon/icon.png",
    "exec": "explorer /e, C:\\path-to-folder",
    "options": [
        {
            "name": "Open with code",
            "exec": "code C:\\path-to-folder"
        },
        {
            "name": "Open with atom",
            "exec": "atom C:\\path-to-folder"
        }
    ]
}

Here is some examples of commands

The exec script in this examples are for Windows, but can be used the equivalent command in any system

  • Open a folder (favorite folder, project)
{
    "name": "Documents",
    "icon": "C:/path-to-icon/folder-icon.png",
    "exec": "explorer /e, C:\\Users\\Name\\Documents"
}

  • Open the GMail
{
    "name": "GMail",
    "icon": "C:/path-to-icon/gmail-icon.png",
    "exec": "start chrome https://mail.google.com/"
}

  • Open a project folder with code
{
    "name": "Project A",
    "icon": "C:/path-to-icon/icon.png",
    "exec": "code C:\\path-to-project\\ProjectA"
}
  • Open the .json config file
{
    "name": "config.json",
    "icon": "C:/path-to-icon/json.png",
    "exec": "code C:\\path-to-json\\config.json"
}

Possible troubleshooting

If you are on Windows and want a command that open the explorer in some folder using the explorer /e, C:\path, you will have to use double bars to specify the path, for example: C:\\Users\\YourName\\Documents. Here is how it will be the full command in the config.json:

{
    "name": "Command",
    "icon": "C:/path-to-icon/icon.png",
    "exec": "explorer /e, C:\\Users\\Name\\Documents"
}

Related