style: apply Codacy quick fixes across components and vite config

[HikaruQwQ]

Summary by CodeRabbit

• Security

  • Improved the external registration link’s security settings.

• Refactor

  • Standardized callback and cleanup handler formatting across navigation, consent, scrolling, notifications, and team components.
  • Clarified development and preview fallback handling without changing behavior.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 22cae753-c709-45a6-ade9-b4812ce5edec

📥 Commits

Reviewing files that changed from the base of the PR and between 38fe1f6 and fe53c60.

📒 Files selected for processing (7)

• src/components/CookieConsent.tsx
• src/components/Footer.tsx
• src/components/Nav.tsx
• src/components/ScrollTop.tsx
• src/components/Toast.tsx
• src/pages/Team.tsx
• vite.config.ts

Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The PR reformats React callbacks, adds noreferrer to the MIIT link, and replaces inline Vite middleware returns with explicit next(); return; statements. Runtime behavior remains unchanged.

Changes

UI and server cleanup

Layer / File(s)	Summary
UI callback formatting src/components/CookieConsent.tsx, src/components/Nav.tsx, src/components/ScrollTop.tsx, src/components/Toast.tsx, src/pages/Team.tsx	Effect cleanups and event handlers now use block-bodied arrow functions. Their actions remain unchanged.
MIIT link attribute src/components/Footer.tsx	The MIIT registration link adds noreferrer alongside noopener.
Vite fallback control flow vite.config.ts	Development and preview fallback middleware now calls next() and then returns explicitly.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to fe53c

This PR applies localized style and configuration cleanup without any identified behavior or production-impacting issue; no actionable merge-blocking risk remains beyond normal checks and review.

Possibly related PRs

• PolarisHackathon/homepage#16: Both PRs modify the Team page’s hash-scroll effect.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the Codacy style fixes across the listed components and Vite configuration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}