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

want-js-helper

v1.1.4

Published

Tool for quick opening services

Downloads

8

Readme

want-js-helper Build Status

Tool for quick opening services

Install and write your config for quick opening services.

For example:

  1. Install in project npm i want-js --save or npm i want-js --global.
  2. Create in your project or home directory file .want-js.config.js;
  3. Describe commands that you want to open in config, for example, you want to open Github's page of project;

.want-js.config.js

module.exports = {
    commandParams: {
        gt: {
            executor: `${__dirname}/commands/github.js`,
            summary: 'Open github.',
            aliases: ['github']
        },
        tr: {
            executor: `${__dirname}/commands/travis.js`,
            someData: {
                a: 1,
                b: 2
            },
            summary: 'Open travis.',
            aliases: ['travis']
        },
        ...
    }
}

In this example you must describe Object with property commandParams. commandParams is Object which consists of different commands.

A name of property is one of the names some commands. For every command describes executor, we must write path in configs to command's js-file. Also we can add aliases of command and description in readme.

For every command describing Object will represent as data in command js-file.

const getParsedRemoteOriginUrl = require('./libs/get-parsed-remote-origin-url');

module.exports = async function (data) {
    const parsedUrl = await getParsedRemoteOriginUrl();
    if (parsedUrl) {
        const siteUrl = data.siteUrl || parsedUrl[2];
        return `https://${siteUrl}/${parsedUrl[3]}/${parsedUrl[4]}`;
    }
};

Command function can be async or not.

module.exports = function (data) {
    // some action
    return resultString; // return resultArray;
};

Function must return String, Array<String> or Promise which return String or Array<String>.

After all you may do in project or in all projects(if you install globally):

want gt

or

want github