-
-
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 settings not respected in fetch link to db.json #52
Labels
bug
Something isn't working
Comments
I'm not sure what is meant with the comment "can be an url" for the public path. |
The problem still exists: clicking on another page leads to fetch the db.json again (and with wrong path this time). |
benjamincanac
pushed a commit
that referenced
this issue
Jun 9, 2020
* use router basepath in client plugin This should fix #52 by building the fetch URI using publicPath and router.base * Apply wished changes * fix: fix linter issues
pi0
pushed a commit
that referenced
this issue
Feb 8, 2022
Co-authored-by: Renovate Bot <bot@renovateapp.com>
pi0
pushed a commit
that referenced
this issue
May 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
@nuxt/content: v1.2.0
nuxt: v2.12.2
Reproduction Link
repo: https://gitlab.com/chris_jung/nuxt-content-pages-poc
page: https://chris_jung.gitlab.io/nuxt-content-pages-poc/
Steps to reproduce
What is Expected?
The about page should render
What is actually happening?
Showing "NetworkError when attempting to fetch resource."
So the page should respect the base.path setting also in the fetch actions that are fetching the "db.json"
While this works for "regular" chunks like "https://chris_jung.gitlab.io/nuxt-content-pages-poc/_nuxt/c7193aa757204530e99b.js", the db.json file is linked as follows: "https://chris_jung.gitlab.io/_nuxt/content/db.json?1590523967052"
The text was updated successfully, but these errors were encountered: