Skip to content
/ bemy Public

CLI tool for auto generation and save renaming BEM nodes

Notifications You must be signed in to change notification settings

f0rmat1k/bemy

Repository files navigation

Bemy

Build Status Bemy is a CLI helper for auto-generation and renaming BEM structure, like this:

myblock
├── myblock.js
├── myblock.css
└── __elem
    ├── myblock__elem.js
    └── myblock__elem.css

Especialy usefull with Webstorm (using external tools). It allows to generate folder and file structure using deps.js (enb dependencies format) file with one command (or hotkey). All templates supports different placeholders that will be replaced with BEM node names. You can tune it and can add your own file types. Bemy can run three usable tasks: create, rename, and auto;

Install

npm i -g bemy

Usage

bemy -t [task] -f [path] [options]

When you call the task of creation on files it is like you call bemy on the folder contains this file. So this two variants are equal: -f ~/testBlock/__elem c j and -f ~/testBlock/__elem/testBlock__elem.bh.js c j.

Starting with version 2.1 -t and -p and -f is no more required.

Shared CLI options

-t [task name] — name of the called task. default: 'auto'; -f [path] — path to BEM node (folder or file); -g — adding into git for created or renamed files (it calls git add for each file); -c [config path] — set path of your own config json file. Read about path working at Configuring section. --debug — to output various information.

The task of creation

Takes arguments with file types and creates files using templates.

CLI for task of creation:

bemy -t create -f [path] -p "[file types]", where file path — is a path to BEM node (folder or file), file types — list of needed files separated by space. Example: Command: bemy -t create -f ~/testBlock/__elem -p "css js"

Result:

testBlock
└── __elem
    ├── testBlock__elem.js
    └── testBlock__elem.css

Result: called 'create' task and appeared some-block/some-block.css and some-block/some-block.js.

Options

-o — opens the file after creation. If file exists, bemy just open it. This command is configured in .bemy.json in section editor-open-command. Default value is wstorm {{file-path}}:{{line-number}}. See more details at below in the section Configuring; -p [file list] — file types list. Available following file types: -p "css js deps priv bh". Also you can use short notation p c j b d. You can add you own file types and shortcuts into .bemy.json. Also you can set file types with just enumeration before single options keys, e.g. bemy c j -o -g.

Webstorm requires -f [path]. An example of using bemy with external tools of webstorm for the task of creation: Don't forget to configure hotkey for task running (e.g. ctrl + c) at keymap section.

The task of renaming

Recursively renames current node and its children. -d turn on deep mode, and contents of files will also be renamed. Deep rename used rename param from config file so you should to configure it for you own file types. rename renames only described files and valid directories (e.g. mod folder in mod folder isn't valid).

CLI for task of renaming:

bemy -t rename -f [path] -p [new name] -d

Options

-d — turn on deep mode with renaming of files content; -p — new BEM node name;

Webstorm is required -f [path]. An example of using bemy with external tools of webstorm for the task of renaming:

The autotask

Calls default action depend on BEM node. Currently work following variants:

  1. If target is a deps-file, creates described elems\mods\elemMods folder structure. And depend on options of .bemy.json also creates elems\mods\elemMods files. By default it's css files. See Configuring section for more details.
  2. Otherwise call create task with default options (equal -t create -f [path] -p "css"). Default file types for autotask configurable at .bemy.json.

CLI for autotask

bemy -f [path]

or you can call just bemy: Run autotask:

cd some-block
bemy

Result:

some-block
└── some-block.css

Called autotask and created the only css file some-block.css. You should set -f when you want set different from the current directory or call bemy on deps.js file.

Webstorm is required -f [path]. An example of using bemy with external tools of webstorm for the autotask: Don't forget to configure hotkey for task running (e.g. ctrl + a) at keymap section.

Confguring

Bemy will try to find .bemy.json on the every previous level (like npm) until the root directory, so you can put .bemy.json into your home directory or project directory if you need different options depend on project. Otherwise bemy will take .bemy.json from own directory.

file-types

Description of the used file types. suffix used by 'create' when forming file and by 'rename' for files validation (rename renames only described files); shortcuts — list of short that you can use after -p key in Task of creation; rename – mask for deep renaming. {{bemNode}} will be replaced to new node name. You can also use an array of masks; filename — sets up your own resulting file name. Useful when you allways need index.css or index.jsx instead of BEM names. template — path to template of file type. Teamplate used when any files are created. There are following placeholders: {{blockName}}, {{BlockName}}, {{elemName}}, {{ElemName}}, {{modName}}, and the same with kebab-case, e.g. {{Block-Name}}, {{ModName}}, {{modVal}} and {{cursor}}. When files are created this entries will be replaced with relevant part of BEM node name. And {{cursor}} will be deleted and used for setting cursor line number (see more at Configuring section). Also, you can set a hook, which will be called, when file will be created. The hook-command get file path with the first argument by replacing {{filePath}}.

For example, default css template contain:

.{{blockName}}{{elemName}}{{modName}}{{modVal}}
{
   {{cursor}}
}

, so resulted file will contain:

.testBlock__elem {
/* curor will be here, when you use right configured -o key */
}

deps_task

Options for autotask when it called on deps file. files – list of file types to be created in addition to folders.

auto_dir

Options for autotask when it called on directory. It set needed file types, which will be created. Default is ['css'].

editor-open-command

Command to be called after creating the file. There are two placeholders:

  1. {{file-path}} to be replaced with relevant file path.
  2. {{line-number}} will be taken from {{cursor}} position of relevant template. Default command is wstorm {{file-path}}:{{line-number}}, so if you use webstorm you should to create CLI launcher at webstorm with same name (Tools / Create Command-line Lanucher). If you use old version of webstorm on Mac you can try to use /Applications/WebStorm.app/Contents/MacOS/webide for editor-open-command.

bem

Your BEM options. If you use own separators you have to set right allowed-name-symbols-regexp.

debug — to output various information. checkForUpdate — check for new version.

Windows

On Windows bemy is installed into c:\Users\[user-name]\AppData\Roaming\npm\node_modules\bemy\bemy.js, and webstorm cannot run bemy simply, using bemy command, so you have to set node into the field Program, and full absolute path to bemy into field Parameters before parametres. The path to bemy usually is c:\Users\[user-name]]\AppData\Roaming\npm\node_modules\bemy\bemy.js. So settings should be something like this: 2015-04-04 21-58-18 edit tool

Also on windows CLI intarface isn't working fully, e.g. you can't run just bemy without -f param. And -f have to be absolute path.

Solutions with the same functionality