AHA-Theme

Version Information

• Version 0.0.27: Old theme structure that most projects still follow
• Version 0.1.0+: New theme structure that we'll be using moving forward. Currently implemented in the bmt-client project

SETUP

1. Run npm i

Git hooks

Husky runs local Git hooks from .husky/. After npm i (or npm install), the prepare script registers hooks for the repo. Commit .husky/ and scripts/validate-commit-msg.mjs so everyone shares the same checks.

Commit message format (commit-msg)

The hook validates the first non-comment line of the commit message. It must match one of:

1. Conventional commit with one or more (bmt-client#<digits>) scopes, optional !, optional : <description>. Types: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test. Example: feat(bmt-client#123): update theme tokens
2. Default merge commit subjects (starts with Merge), such as Merge branch 'main'.

To change this rule, edit scripts/validate-commit-msg.mjs.

Pre-push checks (pre-push)

On git push, hooks run in order and the first failing command blocks the push:

1. npm run lint
2. npm run prettier:check

Update the --max-warnings value for the lint command when the baseline warning count is intentionally reduced.

Publishing

1. Build the package npm run build
2. Login to npm using npm login
3. Increment the version using npm version patch|minor|major
4. Dry run the publish to verify everything works npm publish --dry-run
5. Publish using npm publish --access public

Troubleshooting

Where do I create a username and password

https://www.npmjs.com/

Who can invite me to the npm project so I can publish

Eric Strabala Ethan Dyas Chris Kollars