Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

broken links on build #7679

Closed
6 tasks done
Arhell opened this issue Jun 24, 2022 · 1 comment
Closed
6 tasks done

broken links on build #7679

Arhell opened this issue Jun 24, 2022 · 1 comment
Labels
closed: working as intended This issue is intended behavior, there's no need to take any action.

Comments

@Arhell
Copy link

Arhell commented Jun 24, 2022

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

When checking yarn start locally, everything works, I checked the links.
yarn build throws errors

Provided that docusaurus.config.js has onBrokenLinks: 'throw'
If you remove this value, then everything is fine, but the condition that this value would be.

Reproducible demo

kubevela/kubevela.github.io#771

Steps to reproduce

update https://github.com/kubevela/kubevela.io/pull/771/files
https://github.com/kubevela/kubevela.io/runs/7039961689?check_suite_focus=true

Expected behavior

There should be no errors if the links are not broken

Actual behavior

https://github.com/kubevela/kubevela.io/runs/7039961689?check_suite_focus=true

Your environment

@Arhell Arhell 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 Jun 24, 2022
@Josh-Cena
Copy link
Collaborator

Hi! It's because in the latest version, we will not output slugs with duplicate last segment by default. See #5830. You can fix this by adding explicit slugs to those docs.

@Josh-Cena Josh-Cena closed this as not planned Won't fix, can't repro, duplicate, stale Jun 25, 2022
@Josh-Cena Josh-Cena added closed: working as intended This issue is intended behavior, there's no need to take any action. and removed 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 Jun 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: working as intended This issue is intended behavior, there's no need to take any action.
Projects
None yet
Development

No branches or pull requests

2 participants