Set up initial project structure with Vite, React, and TypeScript; ad…

[rahul-vyas-dev]

This PR sets up the initial frontend project structure for Org Explorer using Vite + React + TypeScript. The goal of this change is to establish a clean, modern, and scalable foundation that future features can be built on top of.

The setup includes the basic project configuration, TypeScript support, and a development environment optimized for fast iteration and minimal overhead. This initial structure will support upcoming work such as GitHub API integration (REST and GraphQL), local caching using IndexedDB and localStorage, and interactive graph-based visualizations for exploring organizations.

No application logic is introduced in this PR. It is intentionally limited to project initialization so that subsequent changes can be reviewed and evolved incrementally in a clear and structured way.

Checklist

• My code follows the project's code style and conventions
• I have made corresponding changes to the documentation
• My changes generate no new warnings or errors
• I have joined the Discord server and I will share a link to this PR with the project maintainers there
• I have read the Contributing Guidelines

⚠️ AI Notice - Important!

We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.

@Zahnentferner

Summary by CodeRabbit

• New Features

  • OrgExplorer app scaffold is live with a minimal UI and entry point.

• Chores

  • Project initialized with tooling, TypeScript and bundler config, linting, npm scripts, global styles, HTML entry, and comprehensive .gitignore for a cleaner workspace.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new Vite + React + TypeScript project scaffold (OrgExplorer): package and tool configs, TypeScript and ESLint settings, Vite config, HTML entry, React entry/component, global and component CSS, and a comprehensive .gitignore.

Changes

Cohort / File(s)	Summary
Project metadata & scripts package.json	Adds project manifest, dependencies (react, react-dom), devDependencies (TypeScript, Vite, ESLint, plugins), and scripts (dev, build, lint, preview).
Build tool config vite.config.ts	Adds Vite config with React plugin: export default defineConfig({ plugins: [react()] }).
Linting eslint.config.js	Adds ESLint configuration (TypeScript, React, React Hooks, React Refresh) targeting .ts/.tsx and ignoring dist. Exports default config via defineConfig.
TypeScript configs tsconfig.json, tsconfig.app.json, tsconfig.node.json	Adds root composite tsconfig plus app and node-specific configs (ES targets, bundler module resolution, strict checks, JSX react-jsx, noEmit).
App entry & component src/main.tsx, src/App.tsx	Adds React 18 entry using createRoot and a minimal App component exporting "Hello, OrgExplorer!".
Styling src/index.css, src/App.css	Adds global base styles (typography, color-scheme, smoothing) and component/root layout styles (max-width, padding, centered content).
HTML shell index.html	Adds minimal HTML document with <div id="root"> and module script to src/main.tsx.
VCS ignores .gitignore	Adds comprehensive ignore rules: node_modules, builds (dist, build, out), caches, logs, env files, IDE files, OS artifacts, TypeScript build info, and test outputs.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

I nibble at code in a cozy den,
Vite and TypeScript stitched by my pen,
React buds sprout in the burrow tonight,
OrgExplorer hops into the light,
Come nibble, create — boundless delight! 🐇

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main objective of setting up the initial project structure with Vite, React, and TypeScript, which aligns with all file additions shown in the changeset.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

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

[rahul-vyas-dev]

Hello sir @Zahnentferner, could you please review this when you have time? That would help me proceed with further work and merge it, so that my upcoming PRs can avoid conflicts.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@index.html`:
- Line 5: The favicon link in index.html currently points to /vite.svg which
doesn't exist; update the href attribute in the <link rel="icon"...> element to
reference an existing asset (e.g., change /vite.svg to /aossie-logo.svg or
/stability.svg), or alternatively add a vite.svg file to the public/ directory;
ensure the chosen filename matches the asset present so the browser can load the
favicon.

🧹 Nitpick comments (2)

index.html (1)

7-7: Consider consistent casing for the project name.

The title uses lowercase "orgexplorer" while the App component uses "OrgExplorer". Consider aligning the casing for consistency (e.g., "OrgExplorer").

Suggested fix

-    <title>orgexplorer</title>
+    <title>OrgExplorer</title>

src/App.tsx (1)

3-10: LGTM - Clean placeholder component.

The component structure is appropriate for an initial setup. One minor optional refinement: the React fragment (<>...</>) is unnecessary when returning a single element.

Optional: Remove unnecessary fragment

 function App() {
-
   return (
-    <>
-      <h1>Hello, OrgExplorer!</h1>
-    </>
+    <h1>Hello, OrgExplorer!</h1>
   )
 }