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

@wwselleck/raft-cli

v0.0.1

Published

To use the raft-cli, first install it `npm install --save-dev @wwselleck/raft-cli`

Downloads

3

Readme

Raft CLI

To use the raft-cli, first install it npm install --save-dev @wwselleck/raft-cli

You'll first want to make a configuration file. A Raft configuration file exports an object that can then be passed to Raft.create. For example,

// raft.config.js
const googledrive = require('@wwselleck/raft-plugin-googledrive')

module.exports = {
  datasources: [
    gdrive: {
        source: googledrive({
          authConfig: {
            type: 'service',
            path: path.resolve(__dirname, 'creds', 'gdrive_creds.json')
          },
          baseDirName: 'MyData'
        })
    }
  ]
}

I call mine raft.config.js, but it doesn't have to be called that.

To use it, run raft specifying your configuration file with --config.

$(npm bin)/raft --config ./config/raft.config.js

You'll then be presented with a screen that looks like this.

From here you can select any of your configured data sources. I only have one so I'll select that one.

Now you'll be able to see a list of actions that you can perform on the selected data source. Again, I only have one, so I'll select that one.

You're then prompted to enter whatever parameters that action needs. Right now, you have to enter something that is valid JSON (i.e. will not throw an error when passed to JSON.parse). So for example if you want to enter a list of the string data, you'll enter ["data"] (note that JSON requires double quoted strings). This will hopefully change at some point, but for now that's a requirement.

Once you're done, the action will be executed and the results logged to you.