Running Apps¶
Every dev command¶
npm run dev:corporate # @akshaya/corporate-web
npm run dev:software # @akshaya/software-web
npm run dev:logistics # @akshaya/logistics-web
npm run dev:commerce # @akshaya/commerce-web
npm run dev:embroidery # @akshaya/embroidery-web
npm run dev:admin # @akshaya/admin-web
npm run dev:investors # @akshaya/investors-web
npm run dev:api # @akshaya/api-worker (wrangler dev, local D1+R2 emulators)
Each of the first 7 is a plain vite dev server for that workspace - fast HMR, no Wrangler
involved (the run_worker_first Worker routes on Corporate/Software/Admin are not exercised
by npm run dev:<app> - only by wrangler dev/a real deploy; see below if you need to test those
routes locally).
Testing an app's own Worker routes locally (Corporate, Software, Admin only)¶
Runs the actual Worker (static assets +/customer-portal*//api/customer/* routes) locally,
closer to production behavior than plain vite. Same pattern for apps/software-web and
apps/admin-web.
Every build command¶
npm run build # all 7 apps (what CI runs)
npm run build:corporate
npm run build:software
npm run build:logistics
npm run build:commerce
npm run build:embroidery
npm run build:admin
npm run build:investors
Which command should I use?¶
| I'm doing... | Command |
|---|---|
| Frontend-only work on one app | npm run dev:<app> |
| Testing that app's own Worker routes (Corporate/Software/Admin only) | cd apps/<app> && npx wrangler dev |
| Working on the central API | npm run dev:api |
| Confirming a build won't break CI | npm run build (all apps) or npm run build:<app> (one) |
| Confirming shared-CSS changes propagated | npm run check:portal-styles-drift |
| Running the test suite | npm test |
Validation¶
Troubleshooting¶
See Troubleshooting.