Skip to content

bug: <AnimatedRoutes> component is defined but never rendered — ErrorBoundary, PageTransition, and /forge /focus routes are completely dead #1501

@Abhishek2005-ard

Description

@Abhishek2005-ard

Bug Description

App.jsx defines two separate routing trees — <AnimatedRoutes> and a plain
<Routes> block directly inside <App>. The <AnimatedRoutes> component is never
mounted anywhere in the JSX
, making it entirely dead code. The app silently runs on
the plain <Routes> tree which is missing critical features.

Location

frontend/src/App.jsx

Current Code (Buggy)

// Defined but NEVER used ↓
const AnimatedRoutes = () => {
  return (
    <AnimatePresence mode="wait">
      <Routes>
        {/* Has ErrorBoundary, PageTransition, /forge, /focus routes */}
      </Routes>
    </AnimatePresence>
  );
};

const App = () => {
  return (
    <BrowserRouter>
      <Navbar />
      <main>
        <Routes>  {/* ← This plain Routes tree is what actually runs */}
          {/* No ErrorBoundary, No PageTransition, missing /forge & /focus */}
        </Routes>
      </main>
    </BrowserRouter>
  );
};

Metadata

Metadata

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions