Robo-Dapp Separation Plan

Problem: Robo-Dapp exists as a separate Next.js app but is incorrectly imported into main App.tsx, creating build conflicts.

Current Situation

robo-hub/ (Vite app)
├── App.tsx ← Imports from Robo-Dapp ✗ WRONG
├── package.json (React 18.2, Vite)
│
└── Robo-Dapp/ (Next.js app)
    ├── package.json (React 19.0, Next.js) ← Conflict!
    ├── app/
    └── components/

Solution: Complete Physical Separation

Phase 1: Remove All Robo-Dapp Imports from App.tsx

Files to check:

• App.tsx (remove any Robo-Dapp imports/references)

• Any components that reference Robo-Dapp

Action:

# Find all Robo-Dapp imports
grep -r "from.*Robo-Dapp" --include="*.tsx" --include="*.ts"

# Remove those imports and replace with placeholder

Phase 2: Deploy Robo-Dapp as Separate Next.js App

Deployment options:

1. Vercel (recommended for Next.js)

   cd Robo-Dapp
   vercel

2. Same server, different port

   # Main app on :3000
   # Robo-Dapp on :3001

3. Subdomain

   fleetos.t420.com → Vite app
   robo-hub.t420.com → Vite app
   robo-dapp.t420.com → Next.js app (separate deployment)

Phase 3: Share Services via npm Private Packages

Instead of file imports, publish shared services:

# Create shared package
npm init -y @t420/shared-services

# Publish to npm private registry or GitHub packages
npm publish --access restricted

Then in Robo-Dapp:

// Instead of:
import NotificationService from '../robo-hub/services/NotificationService';

// Use:
import { NotificationService } from '@t420/shared-services';

Phase 4: API Communication Between Apps

For inter-app communication, use APIs:

// Main app → Robo-Dapp
const response = await fetch('https://robo-dapp.t420.com/api/fleet-status');

// Robo-Dapp → Main app
const response = await fetch('https://robo-hub.t420.com/api/rfq-status');

Benefits

• ✅ No build conflicts - Separate deployments, separate dependencies

• ✅ Independent scaling - Scale Next.js app separately from Vite app

• ✅ Clear boundaries - No accidental cross-imports

• ✅ Faster builds - Each app builds independently

• ✅ Technology flexibility - Can upgrade Next.js without affecting Vite

Current Status

PENDING: Requires manual review of App.tsx to find all Robo-Dapp references and remove them.

Next Steps

1. Audit App.tsx for Robo-Dapp imports

2. Remove imports and replace with navigation to separate URL

3. Deploy Robo-Dapp to separate URL/port

4. Test inter-app navigation

5. (Future) Publish shared services as npm package

Migration Checklist

• Find all Robo-Dapp imports in main codebase

• Remove imports from App.tsx

• Create placeholder "Open Robo-Dapp" button that links to separate URL

• Deploy Robo-Dapp to separate port/URL

• Test navigation between apps

• Document new architecture