Blaster

Usage

You will need to have installed styled-components as well as styled-system in the application you want to use Blaster in.

npm install --save styled-components styled-system @blasterjs/core

Core Component Development

Starting the documentation

1. Change node versions: nvm use recommend using nvm for switching node versions
2. Setup project: npm install
3. Run npm run start

Starting the test-bed application

1. Change node versions: nvm use recommend using nvm for switching node versions
2. lerna bootstrap
3. npm run watch:build
4. In a separate terminal: cd packages/testbed then npm run start

Using the Blaster CLI

Blaster has a built-in CLI. It's the preferred method of managing components and constants. In order to use the CLI, after cloning the repo, you will need to run npm link.

CLI Commands

blaster {g,generate} {component, constant} <packageName> <newThingName> ex: blaster g component core tooltip, blaster generate constant core direction Generates a component or constant in the specified package.

blaster {d,destroy} {component, constant} <packageName> <thingToDestroyName> ex: blaster d component core tooltip, blaster destroy constant core direction Removes a component or constant in the specified package. Includes confirmation.

blaster {i,index} Regenerates all index files for each package as necessary.

blaster update-icons Regenerates the index file icons.

Styled System shortcuts in defaultProps

When declaring a component's defaultProps for margin or padding, avoid using the symmetric x and y shortcuts supplied by styled-system (mx, my, px, py). If you declare defaults for those shortcuts, a developer using your component will be unable to override them with styled-system's asymmetric shortcuts (ml, mr, mt, mb, pl, pr, pt, pb). Better to declare defaults using the asymmetric shortcuts, which a developer can override using either asymmetric or symmetric shortcuts.

Scripts

Command	Description
npm run start	This is the most commonly used command when developing locally. It runs npm run build, lerna bootstrap, and starts the docz server.
npm run bootstrap	An alias for lerna bootstrap. Symlinks the various packages together to enable a smooth monorepo development workflow.
npm run test	Run tests for all components
npm run build	Uses lerna to run all packages through babel.
npm run release	Create a new release interactively with Lerna
npm run clean	Remove all existing node_modules directories

All Lerna commands are also available.

Package Structure

All npm publishable packages are located in the packages directory.

package
├── index.js
├── components
│   ├── firstComponent
│   └── secondComponent
└── package.json

Component Structure

firstComponent
├── index.js
└── README.md

Publishing

Blaster uses Lerna in the default locked versioning mode. This means that whenever one package is updated to a new version, all packages are also bumped to have matching version numbers.

1. Ensure all changes have been committed. Publishing will not work if your local version is not up to date with master.
2. npm addUser --scope @blasterjs - this ensures you are logged into npm and have sufficient privileges to publish Blaster
3. npm run release - this runs lerna publish --exact, which is an interactive process. All dependencies are pinned to the versions currently installed. Select the appropriate version bump according to semantic versioning.