package-management

To synchronize CDK versions across a monorepo, align package.json manifests and workspace references so that the root and all subpackages share identical aws-cdk-lib and constructs versions, preventing version drift and dependency conflicts across packages.

Managing workspace references in a CDK monorepo involves configuring package.json for subpackages with local workspace links and version pinning. This ensures cross-package references remain intact and dependencies resolve correctly without nested node_modules.

Aligning tsconfig references and package.json manifests requires coordinating package metadata across your workspace. This process updates version pinning and cross-package references so that TypeScript project references match your dependency configuration.

Yes, you can use postinstall scripts to maintain a clean workspace and avoid nested node_modules. This approach ensures that workspace links and CDK version management remain intact across all subpackages after dependencies are installed.

CDK version drift happens when root and subpackages independently resolve aws-cdk-lib and constructs versions without manifest alignment. Synchronizing package.json and workspace references prevents this drift and ensures consistent CDK behavior across the repository.

A monorepo setup is not strictly required, but package metadata coordination and CDK version pinning are specifically designed for monorepo scenarios. These features handle cross-package references and workspace links where multiple packages must share CDK versions.