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

component_scaffold

v0.6.0

Published

Will build a folder and file structure that fits your requirements.

Downloads

6

Readme

Component Scaffold

Installation

Using npm:

$ npm i -g component_scaffold

Running the CLI:

$ scaffold

Configuration

scaffold.config.json

  • dest: string = Target parent destination for the files being built.
  • friendlyName: string = Name that appears in the command line when running the scaffold command.
  • structure: array[structure] = The files and folders object array

structure <array[structure]>

  • type: string = file or folder
  • name: string = By default, the name of the file/folder is the string input into the command line while running the scaffold CLI. However, this will override that name to one of your choosing.
  • prefix: string = This string will become part of the file name at the beginning of the final string regardless if a name is specified or if it's left to the default name.
  • suffix: string = This string will become part of the file name at the end of the final string regardless if a name is specified or if it's left to the default name.
  • extension: string = This is the desired extension of the file.
  • content: string | { src: string }
    • string: If the content is a string it will fill the file with that string.
    • { src: string }: If the content is an object with a node of src, the CLI will read a template file at location and utilize it's content to fill the file being created.

Template file string replacement

When the content of a file is being filled by a template file, it's utilizes a simple string replacement for some of the options decided throughout the CLI process. These strings will be inclosed in % to indicate the beginning and the end of the desired replacement command. These options consist of the options input into the structure for the file. The only instance when the option will not be replaced as input is the name. The name has a case selection. These cases are:

  • snake
  • hyphen
  • camel
  • pascal
  • uppercase
  • lowercase

As an example on how to do the above:

export default class %name.pascal% extends React.Component<%name.pascal%Props, %name.pascal%States>

The above resolved into:

export default class YourNewComponent extends React.Component<YourNewComponentProps,YourNewComponentStates>