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
Is your feature request related to a problem? Please describe
In the previous major version (nuxt-content@2), I was able to specify api.baseUrl in nuxt.config.ts. This option was essential for me because my Nuxt application is served from a non-root directory. I had api.baseUrl = '_nuxt/content' configured in my nuxt.config.ts.
After migrating to nuxt-content@3, I encountered an issue where requests to /api/content return a 404 error. This happens because building the app creates an api/content directory in .output, which is located next to my _nuxt directory. Unfortunately, I cannot change the non-standard path for my application.
Describe the solution you'd like
Adding the ability to specify baseUrl for api.
Describe alternatives you've considered
Sorry, didn't find any solutions
Additional context
A screenshot is probably not necessary for this feature request.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
In the previous major version (
nuxt-content@2
), I was able to specifyapi.baseUrl
innuxt.config.ts
. This option was essential for me because my Nuxt application is served from a non-root directory. I hadapi.baseUrl = '_nuxt/content'
configured in mynuxt.config.ts
.After migrating to
nuxt-content@3
, I encountered an issue where requests to/api/content
return a 404 error. This happens because building the app creates anapi/content
directory in.output
, which is located next to my_nuxt
directory. Unfortunately, I cannot change the non-standard path for my application.Describe the solution you'd like
Adding the ability to specify
baseUrl
for api.Describe alternatives you've considered
Sorry, didn't find any solutions
Additional context
A screenshot is probably not necessary for this feature request.
The text was updated successfully, but these errors were encountered: