The original plan was to develop the series of Sprout addons as separate packages that could be installed individually dependent on the requirements of the user. It was likely that the majority of people would require at least one of the addons, so it included an additional step to get started.
There was also an outstanding deprecation within the codebase that had been flagged quite early and was waiting for full deprecation in the next major release.
The decision was made to develop all of the addons within a single monorepo codebase that functions as a single package, providing all functionality and reducing the number of steps required to get started.
Due to the massive restructure of the codebase, which affected the namespaces, the public API was broken, so a bump to the major version was required.
The decision was between this approach and sticking with the original plan.
The other alternative was to develop the addons as separate packages and keep them separated only to pull in when needed.
This was rejected for the following reasons: