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

frint-cli

v5.7.2

Published

CLI for Frint

Downloads

27

Readme

frint-cli

npm

CLI for Frint


Guide

Installation

With npm:

$ npm install -g frint-cli

Usage

From your Terminal:

$ frint

Will list all the commands available to you.

Built-in commands

init

Scaffolds a new FrintJS application in the current directory:

$ mkdir my-directory && cd my-directory
$ frint init

To scaffold a certain example, as available in the repository here:

$ frint init --example kitchensink

new

Scaffolds a new FrintJS application in the current directory:

$ mkdir my-directory && cd my-directory
$ frint new

Scaffolds a new FrintJS application in the specified directory:

$ frint new my-directory

To scaffold a certain example, as available in the repository here:

$ frint new my-directory --example kitchensink

It is also possible to scaffold an example from an arbitrary repository:

$ frint new my-directory --example frintjs/frint-vue/tree/master/examples/basic

version

Shows the current version of frint-cli:

$ frint version

help

Shows help text of commands:

$ frint help init
$ frint help help

Using plugins

You can install frint-cli plugins just like a regular npm package in your project:

$ npm install --save frint-cli-hello

.frintrc

To register this new CLI plugin, update your .frintrc file in your project's root directory:

{
  "plugins": [
    "frint-cli-hello",
    "./some-relative/path"
  ]
}

Run the plugin

Now the frint-cli-hello plugin can be run as:

$ frint hello
world

Developing your own plugin

Building a plugin for frint-cli, is just like developing a regular FrintJS app.

// frint-cli-hello/index.js
const createApp = require('frint').createApp;

module.exports = createApp({
  name: 'hello', // this is the subcommand name in `$ frint hello`

  providers: [
    {
      name: 'summary',
      useValue: 'Short help text',
    },
    {
      name: 'description',
      useValue: 'Long help text',
    },
    {
      name: 'execute',
      useFactory: function () {
        return function () { // this returned function will be excuted
          console.log('world!');
        }
      },
    }
  ],
});

It is required that you have a provider called execute, which returns a function. This function will then be called when the subcommand is run.

To register multiple commands from the same plugin, you can export an array of App classes.

The summary and description is used when the user is trying to get help text by running:

$ frint help hello

Providers available in plugins

  • console (Console): The same console available in NodeJS globally
  • pwd (String): Current working directory
  • config (Object): As available in .frintrc file
  • params (Object): An yargs compatible object after parsing CLI options
  • fs (Object): Node's fs module