You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title: Integrate VitePress at a Specific Route within Nuxt Project
Description:
I'm working on a Nuxt project and would like to integrate VitePress to serve documentation at a desired route (e.g., /docs). I'm encountering challenges in configuring and seamlessly embedding VitePress within the existing Nuxt structure.
Key Questions:
How can I set up VitePress to function as a subdirectory/route within the Nuxt application?
What's the recommended way to handle potential conflicts between Nuxt routing and VitePress routing?
Are there any Nuxt-specific configuration considerations to be aware of?
Desired Outcome:
A clear step-by-step integration guide.
Best practices for managing Nuxt and VitePress routing together.
Troubleshooting tips for common issues that might arise.
Additional Context:
Nuxt Version: [Nuxt 3.11.1 with Nitro 2.9.6]
VitePress Version: [vitepress v1.1.0]
Deployment Environment: (Azure App Service - Static Web App)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Title: Integrate VitePress at a Specific Route within Nuxt Project
Description:
I'm working on a Nuxt project and would like to integrate VitePress to serve documentation at a desired route (e.g.,
/docs
). I'm encountering challenges in configuring and seamlessly embedding VitePress within the existing Nuxt structure.Key Questions:
Desired Outcome:
Additional Context:
On local machine both work:
Nuxt: http://localhost:3000/
Vitepress: http://localhost:5173/
** Current Nuxt config: **
** Current azure Github actions pipeline **
Thank you for your assistance!
Beta Was this translation helpful? Give feedback.
All reactions