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

export-to-cli

v1.0.1

Published

Exports a function or entire module to CLI

Downloads

3

Readme

Export to CLI

Exports a function or an entire module to CLI

Usage

Just add one line of code to your module:

// export to CLI
require.main === module && require('export-to-cli').exportModule(myModule)

Now you can execute functions from myModule directly from CLI!

Example

Consider the following module from a file called person.js:

class Person {

    greeting(name, age) {
        var str = `${name} is ${age} years old`
        return str;
    }

    foo() {
        return 'bar'
    }
}

module.exports = Person

// export to CLI
require.main === module && require('export-to-cli').exportModule(Person)

Results

You can run functions from person.js in CLI:

$ node person.js greeting --age 12 --name "John Smith"

Output:

Jonh Smith is 12 years old

If you run without arguments:

$ node person.js

You shall get a default message:

Usage: person.js <function> [--argname1 value1 --argname2 value2...]

Required Arguments:
  function  Function name from the module to invoke.
            One of:
            -   greeting(name, age)
            -   foo()

Options:
  --version  Show version number                           [boolean]
  --help     Show help                                     [boolean]

Error: function is a required argument

Final note

Of course, you can continue using person.js as usual:

// another-file.js
const Person = require("./person.js")
var person = new Person()
var x = person.foo()