-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Error: Broken links found!
facing on docusaurus build
#3136
Comments
@bhaskarhc broken links detection is new, and as it's shawn in the error message you can simply disable it if it's annoying to you. However if you feel like it reports broken links while it shouldn't, I'd be interested to have more informations. Do you have a public site, a public repo, a PR migrating your site to alpha.59? If not, can you give us the real file structure of your site, the urls of docs that actually exist, and the navbar.items config content. From the data you gave us, I can't check anything. |
@bhaskarhc this site is not alpha 59, can you provide me the site that produces the broken links Also it would help if I could see the existing site hosted somewhere online From your repo, I see 3 nav items, which one is being reported as broken?
Please give me the non-obfuscated output, I need to see the real content of this error |
By seeing the Failed build logs got that |
@slorber |
@bhaskarhc thanks. I now have proper informations to reproduce this bug: Page But this link is reported as broken:
That's what I needed, and there's definitively something wrong happening here
You can temporarily ignore those broken link errors, did you try this 'onBrokenLinks' setting? |
In my case all links are breaking. |
Hi, I'm also encountering problems with broken link. In my case, it seems that relative path are not resolved properly Here's a snippet of my document.
Generates this error:
It seems that the path are now absolute and not relative. It don't think this is a reporting issue that can be ignored with the brokenLink setting. I have the feeling that the latest version can't handle relative paths. |
Yes I've noticed some strange behavior reported, will try to see where the regression comes from. I think if you reference the docs with the .md extension it will work, but will try to get this fixed asap and publish a new version |
I also noticed a problem with external link references Snippet in my document
Produces:
There's a weird front slash in the external URL. |
I'm feeding more info as this may help with the investigation. For the given url:
It get resolved to |
Yes I think there's a leading / added by mistake in relative links, will check where to remove it. @daniellavoie for me using the .md extension does produce absolute links:
If you don't have this behavior this is surprising. |
I confirm I get the same broken link with and without |
I have a fix ready, but @daniellavoie this is totally unrelated to how links to .md extensions are resolved, this part of the code did not change recently, so please double-check that referencing a md file path work for you (it should). If this does not work, it's a totally different bug to report with the full details |
Will be fixed in next release (probably tomorrow) |
FYI: I cannot find any documentation on the location or signature of the |
https://v2.docusaurus.io/docs/docusaurus.config.js/#optional-fields It takes 4 possible values, as documented |
I stand corrected! I was also able to find this in the original typescript defs, but nice work on the documentation search. |
@slorber is issue fixed version avaliable now ? |
Hi, not yet but I will release in the next hours (unless there's a new important bug reported) |
@viztastic Yes, this is the expected behavior. It was renamed in alpha.59, but it was not stated explicitly in the release notes. |
yes sorry it's not very visible on the changelog (should probably highlight more by editing the changelog next time) but it is in one of the PRs in the breaking changes: #2971 |
🐛 Bug Report
links
withitems
on docusaurus.config.jsdocusaurus build
Build Logs
The text was updated successfully, but these errors were encountered: