-
-
Notifications
You must be signed in to change notification settings - Fork 623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Router.base ignored when fetching content #69
Comments
This doubles #52 |
@campino2k I wasn't sure, that one seems to be concerned only with |
Hey @mkamensky, Could you test if the #78 PR solves your issue? |
@benjamincanac Yes, appears like it does, thanks! |
Actually, I'm not sure, but perhaps it's a different problem: the content is shown fine the first time, but if I reload, this just seems stuck. In the console I see messages like:
If I restart |
@mkamensky Do you have this error on dev mode with universal mode? It should be fixed in the last update of the PR. |
@benjamincanac no, it's SPA mode |
* fix: improve regex to support encoded components * fix: workaround for nuxt-i18n behavior
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Version
@nuxt/content: v1.2.0
nuxt: v2.12.2
I have
router.base
set to/fe/
. It seems that@nuxt/content
ignores this when I callfetch()
in my Vue file. When I usecurl
to call the api explicitly, everything seems fine. I tried settingapiPrefix
tofe/_content
, and then the api is called there, but is actually available at/fe/fe/_content
(Sorry, I didn't manage to operate the codesandbox)
The text was updated successfully, but these errors were encountered: