docs: add EdgeOne Pages deploy guide - #2372
Conversation
|
@Ibochkarev is attempting to deploy a commit to the Nuxt Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughAdded a deployment documentation page for Nuxt applications on EdgeOne Pages. The page defines hosting metadata, documents the Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This PR adds an EdgeOne Pages deployment guide and supporting image without introducing an actionable merge-blocking risk; it is merge-ready after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
content/deploy/edgeone.md (1)
22-28: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winUse the EdgeOne Makers deploy command.
The current EdgeOne CLI documentation recommends
edgeone makers;edgeone pagesis available only during the legacy transition. Update this example or mark it as the legacy equivalent.Proposed fix
-edgeone pages deploy +edgeone makers deploy🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/deploy/edgeone.md` around lines 22 - 28, Update the EdgeOne deployment example in the documentation to use the current `edgeone makers` deploy command instead of `edgeone pages deploy`. If retaining the existing command, clearly label it as the legacy equivalent and document the Makers command as the recommended path.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/deploy/edgeone.md`:
- Line 6: Update the nitroPreset frontmatter value in the EdgeOne deployment
guide from edgeone to edgeone-pages so it matches the NITRO_PRESET value used
later in the guide.
---
Nitpick comments:
In `@content/deploy/edgeone.md`:
- Around line 22-28: Update the EdgeOne deployment example in the documentation
to use the current `edgeone makers` deploy command instead of `edgeone pages
deploy`. If retaining the existing command, clearly label it as the legacy
equivalent and document the Makers command as the recommended path.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 3bc89803-7bed-4a91-8ff1-32bb227a9233
⛔ Files ignored due to path filters (1)
public/assets/integrations/edgeone.pngis excluded by!**/*.png
📒 Files selected for processing (1)
content/deploy/edgeone.md
9816c43 to
79c202e
Compare
Production bundleComparing
Largest module increases
|
1 participant
🔗 Linked issue
Fixes #2127
📚 Description
EdgeOne Pages has a Nitro preset (
edgeone-pages) but no card on nuxt.com/deploy yet. People looking for Tencent EdgeOne hosting had to dig into Nitro docs alone.I added an EdgeOne Pages deploy guide covering the console flow with
NITRO_PRESET=edgeone-pages, the EdgeOne CLI, and links to the EdgeOne Nuxt guide and Nitro preset docs.