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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@blastoff/blastoff

v0.0.12

Published

blastoff CLI

Readme

blastoff CLI

A basic CLI for generating components / pages.

Installation

npm install -g @blastoff/blastoff

Commands

blastoff g {component|page|screen} Name (e.g. blastoff g component Button)

This will create a component / page / screen along with a storybook story, test, and index file. The test is assuming that you have react-testing-library installed

Options

  • --path - the path where the parent folder should be created defaults to /src/components/, src/pages/, or /src/screens/
  • --noStory - skip creating a story
  • --noTest - skip creating a test

Configuration

You can add blastoff.config.js to the root of your project for additional customization options such as functions for building the paths (advanced) as well as whether or not to use TypeScript file extensions.

  • useTypeScript - add ts / tsx extensions to the generated files
  • getComponentPath - A function that receives path, name, extension, parameters and returns the path where the component file should be created
  • getIndexPath - A function that receives path, name, extension, parameters and returns the path where the index file should be created
  • getStoryPath - A function that receives path, name, extension, parameters and returns the path where the story file should be created
  • getTestPath - A function that receives path, name, extension, parameters and returns the path where the test file should be created

All of the functions have a signature like the following:

  (path: string, name: string, extension: string, parameters: { [name: string]: any }) => string

Refer to the Gluegun docs for more on Parameters

module.exports = {
  useTypeScript: true,
  getStoryPath: (path, name, extension, parameters) => {
    return `one/${path}/${name}/${name}.stories.${extension}`
  },
  getTestPath: (path, name, extension, parameters) => {
    return `two/${path}/${name}/${name}.test.${extension}`
  },
  getComponentPath: (path, name, extension, parameters) => {
    return `three/${path}/${name}/${name}.${extension}`
  },
  getIndexPath: (path, name, extension, parameters) => {
    return `four/${path}/${name}/index.${extension}`
  }
}