1.2.0 • Published 2 years ago

@bazooka_se/make v1.2.0

Weekly downloads
-
License
ISC
Repository
github
Last release
2 years ago

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:

KeyDefaultTypeDescription
templates_dirtemplatesStringDirectory 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

ExampleNote
toUpperCamelCaseUpperCamelCaseSame as default
toLowerCamelCaselowerCamelCase
toDashedCasedashed-case
toKebabCasekebab-caseSame as dashedCase
toSnakeCasesnake_case
toScreamingSnakeCaseSNAKE_CASE

Filenames

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

Filename examples

TemplateResult
index.js.templateindex.js
[%name%].module.scss.templateComponentName.module.scss

Template settings

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

SettingDefaultDescription
destinationnullThis is generated from selected template by default.
new_folderfalseSet to false to place template content in the root of destination folder.
prompt_subfoldertrueSet to true if destination folder has subfolders where generated component should be placed.
naming_conventionA 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.

1.2.0

2 years ago

1.1.3

2 years ago

1.1.2

2 years ago

1.1.1

3 years ago

1.1.0

3 years ago

1.0.1

3 years ago

1.0.0

3 years ago