feat(typescript): add path aliases and enforce strict mode across TS …

[Sendi0011]

Summary

This PR introduces TypeScript path aliases and enforces strict type checking across the TypeScript packages in the repository to improve maintainability, developer experience, and type safety.

Closes #391

Changes Made

TypeScript Configuration

• Added path alias support (@/) for TypeScript packages

• Enabled and standardized strict TypeScript settings

• Explicitly enforced:

  • strict: true
  • noImplicitAny: true
  • strictNullChecks: true

API Package

Updated:

• api/tsconfig.json
• api/jest.config.js
• .eslintrc.json

Changes:

• Added alias resolution support
• Added ESLint import consistency rules
• Updated imports to use alias-based paths where applicable

Oracle Package

Updated:

• oracle/tsconfig.json
• oracle/vitest.config.ts
• .eslintrc.json

Changes:

• Added alias resolution support
• Updated relative imports to alias-based imports
• Removed problematic .js import extensions where needed

Root Configuration

Updated:

• tsconfig.base.json
• root package.json

Changes:

• Centralized strict TypeScript settings
• Added workspace alignment for TypeScript tooling consistency

Example Import Migration

Before:

import { logger } from "../../utils/logger";

After:

import { logger } from "@/utils/logger";

Why This Change

Relative imports across deeply nested directories were becoming difficult to maintain and error-prone. This update improves:

• readability
• refactor safety
• IDE navigation
• autocomplete support
• long-term maintainability

Strict mode also improves runtime reliability by catching unsafe typing earlier during development.

Validation Performed

• Verified TypeScript configuration updates
• Verified alias resolution setup for Jest/Vitest
• Updated affected imports

[vercel]

@Sendi0011 is attempting to deploy a commit to the smartdevs17's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@Sendi0011 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits