Skip to content

Comments

feat: vercel.json 파일 추가 및 리라이트 설정 구성#599

Merged
oesnuj merged 1 commit intodevelop-fefrom
fix/#598-vercel-spa-routing
Jul 27, 2025
Merged

feat: vercel.json 파일 추가 및 리라이트 설정 구성#599
oesnuj merged 1 commit intodevelop-fefrom
fix/#598-vercel-spa-routing

Conversation

@oesnuj
Copy link
Member

@oesnuj oesnuj commented Jul 27, 2025

#️⃣연관된 이슈

#598

📝작업 내용

  • Vercel에서 SPA 라우팅 시 발생하는 404 Not Found 오류 수정
  • 프로젝트 루트에 vercel.json 파일 추가
  • 모든 경로 요청을 /로 리라이트하여 SPA 라우터가 처리하도록 설정
// vercel.json
{
  "rewrites": [
    { "source": "/(.*)", "destination": "/" }
  ]
}

Summary by CodeRabbit

  • Chores
    • 모든 프론트엔드 요청이 루트 경로로 리다이렉트되도록 구성 파일이 추가되었습니다.

@oesnuj oesnuj self-assigned this Jul 27, 2025
@oesnuj oesnuj added 🌏 Deploy 배포 관련 💻 FE Frontend labels Jul 27, 2025
@vercel
Copy link

vercel bot commented Jul 27, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
moadong ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 27, 2025 2:42pm

@netlify
Copy link

netlify bot commented Jul 27, 2025

Deploy Preview for moadong ready!

Name Link
🔨 Latest commit 1a729af
🔍 Latest deploy log https://app.netlify.com/projects/moadong/deploys/68863ae9c53ee200081148c0
😎 Deploy Preview https://deploy-preview-599--moadong.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 38
Accessibility: 89
Best Practices: 92
SEO: 92
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 27, 2025

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: Invalid regex pattern for base branch. Received: "**" at "reviews.auto_review.base_branches[0]"
⚙️ Configuration instructions
  • Please see the configuration documentation for more information.
  • 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

vercel.json 설정 파일이 frontend 디렉토리에 새로 추가되었습니다. 이 파일은 모든 요청을 루트 경로(/)로 리라이트하는 규칙을 정의합니다. 이를 통해 프론트엔드로 들어오는 모든 요청이 내부적으로 루트 엔드포인트로 리디렉션됩니다.

Changes

파일/경로 변경 요약
frontend/vercel.json 모든 요청을 /로 리라이트하는 규칙 추가

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/#598-vercel-spa-routing

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@PororoAndFriends PororoAndFriends self-requested a review July 27, 2025 14:43
Copy link
Collaborator

@PororoAndFriends PororoAndFriends left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

고생하셨습니다!!

Copy link
Member

@Zepelown Zepelown left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

고생하셨습니다.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
frontend/vercel.json (1)

1-3: 정적 자산‧API 경로까지 덮어쓰는 전역 리라이트는 위험할 수 있습니다

"/(.*)" 패턴은 /_next/*, /static/*, /api/* 등 Vercel 내부 자산과 API 요청까지 모두 루트로 돌려보냅니다.
SPA 용도라 하더라도 정적 파일이나 API가 존재한다면 404 또는 잘못된 응답을 유발할 수 있으니, 다음과 같이 예외를 두거나 handle: "filesystem" 단계를 먼저 선언하는 방식을 고려해 주세요.

{
-  "rewrites": [{ "source": "/(.*)", "destination": "/" }]
+  "rewrites": [
+    { "source": "/(?!api|_next|static)(.*)", "destination": "/" }
+  ]
}

예외 패턴은 프로젝트 구조에 맞게 조정해 주시면 됩니다.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ecddc53 and 1a729af.

📒 Files selected for processing (1)
  • frontend/vercel.json (1 hunks)

@oesnuj oesnuj merged commit 91a4ef2 into develop-fe Jul 27, 2025
9 checks passed
@oesnuj oesnuj deleted the fix/#598-vercel-spa-routing branch July 28, 2025 06:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🌏 Deploy 배포 관련 💻 FE Frontend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants