Known Issues and Status

Known Issues & Status

This page tracks current known issues, temporary workarounds, and the state of the test suite.

Links: Quick Start Guide • Validation Scripts • Troubleshooting • Architecture Overview

Git backup & branch workflow

We recommend creating a backup/staging branch and stashing local changes before experimenting with the demo or docs changes.

# From repo root
git status
# Stash untracked + tracked changes (if any)
git stash -u
# Create a working branch for demo/documentation updates
git checkout -b docs/demo-setup

ESM exports cleanup (pending)

• Symptom: Jest fails parsing ES modules; mismatches between package.json exports and actual build outputs.
• Impact: Affects test suite, not runtime demo flows.
• Status: Deferred. The demo works; we will align package exports to dist outputs in a subsequent task.
• Reference: See Troubleshooting for tips to address locally if needed.

React SSR workaround (temporary)

• To avoid workspace install issues during demo, we install SSR runtime at repo root:

npm install react@18.2.0 react-dom@18.2.0 --no-save

• This is a demo-only workaround; do not use in production packaging. Proper workspace linking/publishing should be configured instead.

Test suite status (non-blocking for demo)

• Current: Test suite has ESM-related failures (e.g., "Unexpected token 'export'").
• Demo impact: None. Runtime and data layer work; see Validation Scripts.
• Next steps (post-demo):
  • Align package.json exports with actual dist outputs
  • Avoid mapping packages directly to src/ in Jest without ESM transform
  • Re-enable CI test matrix once above are addressed