Skip to content

Multi-Instance Routes Not Working in v3.2.1 #10052

@ojbravo

Description

@ojbravo

Have you read the Contributing Guidelines on issues?

Prerequisites

  • I'm using the latest version of Docusaurus.
  • I have tried the npm run clear or yarn clear command.
  • I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
  • I have tried creating a repro with https://new.docusaurus.io.
  • 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: '/'.

Reproducible demo

https://stackblitz.com/edit/github-cwn3ck?file=package.json

Steps to reproduce

  1. Go to https://stackblitz.com/edit/github-cwn3ck?file=package.json
  2. Notice that @docusaurus/core, @docusaurus/preset-classic, @docusaurus/module-type-aliases, @docusaurus/types are all at v3.1.1 in the package.json
  3. Using the main navigation on the website, click on the Default Instance and Second Instance links. Both pages should appear as expected.
  4. In the package.json file, update @docusaurus/core, @docusaurus/preset-classic, @docusaurus/module-type-aliases, @docusaurus/types to v3.2.1
  5. Run the following commands in the terminal:
  • Ctrl+C
  • yarn clear
  • yarn
  • yarn start
  1. 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.

Your environment

Self-service

  • I'd be willing to fix this bug myself.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugAn error in the Docusaurus core causing instability or issues with its execution

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions