Appearance

Best Practices ​

This page summarizes practical development defaults for racletteJS apps.

Plugin-First Development ​

  • Build new features in plugins first.
  • Keep business logic plugin-scoped unless there is a clear runtime-level reason not to.
  • Prefer reusable plugin code over app-local override code.

Use Overrides Carefully ​

  • services/frontend/* and services/backend/* can replace core files by path.
  • Use this as an escape hatch, not as default architecture.
  • Keep overrides minimal and documented.

App-Safe Namespace ​

  • If you only want to add app code, prefer services/*/src/app/*.
  • The app space is reserved for app-local additions and helps avoid accidental core replacement.

Dependency Workflow ​

  • Add runtime dependencies with yarn add-package.
  • Avoid direct dependency edits in generated .raclette files.
  • If packages.json is edited manually, run update/restart flow so containers pick changes up.