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
Please run npm install express && node a.js first,This will start a service that provides the current timestamp.
Then run npx nuxi generate && npx serve .output/public/ to launch the webpage
When using nuxt-link-locale,if a Chinese URL appears, it will cause the cache of useFetch to become invalid. That is to say, even if the webpage is statically compiled and deployed using npx nuxi generate, the data interface will still be accessed when the user enters。This has led to cross domain issues in my project。
I have already tried it in a pure nuxt project (excluding nuxt-i18n), and nuxt-link does not have this issue.
In addition, when using stackitz to generate the minimum environment, the simulated webpage behavior is slightly different from my local test. I won't go into detail now. If you encounter any issues that cannot be replicated, I will explain them in detail
Additional context
No response
Logs
The text was updated successfully, but these errors were encountered:
Environment
Please run npm install express && node a.js first,This will start a service that provides the current timestamp.
Then run npx nuxi generate && npx serve .output/public/ to launch the webpage
Reproduction
https://stackblitz.com/edit/bobbiegoede-nuxt-i18n-starter-fbpwznqc?file=pages%2Findex.vue
Describe the bug
When using
nuxt-link-locale
,if a Chinese URL appears, it will cause the cache ofuseFetch
to become invalid. That is to say, even if the webpage is statically compiled and deployed usingnpx nuxi generate
, the data interface will still be accessed when the user enters。This has led to cross domain issues in my project。I have already tried it in a pure nuxt project (excluding nuxt-i18n), and
nuxt-link
does not have this issue.In addition, when using stackitz to generate the minimum environment, the simulated webpage behavior is slightly different from my local test. I won't go into detail now. If you encounter any issues that cannot be replicated, I will explain them in detail
Additional context
No response
Logs
The text was updated successfully, but these errors were encountered: