Repository navigation
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR updates the path alias configuration by replacing vite-tsconfig-paths plugin with native Vite alias resolution and adjusts TypeScript path mappings accordingly.
- Removed
vite-tsconfig-pathsplugin dependency in favor of native Vite resolve.alias configuration - Updated TypeScript
baseUrlandpathsconfiguration for consistency with the new Vite setup - Bumped package version from 3.2.6 to 3.2.7
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| template/vite.config.ts | Replaced vite-tsconfig-paths plugin with manual resolve.alias configuration using the path module |
| template/tsconfig.json | Updated baseUrl to project root and adjusted paths mapping to align with new Vite alias configuration; removed esModuleInterop option |
| package.json | Version bump to 3.2.7 |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| import { defineConfig } from "vitest/config"; | ||
| import tsconfigPaths from "vite-tsconfig-paths"; | ||
| import path from "path"; |
There was a problem hiding this comment.
The vite-tsconfig-paths package is no longer used after removing the tsconfigPaths() plugin from the configuration. Consider removing this package from the devDependencies in template/package.json to keep dependencies clean and reduce bundle size.
| }, | ||
| "resolve": { | ||
| "alias": { | ||
| "@": path.resolve(process.cwd(), "./src") |
There was a problem hiding this comment.
Using process.cwd() assumes Vite is always run from the project root directory. Consider using fileURLToPath(new URL('./src', import.meta.url)) for more reliable path resolution that works regardless of the current working directory, or simply use ./src as Vite will resolve it relative to the config file location.
No description provided.