Must be one of the following:
feat: A new feature. fix: A bug fix. docs: Documentation only changes. style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc). refactor: A code change that neither fixes a bug nor adds a feature. perf: A code change that improves performance. test: Adding missing tests. chore: Changes to the build process or auxiliary tools and libraries such as documentation generation.
Initial commit π π
New feature β¨ β¨
Bugfix π π
Documentation π π
Performance π π
Tests π¨ π¨
Refactor code π¨ π¨
Removing code/files π₯ π₯
Adding CI build system π· π·
Security π π
Upgrading dependencies β¬οΈ β¬οΈ
Downgrading dependencies β¬οΈ β¬οΈ
Critical hotfix π π
Work in progress π§ π§
Lint π π
Configuration files π§ π§
What if we split our codebase into tiny pieces, shipped 42 React versions from different CDNs, What if we did that so two teams don't have to talk to each other or, heaven forbid, collaborate on the same codebase? and called it "Micro Frontends"? It's like herding cats, but with code!
What if we took all the worst parts of managing a codebase, made sure everything that's supposed to work smoothly is broken into desperate parts, and instead of shipping one version of React, we shipped 42 different versions all from different CDNs? What if we did that so two teams don't have to talk to each other or, heaven forbid, collaborate on the same codebase? Welcome to Micro Frontends - where chaos meets code! π€ͺ