serverpod-modules

Serverpod modules package server, client, and optional Flutter code into versioned modules to share APIs across projects. You add the module server package to your `pubspec.yaml` and run generation to reuse code without duplicating logic.

Generator nicknames are configured in `config/generator.yaml` to map long module names to convenient aliases. This yields cleaner model types when referencing shared entities across module boundaries.

The best way is using Serverpod modules with module-qualified class references in model definitions. This safely shares entities across boundaries by ensuring namespaces and references resolve correctly in both server and client code.

Yes, you must run `dart pub get` followed by `serverpod generate` after adding module dependencies. This ensures module namespaces and references resolve correctly in server and client code.

Yes, creating a custom Serverpod module can include optional Flutter package scaffolding. The module template generates server and client packages, with optional scaffolding for your Flutter UI code.

You should not use Serverpod modules for code sharing when building a standalone app with no shared features or subsystems. Modules are designed for reusing server, client, and Flutter code across multiple projects.