Skip to content

fix: revert @nuxt/content import to /nitro for layer compatibility#20

Merged
amondnet merged 3 commits intomainfrom
fix/nuxt-content-layer-compatibility
Dec 22, 2025
Merged

fix: revert @nuxt/content import to /nitro for layer compatibility#20
amondnet merged 3 commits intomainfrom
fix/nuxt-content-layer-compatibility

Conversation

@amondnet
Copy link
Copy Markdown
Contributor

@amondnet amondnet commented Dec 22, 2025

Summary

Reverts @nuxt/content/server import back to @nuxt/content/nitro to match Docus pattern and fix Rollup TypeScript parsing errors when the layer is consumed by other projects.

Changes

  • Reverts @nuxt/content/server import back to @nuxt/content/nitro in server routes to maintain compatibility with the layer pattern
  • Fixes Rollup TypeScript parsing error when layer is consumed by other projects
  • Adds experimental.asyncContext flag to nuxt.config.ts for improved context handling
  • Updates compatibilityDate to 2025-07-22 in layer config
  • ESLint formatting fixes (quote style consistency) in UI components (Command, Dialog, Kbd)

Key Changes

The main fix is in packages/layer/server/routes/raw/[...slug].md.get.ts:

- import { queryCollection } from '@nuxt/content/server'
+ import { queryCollection } from '@nuxt/content/nitro'

Test Plan

  • Verify the documentation site builds successfully with bun build
  • Confirm no TypeScript errors in layer package with cd packages/layer && bun typecheck
  • Test that the layer can be consumed by other projects without Rollup errors
  • Verify dev mode works with bun dev

Related Issues

Closes #18 (follow-up to previous compatibility fixes)

@amondnet
fix: ensure @nuxt/content layer compatibility and update deprecated i…
e23c027 
…mports

- Add extendViteConfig import and configure optimizeDeps for @nuxt/content/slugify
- Update deprecated @nuxt/content/nitro import to @nuxt/content/server
- Remove duplicate nuxt-og-image module from modules array
- Fix indentation in modules array for consistency

This ensures the @pleaseai/docs layer works correctly when imported as a dependency in other Nuxt projects.
@amondnet
chore: apply AI code review suggestion for optimizeDeps
0de7342
@amondnet
fix: revert @nuxt/content import to /nitro for layer compatibility
f1e7770 
- Changed import from '@nuxt/content/server' to '@nuxt/content/nitro' in raw route handler
- Matches Docus pattern for proper layer compatibility
- Adds experimental.asyncContext flag to nuxt.config.ts
- Updates compatibilityDate to 2025-07-22
- Applies ESLint formatting fixes (double quotes to single quotes) in UI components
- Fixes indentation in apps/docs/nuxt.config.ts
@gemini-code-assist
Copy link
Copy Markdown

gemini-code-assist bot commented Dec 22, 2025

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 primarily addresses compatibility issues within the Nuxt layer, specifically by reverting a @nuxt/content import path to resolve Rollup TypeScript parsing errors. It also includes updates to the Nuxt configuration for better context handling and future compatibility, alongside general code formatting improvements to maintain consistency.

Highlights

  • Nuxt Content Import Reversion: The import path for @nuxt/content has been reverted from /server to /nitro in server routes to ensure compatibility with the Docus layer pattern and resolve Rollup TypeScript parsing errors.
  • Nuxt Configuration Updates: The nuxt.config.ts file in the layer package now includes an experimental.asyncContext flag for improved context handling and updates the compatibilityDate to '2025-07-22'.
  • Vite OptimizeDeps for Nuxt Content: The Vite configuration has been extended to explicitly include @nuxt/content > slugify in optimizeDeps to prevent build issues when the layer is consumed by other projects.
  • Code Formatting: ESLint formatting rules have been applied across various UI components (Command, Dialog, Kbd) to ensure consistent quote style and improve readability.
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. ↩

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Dec 22, 2025

Quality Gate Passed 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

gemini-code-assist[bot]
gemini-code-assist bot reviewed Dec 22, 2025
View reviewed changes
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 primarily reverts an import in @nuxt/content to use the /nitro subpath for better layer compatibility, fixing Rollup parsing errors. It also introduces several other changes: adding experimental.asyncContext, updating the compatibilityDate, and applying widespread ESLint formatting fixes for quote style consistency. The changes look good, especially the cleanup of the duplicate module in nuxt.config.ts. I have one suggestion regarding a hardcoded value in the new Vite configuration logic, which could improve the reusability of the layer.

@amondnet amondnet self-assigned this Dec 22, 2025
@amondnet amondnet merged commit cb4270b into main Dec 22, 2025
1 of 2 checks passed
@amondnet amondnet deleted the fix/nuxt-content-layer-compatibility branch December 22, 2025 09:02
@pleaeai-bot pleaeai-bot bot mentioned this pull request Dec 22, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@amondnet amondnet

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@amondnet