Installation and Versioning

Every published package ships from GitHub Packages under the @caffeinebounce scope.

Install a package

yarn add @caffeinebounce/ui
yarn add @caffeinebounce/identity

Packages with server-only helpers expose separate subpaths when needed:

• @caffeinebounce/identity/server
• @caffeinebounce/commerce/server
• @caffeinebounce/logger/client

Versioning model

• Versions are managed with Changesets.
• Packages are versioned independently.
• The monorepo follows semver, but several packages are still in 0.x, so minor releases can contain meaningful surface expansion.

Import strategy

• Start with the root entrypoint when it matches the app surface you need.
• Prefer documented subpaths for coarse-grained imports like @caffeinebounce/ui/forms or @caffeinebounce/shared-utils/formatters.
• Do not deep-import internal source files from consuming apps.

Consumer expectations

• Treat the portal as the public package contract.
• Check each package page for status, supported entrypoints, and changelog coverage before upgrading.
• If an app depends on a behavior not represented here, the shared package contract probably needs to be tightened.