Links validation failures after updating to 2.0.0-alpha.61

🐛 Bug Report

We are in the process of migrating Litho UI Framework website to Docusaurus v2. After updating Docusaurus setup to alpha.61 we started getting weird behaviour of not seeing the content of static/javadoc folder on the website and prod build started to fail on links validation step.

Have you read the Contributing Guidelines on issues?

Yep

To Reproduce

Validation errors:

1. Check out this PR: https://github.com/facebook/litho/pull/692
2. Go to website folder and run yarn run build for links validation to kick in
3. See lots of validation errors for /javadoc/... links

Navigation failures:

1. Check out the same PR: https://github.com/facebook/litho/pull/692
2. Go to website folder and run yarn run start to access website locally
3. Open website URL and click to “API” item in the right part of the header
4. You’ll see 404 error for the link http://localhost:3000/javadoc/
5. Update the page with Cmd+R/Ctrl+R and you’ll see the correct API Javadocs page

Expected behavior

No validation errors on build and /javadocs/... links navigation working without reloads.

Actual Behavior

Validation errors:

Console log screenshot

Navigation failures: Video in Dropbox

Your Environment

• Docusaurus version used: 2.0.0-alpha.61
• Environment: Chrome 84.0.4147.125 (Official Build) (64-bit), Node.js 14.6.0):
• Operating system: MacOS 10.15.5

Reproducible Demo

• PR and repo: https://github.com/facebook/litho/pull/692
• website content folder: https://github.com/facebook/litho/tree/master/website
• static/javadoc folder: https://github.com/facebook/litho/tree/master/website/static/javadoc

Steps are present in “To Reproduce” section.

[slorber]

Hi,

The escape hatch is mostly for sites that use a baseurl like /myWebsiteBaseUrl and yet they want to link to some page that is “outside” of the baseurl. If the content is in /static/javadoc, we should prevent the broken link checker to report /javadoc as a broken link. As this system is new, I didn’t think about that case 😃 And yes images go through a different path, using webpack’s file-loader system.

So, I’d that we’ll fix this soon, in the meantime you can ignore the broken link errors (or at least not throw) and re-enable later.

In the message above we talk about validation solely. Does that escape-hatch also help with link not being loaded in the browser at first and succeeding only after additional reload?

I have no idea what you are talking about 🤪

[colriot]

I’ve answered in https://github.com/facebook/docusaurus/issues/3309#issuecomment-678249433, to keep navigation discussion in its own issue.