Skip to content

fix: correct frontend directory from apps/frontend to apps/dashboard#125

Open
spmridula wants to merge 1 commit into
Devnil434:mainfrom
spmridula:fix/frontend-misdirection-use-dashboard
Open

fix: correct frontend directory from apps/frontend to apps/dashboard#125
spmridula wants to merge 1 commit into
Devnil434:mainfrom
spmridula:fix/frontend-misdirection-use-dashboard

Conversation

@spmridula
Copy link
Copy Markdown

Problem

The README Quick Start (step 8) instructs contributors to run:

cd apps/frontend && npm install

This fails immediately because apps/frontend/ has no package.json. The actual working frontend points another.

Root Cause

The working frontend is apps/dashboard/ (React 19 + Vite + Tailwind, fully scaffolded with package.json, vite.config.js, src/). apps/frontend/ appears to be an abandoned stub from an earlier Next.js plan that was never built out.

Additionally, apps/frontend/components/ZoneEditor.tsx was orphaned in the wrong directory with no surrounding app context.

Changes

  • README Quick Start step 8: apps/frontend -> apps/dashboard
  • README project structure diagram: updated to reflect actual layout, to show dashboard/ not frontend/
  • Dashboard URL corrected: localhost:3000 -> localhost:5173 (Vite default)
  • Updated make install-frontend description to reference apps/dashboard
  • ZoneEditor.tsx moved to apps/dashboard/src/components/
  • apps/frontend/ stub removed

Testing

cd apps/dashboard
npm install   # succeeds
npm run dev   # opens at http://localhost:5173

Fixes #119

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 27, 2026

Warning

Review limit reached

@spmridula, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 22 minutes and 14 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 135933dc-9505-4fa2-9af5-3a644bc64cd8

📥 Commits

Reviewing files that changed from the base of the PR and between 3c9175c and 929a414.

📒 Files selected for processing (2)
  • README.md
  • apps/dashboard/src/components/ZoneEditor.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: apps/frontend/ missing package.json

1 participant