chore: 절대경로(@ alias) 및 Tailwind Vite 플러그인 설정 #5

[juiuj]

Issue

• [chore] 절대경로 설정 #5

Work Done

• 절대경로 적용
  • 가독성, 유지보수성 개선을 위함

Comment

• 프로젝트 구조 개선을 위한 절대경로 적용
• @coderabbitai review

Summary by CodeRabbit

Chores

• Refactored ESLint configuration with updated plugin structure and simplified language options
• Added import resolution and path aliasing configuration for cleaner module imports using "@" shorthand
• Updated development dependencies, including new ESLint import plugins for enhanced linting
• Restructured Vite and jsconfig configuration files to support path alias resolution across the project

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
react-seemara-project	Ready	Preview, Comment	Jan 3, 2026 8:27am

[coderabbitai]

Warning

Rate limit exceeded

@juiuj has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 14 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between b3d8573 and 7953f26.

📒 Files selected for processing (1)

• vite.config.js

Warning

.coderabbit.yaml has a parsing error

The CodeRabbit configuration file in this repository has a parsing error and default settings were used instead. Please fix the error(s) in the configuration file. You can initialize chat with CodeRabbit to get help with the configuration file.

💥 Parsing errors (1)

Validation error: String must contain at most 250 character(s) at "tone_instructions"

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

📝 Walkthrough

Walkthrough

The changes introduce path aliasing (@ → ./src) across the build and linting toolchain. This includes refactoring ESLint configuration to use explicit plugins and simplified structure, adding jsconfig.json with baseUrl and path mappings, configuring Vite with alias resolution, and updating package.json dependencies to support these configurations.

Changes

Cohort / File(s)	Summary
Path Aliasing Setup eslint.config.js, jsconfig.json, vite.config.js	Introduces module path aliasing for @ → ./src across build and lint toolchain. ESLint config refactored: export pattern changed from defineConfig([...]) to plain array [...], imports simplified (dropped @eslint/js, globals, React hooks/refresh), plugins (react, import) and settings added with import resolver alias mapping. jsconfig.json and vite.config.js both configure alias resolution with path.resolve().
Dependencies package.json	Moved @tailwindcss/vite from dependencies to devDependencies (v^4.1.18). Added eslint-import-resolver-alias (v^1.1.2) and eslint-plugin-import (v^2.32.0) as new devDependencies.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

Poem

🐰 Path aliases dance with joy so bright,
@ now points to src with elegant might,
ESLint, Vite, and config align,
Module imports sparkle and shine,
The toolchain's harmony starts to take flight! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main changes: setting up absolute path alias (@) and configuring Tailwind Vite plugin, which aligns with the actual changeset across eslint.config.js, jsconfig.json, package.json, and vite.config.js.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7556913 and b3d8573.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

• eslint.config.js
• jsconfig.json
• package.json
• vite.config.js

🔇 Additional comments (8)

package.json (2)

24-25: New ESLint dependencies support alias resolution.

The additions of eslint-import-resolver-alias and eslint-plugin-import correctly support the new "@" path alias feature implemented across the toolchain.

---

19-19: Correct placement of build-time dependency.

Moving @tailwindcss/vite to devDependencies is appropriate since it's a build-time tool, not a runtime dependency. No known security vulnerabilities were found for this version.

However, there is conflicting information regarding the current version: web sources indicate both 4.1.18 (Dec 11, 2025 release) and 4.1.13 as the latest version. Verify whether 4.1.18 is indeed the current published version and clarify if the version change represents a minor or patch update.

jsconfig.json (1)

1-9: Well-configured path alias for IDE support.

The jsconfig.json is correctly configured to provide IntelliSense and path resolution for the "@" alias in editors. The configuration aligns perfectly with the Vite and ESLint alias setups.

vite.config.js (1)

11-15: Alias configuration structure is correct.

The resolve.alias configuration properly maps "@" to the src directory, enabling clean imports like import Component from "@/components/Component".

eslint.config.js (4)

1-4: Imports correctly support the new plugin-driven ESLint configuration.

The imports properly set up the globals, React plugin, import plugin, and path utilities needed for the alias resolution feature.

---

6-6: Simplified export structure is acceptable.

Removing the defineConfig wrapper and exporting a plain array is valid for ESLint flat config format. This is a cleaner approach.

---

25-25: Korean comment is intentional.

The placeholder comment "여기에 기존 룰 유지/추가" (here to maintain/add existing rules) matches the project's Korean context from the PR description.

---

12-23: The alias resolver configuration is correctly formatted for eslint-import-resolver-alias v1.1.2.

The map array with 2-item arrays and the extensions array follow the plugin's documented configuration format and will work as expected.