web/apps/admin/vite.config.ts (1)

37-40: Make the alias robust to workspace hoisting.
path.resolve(__dirname, "node_modules/react-router-dom") assumes a local node_modules folder. In pnpm/yarn workspaces, this path can be absent, causing the alias to point to a non-existent location. Consider resolving via Node’s module resolution instead.

♻️ Suggested change

 import path from "path";
+import { createRequire } from "module";
 import { fileURLToPath } from "url";

 const __dirname = path.dirname(fileURLToPath(import.meta.url));
+const require = createRequire(import.meta.url);
+const reactRouterDomPath = require.resolve("react-router-dom");

   resolve: {
     alias: {
-      "react-router-dom": path.resolve(__dirname, "node_modules/react-router-dom"),
+      "react-router-dom": reactRouterDomPath,
     },
   },

web/lib/admin/views/audit-logs/sidepanel-list-link.tsx (1)

5-33: Discriminated union recommended to prevent silent non-link rendering when isLink is true without onNavigate.

All current usages correctly pass onNavigate when using SidepanelListItemLink. However, the current prop design allows isLink={true} with missing onNavigate, which silently renders as plain text instead of a link. Consider adopting the discriminated union pattern to enforce this constraint at compile time and prevent future misconfiguration:

🔧 Suggested type tightening (discriminated union)

-type SidepanelListItemLinkProps = {
-  isLink: boolean;
-  children: ReactNode;
-  href: string;
-  label: string;
-  onNavigate?: (path: string) => void;
-  "data-test-id"?: string;
-};
+type SidepanelListItemLinkProps =
+  | {
+      isLink: true;
+      children: ReactNode;
+      href: string;
+      label: string;
+      onNavigate: (path: string) => void;
+      "data-test-id"?: string;
+    }
+  | {
+      isLink: false;
+      children: ReactNode;
+      href: string;
+      label: string;
+      onNavigate?: never;
+      "data-test-id"?: string;
+    };