Context
The WebSocket server currently runs via node server/server.js. For npm packaging, developers need a defined way to start it. Three options exist:
Options
- Bundled CLI —
npx reactime-native starts the server (simplest DX)
- Separate package —
npm install -g reactime-native-server (cleaner separation)
- Auto-started by agent — server starts when
initReactimeNative() is called (most magical, hardest to implement)
Decision needed
The team needs to agree on option 1, 2, or 3 before implementation begins. This decision gates the entire v0.3.0 packaging milestone.
Acceptance criteria
Context
The WebSocket server currently runs via
node server/server.js. For npm packaging, developers need a defined way to start it. Three options exist:Options
npx reactime-nativestarts the server (simplest DX)npm install -g reactime-native-server(cleaner separation)initReactimeNative()is called (most magical, hardest to implement)Decision needed
The team needs to agree on option 1, 2, or 3 before implementation begins. This decision gates the entire v0.3.0 packaging milestone.
Acceptance criteria
CLAUDE.mdengineering decision logREADME.mdreflects the correct start command