Bug introduced in 3.9.0: `docusaurus build` replicates baseUrl path as folderStructure

[FelixK39]

Have you read the Contributing Guidelines on issues?

• I have 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

We upgraded our docusaurus version yesterday from 3.8.1 to 3.9.0 which caused a downtime of our documentation page. It appears that whatever path you specify as your baseUrl, will be replicated as folder structure in the /build path.

Reproducible demo

No response

Steps to reproduce

1. Use version 3.9.0
2. Change your builtPath to /whatever/Random/Path
3. run docusaurus build
4. Your files will be created under /build/whatever/Random/Path/*

Expected behavior

Expect that a minor change does not lead to breaking changes.

Actual behavior

Minor version change broke our documentation. We expect that the docusaurus build is not changed in an incompatible way, or if it is it should be stated clearly in the CHANGELOG/RELEASELOG.

Your environment

• Public source code: NA
• Public site URL: NA
• Docusaurus version used: 3.9.0
• Environment name and version (e.g. Chrome 89, Node.js 16.4): NA, also replicable locally

Self-service

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

[slorber]

Thanks for reporting

That seems related to this comment from @travipross: 2febb76#r166543291

I'll see how to get it fixed asap

[slorber]

Sorry for the inconvenience, this is going to be fixed in #11434

Once merged, can you please test a canary release and let me know if it solves your problem?
https://docusaurus.io/community/canary

[FelixK39]

@slorber I updated all @docusaurus/* dependencies to the latest canary version, but the behavior is still the same

[slorber]

@FelixK39 can you try canary 3.9.0-canary-6406?

Maybe you tried too soon and the version you used was from yesterday, not including the fix.

[slorber]

I just tested again that canary on a newly initialized website and it works

Since this fix is quite critical, I'll release the fix asap, but please let me know if you encounter any problem.

[slorber]

Fixed in https://github.com/facebook/docusaurus/releases/tag/v3.9.1

[FelixK39]

Can confirm that the fix is working, thanks!