docusaurus: "Docs markdown link couldn't be resolved" infinite loop on build or start

🐛 Bug Report

I upgraded to 66 recently for our docs site and since we’re doing translations that are in-progress, there are a lot of broken links (because translators copy the english, change the text and keep the markdown - so links and images, etc) which is fine, I don’t want translators to remove links then re-add them later it’ll just get confusing. I have set onBrokenLink to ignore but the warning messages still appear.

The issue is whenever I do a build or run the dev server the console just gets inundated with:

Docs markdown link couldn't be resolved: ...

I thought there were just a lot of links so I left it running for 10 minutes and it’s still printing! It seems to be stuck in an infinite loop as it prints the same thing over and over. It opens the browser but the page never loads.

I’m thinking it’s related to the type of TTY though because on Vercel it builds fine (ignoring the other error) https://vercel.com/openmultiplayer/wiki/4wphzsm3e could it be related to that progress bar graphic that appears in the terminal?

It seems to be TTY related, if I pipe the output to a file then the server starts up fine:

wiki on  master [$✘] via ⬢ v12.18.3 took 2m48s
❯ npm start > logs
Docs markdown link couldn't be resolved: (NPC:StartRecordingPlayback.md) in E:\Work\open.mp\wiki\docs\scripting\callbacks\OnRecordingPlaybackEnd.md for version current
Docs markdown link couldn't be resolved: (NPC:StopRecordingPlayback.md) in E:\Work\open.mp\wiki\docs\scripting\callbacks\OnRecordingPlaybackEnd.md for version current
[BABEL] Note: The code generator has deoptimised the styling of E:\Work\open.mp\wiki\docs\scripting\resources\animations.md as it exceeds the max of 500KB.
Docs markdown link couldn't be resolved: (../resources/weaponskills#skill-levels.md) in E:\Work\open.mp\wiki\docs\scripting\functions\SetPlayerSkillLevel.md for version current
Docs markdown link couldn't be resolved: (../scripting/functions/GetPlayerDrunkLevel.md) in E:\Work\open.mp\wiki\docs\scripting\functions\SetPlayerDrunkLevel.md for version current
Docs markdown link couldn't be resolved: (GetVehicleRotation.md) in E:\Work\open.mp\wiki\docs\scripting\functions\GetVehicleZAngle.md for version current
Docs markdown link couldn't be resolved: (GetVehicleRotation.md) in E:\Work\open.mp\wiki\docs\scripting\functions\GetVehiclePos.md for version current
Docs markdown link couldn't be resolved: (../tutorials/colorfix.md) in E:\Work\open.mp\wiki\docs\scripting\functions\GetPlayerColor.md for version current
Docs markdown link couldn't be resolved: (UpdatePlayer3DTextLabel.md) in E:\Work\open.mp\wiki\docs\scripting\functions\Attach3DTextLabelToVehicle.md for version current
Docs markdown link couldn't be resolved: (UpdatePlayer3DTextLabel.md) in E:\Work\open.mp\wiki\docs\scripting\functions\Attach3DTextLabelToPlayer.md for version current

And it stops printing there, the browser opens as expected and I can browse/edit the site and it reloads live.

Have you read the Contributing Guidelines on issues?

Yes

To Reproduce

I think just having a ton of 404s triggers it, clone this and build it: https://github.com/openmultiplayer/wiki/

Your Environment

Does not occur on Vercel but occurs locally on Windows.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 24

Most upvoted comments

@slorber Thank you very much! I will try to fix the mentioned issues and come back to you if the infinite loop warning still remains 😃