Skip to content

[BUG][P0] Wrong relative imports block module resolution in API routes #9

@l0gic

Description

@l0gic

Describe the bug

Several API route files use incorrect relative imports (../../../../../lib/auth) instead of the project's @/lib/auth alias, causing module resolution failures.

To Reproduce

  1. Run pnpm run dev or pnpm run build
  2. Observe module resolution errors for:
    • src/app/api/analytics/activity/route.ts
    • src/app/api/analytics/user-stats/route.ts
    • src/app/api/test/feature-584-audit-immutability/route.ts
    • src/app/api/privacy/delete/route.ts
    • src/app/api/admin/audit-logs/route.ts

Expected behavior

All imports should use the @/ alias consistently for proper module resolution.

Possible Solution

Replace all relative imports like ../../../../../lib/auth with @/lib/auth.

Files Affected

  • src/app/api/analytics/activity/route.ts:4
  • src/app/api/analytics/user-stats/route.ts:4
  • src/app/api/test/feature-584-audit-immutability/route.ts:12
  • src/app/api/privacy/delete/route.ts:5
  • src/app/api/admin/audit-logs/route.ts:21

Discovered By

Automated build error analysis during dev server startup.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions