Add modern dashboard skeleton

[mtrezza]

Summary

• set up a new React-based dashboard using Vite in new-dashboard/
• add ability to switch between dashboards via a link in the sidebar
• serve the new dashboard from Express
• keep build artifacts ignored via .gitignore
• ensure root scripts trigger build and lint for the new dashboard

Testing

• npm test (fails: Config options test because of missing statusCode)
• npm run build
• npm run lint

---

https://chatgpt.com/codex/tasks/task_e_686c1f5d2440832da0761d91f4c3fd8f

Summary by CodeRabbit

• New Features

  • Introduced a new dashboard accessible at the /new URL, featuring a modern React-based UI with Material UI components.
  • Added a sidebar link labeled "New Dashboard" for easy navigation.
  • The new dashboard allows viewing and updating cloud configuration parameters for Parse apps.

• Improvements

  • Updated build, lint, and test scripts to include the new dashboard in project workflows.
  • Enhanced authentication handling for the new dashboard route.

• Chores

  • Added and updated .gitignore files to exclude build artifacts and dependencies.
  • Added documentation and configuration files for the new dashboard setup.

[parse-github-assistant[bot]]

🚀 Thanks for opening this pull request!

[parse-github-assistant[bot]]

The label codex cannot be used here.

[coderabbitai[bot]]

📝 Walkthrough

Walkthrough

A new React-based dashboard ("new-dashboard") was introduced as a subproject, including its own build system, configuration, and UI. The main server was updated to serve this dashboard at /new, with authentication and static file handling. The main sidebar now links to the new dashboard, and build/test/lint scripts were updated to integrate its lifecycle.

Changes

File(s)	Change Summary
.gitignore, new-dashboard/.gitignore	Updated to ignore new-dashboard/node_modules/, dist/, editor/project files, logs, and build outputs.
Parse-Dashboard/app.js	Added middleware and routes to serve the new dashboard at /new with authentication and static file serving.
src/components/Sidebar/Sidebar.react.js	Added a "New Dashboard" link with icon to the sidebar footer for authenticated users.
package.json	Updated scripts to build, lint, and install the new-dashboard as part of main project workflows.
new-dashboard/README.md	Added documentation for the new React + Vite dashboard template and linting recommendations.
new-dashboard/package.json	Added project metadata, scripts, dependencies, and devDependencies for the new-dashboard subproject.
new-dashboard/eslint.config.js, vite.config.js	Added ESLint and Vite configuration for the new-dashboard React project.
new-dashboard/index.html	Added HTML entry point for the new dashboard React app.
new-dashboard/src/App.jsx, src/CloudConfig.jsx	Added main React app and cloud config management component for the dashboard UI.
new-dashboard/src/main.jsx	Added React entry point mounting the app to the DOM.
new-dashboard/src/App.css, src/index.css	Added CSS styles for the new dashboard UI.

Sequence Diagram(s)

sequenceDiagram
    participant Browser
    participant Server (Express)
    participant File System
    participant Auth

    Browser->>Server (Express): GET /new
    alt User is authenticated
        Server->>File System: Serve new-dashboard/dist/index.html
        File System-->>Server: index.html
        Server-->>Browser: index.html
    else User not authenticated
        Server->>Auth: Check authentication
        Auth-->>Server: Not authenticated
        Server-->>Browser: Redirect to /login?redirect=%2Fnew
    end

sequenceDiagram
    participant User
    participant New Dashboard (React)
    participant Parse Server

    User->>New Dashboard: Load UI (/new)
    New Dashboard->>Parse Server: GET /parse-dashboard-config.json
    Parse Server-->>New Dashboard: Dashboard config JSON
    User->>New Dashboard: Add or update cloud config param
    New Dashboard->>Parse Server: PUT /cloud-code-config (with masterKey)
    Parse Server-->>New Dashboard: Updated config
    New Dashboard-->>User: Updated config displayed

[!WARNING] There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error code ERR_SSL_WRONG_VERSION_NUMBER npm error errno ERR_SSL_WRONG_VERSION_NUMBER npm error request to https://10.0.0.28:4873/npm/-/npm-10.9.2.tgz failed, reason: C0EC0F8BFC7E0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354: npm error npm error A complete log of this run can be found in: /.npm/_logs/2025-07-07T20_18_38_822Z-debug-0.log

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[parseplatformorg]

:tada: Snyk checks have passed. No issues have been found so far.

:white_check_mark: security/snyk check is complete. No issues have been found. (View Details)

[patelmilanun]

I think this won't have the HMR, will check and compare it with mine. Also haven't we decided to use refine.dev?

[mtrezza]

Also haven't we decided to use refine.dev?

I didn't follow that route, but you are right; i've mentioned it in the issue discussion, it seems like a reliable framework. This here is really just a basic PoC to have both dashboard react versions running side by side.