Use a common versioning system to ensure consistency in the versioning approach across microfrontends. Microfrontends are a way of breaking down a large frontend application into smaller, more manageable pieces. Each microfrontend is developed and deployed independently, which means that they can have different versions at any given time. To ensure that the microfrontends work together seamlessly, it is important to have a common versioning system that all teams follow.

A common versioning system ensures that all microfrontends are versioned in a consistent way. This makes it easier to manage dependencies between microfrontends and to ensure that the correct versions are deployed together. It also makes it easier to track changes and to identify which version of a microfrontend is currently running in production.

One example of a common versioning system is Semantic Versioning (SemVer). SemVer is a widely used versioning system that provides a clear and consistent way of versioning software. It consists of three numbers separated by dots: MAJOR.MINOR.PATCH. The MAJOR version is incremented when there are incompatible changes, the MINOR version is incremented when new functionality is added in a backwards-compatible manner, and the PATCH version is incremented when bug fixes are made in a backwards-compatible manner. By following SemVer, all teams can ensure that their microfrontends are versioned in a consistent way, making it easier to manage dependencies and track changes.

// Example of SemVer versioning
"dependencies": {
  "my-microfrontend": "^1.2.3"
}