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
I have read the console error message carefully (if applicable).
Description
Running multi-instance in <= v3.1.1 works flawlessly. Upgrading to >= v3.2.0 breaks the non-default instance and displays a "Page Not Found". This occurs when the default instance has a routeBasePath: '/'.
Notice that @docusaurus/core, @docusaurus/preset-classic, @docusaurus/module-type-aliases, @docusaurus/types are all at v3.1.1 in the package.json
Using the main navigation on the website, click on the Default Instance and Second Instance links. Both pages should appear as expected.
In the package.json file, update @docusaurus/core, @docusaurus/preset-classic, @docusaurus/module-type-aliases, @docusaurus/types to v3.2.1
Run the following commands in the terminal:
Ctrl+C
yarn clear
yarn
yarn start
Using the main navigation on the website, click on the Default Instance and Second Instance links. The Default Instance should appear as expected, but the Second Instance will display a Page Not Found.
Expected behavior
Both instances should work in v3.2.1
Actual behavior
The Default Instance appears as expected, but the Second Instance will display a Page Not Found.
Environment name and version (e.g. Chrome 89, Node.js 16.4): Chrome 123, Node 18
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Mac OS Ventura
Self-service
I'd be willing to fix this bug myself.
The text was updated successfully, but these errors were encountered:
ojbravo
added
bug
An error in the Docusaurus core causing instability or issues with its execution
status: needs triage
This issue has not been triaged by maintainers
labels
Apr 17, 2024
Thanks for the report, agree something weird is going on here.
Surprisingly, if I use baseUrl: "/" instead of /test/ then multi-instance works again.
I recently refactored the code to optimize the DX, and it's possible there's something wrong with how we order the routes in .docusaurus/routes.js (the order probably has changed? need to investigate locally because I can't see it in Stackblitz)
Confirming that this fixed this issue in my project. Looking forward to 3.2.2 to avoid issues with peerDependencies in 3rd party plugins (always end up having to manually edit lockfiles to make canaries work)
Have you read the Contributing Guidelines on issues?
Prerequisites
npm run clear
oryarn clear
command.rm -rf node_modules yarn.lock package-lock.json
and re-installing packages.Description
Running multi-instance in <= v3.1.1 works flawlessly. Upgrading to >= v3.2.0 breaks the non-default instance and displays a "Page Not Found". This occurs when the default instance has a
routeBasePath: '/'
.Reproducible demo
https://stackblitz.com/edit/github-cwn3ck?file=package.json
Steps to reproduce
@docusaurus/core
,@docusaurus/preset-classic
,@docusaurus/module-type-aliases
,@docusaurus/types
are all atv3.1.1
in thepackage.json
Default Instance
andSecond Instance
links. Both pages should appear as expected.package.json
file, update@docusaurus/core
,@docusaurus/preset-classic
,@docusaurus/module-type-aliases
,@docusaurus/types
tov3.2.1
Default Instance
andSecond Instance
links. TheDefault Instance
should appear as expected, but theSecond Instance
will display aPage Not Found
.Expected behavior
Both instances should work in v3.2.1
Actual behavior
The
Default Instance
appears as expected, but theSecond Instance
will display aPage Not Found
.Your environment
Self-service
The text was updated successfully, but these errors were encountered: