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
First of all, my English may not be good, please forgive me.
In the test of [email protected] , multilanguage support worked.
But when I upgraded [email protected], I put the same directory configuration structure into the framework, and when I started it, the page navigation bar didn't display properly.
In debug mode, the parameters associated with the locales cannot be seen.
Maybe I did something wrong, but my configuration item is exactly the same as @0.13.2, which is makes me confused, so I would like to ask if the configuration related to multilingual support has changed, and I suggest you check if there is any error.
Reproduction
npm install vitepress.
npm run dev.
open the page at localhost.
Describe the bug
First of all, my English may not be good, please forgive me.
In the test of
[email protected]
, multilanguage support worked.But when I upgraded
[email protected]
, Iput the same directory configuration structure
into the framework, and when I started it, the page navigation bar didn't display properly.In debug mode, the parameters associated with the locales cannot be seen.
Maybe I did something wrong, but my configuration item is exactly the same as @0.13.2, which is makes me confused, so I would like to ask if the configuration related to multilingual support has changed, and I suggest you check if there is any error.
Reproduction
npm install vitepress.
npm run dev.
open the page at localhost.
Expected behavior
In [email protected], The navigation bar is displayed correctly
With the same configuration in [email protected], the navigation bar is not displayed, as shown in the following picture.
The personal configuration is shown in the following picture
In debug mode, the locale parameter is null
System Info
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: