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

@bazooka_se/make

v1.2.0

Published

A scaffolding tool for creating components in an existing project.

Downloads

178

Readme

Installation

npm i @bazooka_se/make

Add a script entry to your package.json file:

"scripts": {
    "make": "bazooka-make"
}

Run the script and follow instruction to generate a new component:

npm run make

Setup

To get started, create a directory in your project root called templates with directories for each template inside it. Template directory name can be changed in settings, see below.

Example directory structure:

/templates
    /component
    /container

Global settings

An optional settings file can be created in your project root to change some settings. Create a file called bazooka.make.json and add your settings as an object:

{
    "templates_dir": "templates"
}

Supported settings

The following values are supported at the moment:

| Key | Default | Type | Description | |---|---|---|---| |templates_dir|templates|String|Directory where templates are located|

Templates

A template can contain both files and directories. Empty directories are ignored.

See example templates here.

Template data

The templates will be passed data that can be accessed in both files and filenames. Currently the only data passed is the name you enter, together with case convertions, see below.

Use the following syntax to access the passed data:

# In a filename
[%name%]
[%name.toScreamingSnakeCase%]
# Inside a file
<% name %>
<% name.toDashedCase %>

Available case conversions

| | Example | Note | | - | - | - | | toUpperCamelCase | UpperCamelCase | Same as default | | toLowerCamelCase | lowerCamelCase | | | toDashedCase | dashed-case | | | toKebabCase | kebab-case | Same as dashedCase | | toSnakeCase | snake_case | | | toScreamingSnakeCase | SNAKE_CASE | |

Filenames

All files must have the file ending .template to be included.

Filename examples

| Template | Result | | --- | --- | | index.js.template | index.js | | [%name%].module.scss.template | ComponentName.module.scss |

Template settings

Each template can have a .settings file that supports the following settings:

| Setting | Default | Description | | --- | --- | --- | | destination | null | This is generated from selected template by default. | | new_folder | false | Set to false to place template content in the root of destination folder. | | prompt_subfolder | true | Set to true if destination folder has subfolders where generated component should be placed. | | naming_convention | | A string or an array of strings with regular expressions that given name should match. Disable naming convention by setting a falsy value. Default convention is UpperCamelCase. |

{
    "destination": "tests/",
    "prompt_subfolder": true,
    "new_folder": false,
    "naming_convention": ["^my[A-Z].+$", "[^_]"]
}

Example .settings file.