NextSpark Monorepo Architecture

The NextSpark monorepo architecture organizes code into distinct packages, themes, plugins, and apps. This structure clarifies package relationships and helps developers quickly grasp how the codebase is structured for adding new features.

Dependency management in this pnpm monorepo requires correctly distinguishing between dependencies and peerDependencies. Understanding these rules prevents common pitfalls when managing inter-package dependencies across the NextSpark framework.

You can filter themes and plugins during the build process using environment variables. This build-time filtering mechanism optimizes the build by including only the specific themes and plugins required for your target deployment.

You need to regenerate registries before building when the monorepo structure or package contents change. This process ensures the build system accurately references the updated themes, plugins, and apps within the NextSpark framework.

Versioning different package types in a monorepo involves specific guidelines for apps, themes, and plugins. Following these version management rules ensures consistency across dependencies when updating or releasing new features.

Using peerDependencies instead of dependencies for monorepo packages prevents duplicate versions and common dependency pitfalls. This strategy ensures packages rely on a single shared instance of a library across the NextSpark framework.