Update nuxt to version 4

[nurRiyad]

Summary by CodeRabbit

• Chores
  • Upgraded the app to Nuxt 4.x.
  • Migrated icon handling to the official @nuxt/icon module.
  • Updated development dependencies to align with the new framework and icon module.
  • Users may notice updated icon rendering and smoother runtime behavior with the newer stack.
  • No new features or API changes; existing functionality remains the same.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
blog	Error			Aug 18, 2025 3:50pm

[coderabbitai]

Walkthrough

Configuration updated to reference seo data from app/data and switch Nuxt icon module to @nuxt/icon. Dependencies adjusted in package.json to replace nuxt-icon with @nuxt/icon and upgrade Nuxt from 3.x to 4.0.3.

Changes

Cohort / File(s)	Change summary
Nuxt config updates nuxt.config.ts	Updated import path from ./data to ./app/data. Replaced module entry nuxt-icon with @nuxt/icon.
Dependency updates package.json	Removed nuxt-icon devDependency, added @nuxt/icon ^2.0.0. Upgraded nuxt from ^3.17.4 to ^4.0.3.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Update dependencies: bump nuxt to version 3.16.1 #85 — Also updates Nuxt version in package.json, indicating a related dependency upgrade path.

Poem

I twitched my nose and nudged the deps,
From three to four, the Nuxt now steps.
New icons shine, the old ones hop—
app/data burrow, a tidier stop.
Thump-thump! Code carrots stack in rows—
Ship it quick, before the garden grows. 🥕🐇

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch nuxt-4

---

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

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

nuxt.config.ts (1)

25-25: Prefer UTF-8 over UTF-16 for the document charset.

UTF-16 for HTML is unusual, inflates payloads, and may cause charset issues in some tooling. UTF-8 is the web standard.

Example:

export default defineNuxtConfig({
  app: {
    head: {
      charset: 'utf-8',
      // ...
    }
  }
})

package.json (1)

36-36: Nuxt 4 requires a modern Node; consider pinning engines.

To avoid CI/host mismatches, add an engines field reflecting Nuxt 4’s Node requirement.

Example:

{
  "engines": {
    "node": ">=18.20.0 || >=20.10.0"
  }
}

Optionally also pin your package manager (e.g., "packageManager": "[email protected]") if relevant to your setup.

📜 Review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b5681f8 and 626ad06.

⛔ Files ignored due to path filters (7)

• app/assets/images/dark.png is excluded by !**/*.png
• app/assets/images/logo.png is excluded by !**/*.png
• app/assets/images/preview1.png is excluded by !**/*.png
• app/assets/images/preview2.png is excluded by !**/*.png
• app/assets/images/preview3.png is excluded by !**/*.png
• app/assets/images/preview4.png is excluded by !**/*.png
• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• nuxt.config.ts (1 hunks)
• package.json (2 hunks)

🔇 Additional comments (3)

nuxt.config.ts (2)

8-8: ✔ Migration to @nuxt/icon verified — no leftover nuxt-icon usage

• All occurrences of <NuxtIcon> or <nuxt-icon> components have been removed.
• No nuxtIcon: keys remain in any nuxt.config.* file.
• Only the intended @nuxt/icon entries appear in package.json and nuxt.config.ts.
• <Icon> is used throughout (e.g. in pages and shared components), confirming the switch is complete.

---

1-1: ✅ ./app/data import verified for build-time usage
The file app/data/index.ts exists, exports seoData, and contains no runtime-only APIs. The import { seoData } from './app/data' in nuxt.config.ts is safe at build time. No changes needed.

package.json (1)

22-22: Switch to @nuxt/icon in devDependencies LGTM.

Matches the module change in nuxt.config and is the recommended module for Nuxt 4.