'/api/' path should be configurable

[rikzwarthoff]

The problem

In my case i'm already running an API at the /api/'path so this conflicts. Currently the config only allows for editing the base path /api/${options.base}/

Solution

I would make options.baseinclude the '/api/', so the default would be /api/_content/. This should also function in combination with the options.sources

Other solution

Other options would be to have a separate config option for the /api/ part.

[atinux]

What do you mean you are having an API on /api ? You are leveraging a proxy?

[rikzwarthoff]

What do you mean you are having an API on /api ? You are leveraging a proxy?

Yes on the domain where the app will be hosted there is an API running at /api/, different application entirely . This means that /api/_content is unreachable for the Nuxt app. So I want to move the content api to something like /content-api/.

The nuxt target is static by the way

[atinux]

What do you think about this @farnabaz ?

[TheAlexLichter]

I second this idea. Especially when using proxy + target rewrites, api is a very common path. Rewriting the calls to Nuxt content unintentionally leads to issues.

[farnabaz]

We can deprecate base option and introduce new option.

[atinux]

I would anyway recommend to proxy on another route than /api as best practices since Nuxt server/api/ is already matching to /api.

But happy to chance the base option.

[rikzwarthoff]

I agree, i would rather proxy elsewhere, but we may not always have that choice