chore: nuxt and node updated

[hmbanan666]

Summary by CodeRabbit

• Chores
  • Updated package metadata and repository information.
  • Upgraded required Node.js and pnpm versions.
  • Updated dependency versions for several packages to their latest minor or patch releases.

[coderabbitai]

Walkthrough

This update modifies project metadata and dependency requirements. The package.json file has been revised to update repository links, engine requirements, and remove several descriptive fields. The pnpm-workspace.yaml file reflects minor version bumps for several dependencies in the catalog section. No code logic or public API changes are present.

Changes

Cohort / File(s)	Change Summary
Project Metadata & Engine Requirements package.json	Updated repository URL, cleared version, removed description/author/homepage/bugs/keywords, and raised Node.js and pnpm engine versions.
Dependency Version Updates pnpm-workspace.yaml	Incremented versions for @vitejs/plugin-vue, nuxt, nuxt-auth-utils, and nuxt-zod-i18n in the catalog section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇
I nibbled through the metadata fields,
Tidied the links, let new versions yield.
With engines tuned and packages spry,
The garden of code is fresh and high.
No logic changed, just roots and shoots—
Now onward, devs, in your bunny boots!
🌱✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4681e58 and 030d7bc.

📒 Files selected for processing (1)

• package.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update

---

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

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

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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	eslint@​9.32.0

View full report

[coderabbitai]

Actionable comments posted: 3

♻️ Duplicate comments (2)

docker/web-app/Dockerfile (1)

1-1: Same tag-existence concern as the parser image

See previous comment on node:22.18.0-alpine; verify the tag exists or builds will fail.

docker/web-storefront/Dockerfile (1)

1-1: Same tag-existence & digest-pinning concerns

Applies identically to this Dockerfile.

🧹 Nitpick comments (1)

package.json (1)

9-16: Repository URLs lost the .git suffix

Many tooling & badge generators expect the .git suffix. Consider keeping it to avoid CI or changelog issues.

-  "url": "git+https://github.com/nextorders/roll-stack"
+  "url": "git+https://github.com/nextorders/roll-stack.git"

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9b5709f and 2aeeee2.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (5)

• docker/web-app/Dockerfile (1 hunks)
• docker/web-parser/Dockerfile (1 hunks)
• docker/web-storefront/Dockerfile (1 hunks)
• package.json (2 hunks)
• pnpm-workspace.yaml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (1)

pnpm-workspace.yaml (1)

31-56: Lockfile is up to date with bumped versions
Verified that pnpm-lock.yaml now contains nuxt@4.0.2 and nuxt-auth-utils@0.5.22, so no further action is needed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud