All things about monorepo frontend. you can see all changes in CHANGELOG.md

• Usage
• Release
  • Versioning
  • Process
• Code Structure
  • Packages
    • @monorepo/token
    • @monorepo/icons
    • @monorepo/core
    • @monorepo/portal
• Links

gh repo clone ddalpange/monorepo-template
yarn install
yarn prepare
yarn dev

we're using the rule we discussed with QA engineers not semantic versioning.

major - we're not using.
minor - sprint number
fetch - count of deployments

you can see all versions we deployed in package.json or git tags if you want set new version, run this command it will update CHANGELOG.md and commit on your current branch with tag.

yarn versioning
# input your next version (now is 0.15.0)
0.15.1

Big changes.

1. removed stg, prod branches. those are replaced with git tags.
2. create sprint release branch from main branch.
3. if QA engineer finds bug. you can fix it on sprint release branch.
4. you will increase fetch version on release branch and push tag (stg or prod) to git.
5. After sprint. merge release branch to main branch.

Example Flow.

main -> yarn versioning 0.15.0
main -> git checkout -B release/sp-15
release/sp-15 -> git tag -a stg 
release/sp-15 -> git push --follow-tags --force # replace old tag
# ... fixed some bugs ...
release/sp-15 -> yarn versioning 0.15.1
release/sp-15 -> git tag -a stg && git tag -a prod
release/sp-15 -> git checkout main
# ... completed sp-15 ...
main -> git merge release/sp-15

Monorepo tooling

we're using yarn workspace and ultra-runner

you can run specific command to all package in <root> folder. ultra detect package's dependencies and sort out commands.

I already defined useful shortcuts. define other thing if you want.

ultra -r yarn build

have minimal unit variables and style sheets. (It may be automatically created later.)

the Icons created automatically through the FIGMA API

The actual React component implementation.

This product is provided to users

• github