Skip to content

fix: move @nuxtjs/robots and nuxt-llms to dependencies#23

Merged
amondnet merged 4 commits intomainfrom
fix/move-runtime-deps
Dec 22, 2025
Merged

fix: move @nuxtjs/robots and nuxt-llms to dependencies#23
amondnet merged 4 commits intomainfrom
fix/move-runtime-deps

Conversation

@amondnet
Copy link
Copy Markdown
Contributor

Summary

  • Move @nuxtjs/robots and nuxt-llms from devDependencies to dependencies
  • These packages are required at runtime for the documentation layer, not just for development
  • Ensures proper installation for consumers of the layer package

Test plan

  • Package.json updated correctly
  • Commit follows conventional commit format
  • No breaking changes to existing functionality

These packages are required at runtime for the documentation layer,
not just for development. Moving them from devDependencies to
dependencies ensures they are properly installed for consumers.
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @amondnet, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request rectifies an oversight in dependency classification by moving two critical packages, @nuxtjs/robots and nuxt-llms, from development-only to production dependencies. This ensures the documentation layer functions correctly in deployed environments and that all necessary components are properly installed for consumers of the layer package.

Highlights

  • Dependency Management: The packages @nuxtjs/robots and nuxt-llms have been reclassified and moved from devDependencies to dependencies within the packages/layer/package.json file.
  • Runtime Requirement: This change addresses the fact that these packages are crucial for the documentation layer's functionality at runtime, not just during development.
  • Consumer Installation: By promoting these to dependencies, the pull request ensures that any project consuming this layer package will automatically install these necessary runtime components.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request correctly moves @nuxtjs/robots and nuxt-llms from devDependencies to dependencies. This is an important fix, as these modules are required at runtime for the documentation layer to function correctly for consumers of the package. The change is well-described and justified. I have one minor suggestion to improve the maintainability of the package.json file.

Runtime dependency needed by consumers extending this layer.
@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Dec 22, 2025

Deploying docs-please with  Cloudflare Pages  Cloudflare Pages

Latest commit: 8c9a593
Status:⚡️  Build in progress...

View logs

@amondnet amondnet self-assigned this Dec 22, 2025
- Use explicit v-bind syntax for title and class props
- Remove unused props variable in UButton
@amondnet amondnet merged commit cc1453a into main Dec 22, 2025
1 check was pending
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant