In the root directory, you can run:
Install all development dependencies.
Run a local storybook with all the components and their stories.
Link packages into root to have only one node_modules
Create new Lerna managed component.
Adds new depdency to all subsequent packages lerna add (For example styled-components needed to be installed as a dependency)
Adds dependencies as peerDependencies to all the packages.
Runs in all the packages the npm dev script.
The CI jobs evaluate the commit messages, when merged on master. A short summary for conventional commits can be found on Conventional Commits and on Angular Release Messages. The most important types are:
- fix: patches a bug in your codebase (this correlates with PATCH in semantic versioning, x.x.1 -> x.x.2).
- feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in semantic versioning x.1.x -> x.2.x).
- BREAKING CHANGE: or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in semantic versioning 1.x.x -> 2.x.x). A BREAKING CHANGE can be part of commits of any type.
An example commit message has the following logic:
<type>(<optional scope>): <short summary>
│ │ │
│ │ └─⫸ Summary in present tense. Not capitalized. No period at the end.
│ │
│ └─⫸ Optional Commit Scope: ls-card|ls-list|ls-XXXX
│
└─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|style|test
- Copy existing component.
- Adjust package.json of new component and add correct type file (name of the .d.js).
- Run
lerna link convert
in root - run
yarn
to generate new yarn.lock