-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
Detect external broken links on build #3193
Comments
It will increase build time and I think it makes less sense since external link may become dead after the build. |
Hi, That's an interesting feature but I don't think we should make it part of Docusaurus. This would make the build unstable, slower, dependant of the availability and speed of external link, + as. @anshulrgoyal said they can go offline after the build anyway so you actually prevent nothing. You definitively can add this easily on your own with the package you linked if you really need this, and we wouldn't really do a better job including this in Docusaurus. |
I think that's a fair answer, thanks for taking a look! |
NTS: If I ever figure out how to make |
@adrianmcli it is very easy to create a new remark plugin for it. I have created one for image and one for assets u can take a look. |
Here is my pr for assets check #3096 |
🚀 Feature
Partly inspired by #3048, it would be nice to detect external links in the Markdown docs and signal to the user that they are broken.
Ref projects:
Have you read the Contributing Guidelines on issues?
Yes
Motivation
If you want good docs, you probably don't want broken links.
Pitch
We should signal users if any external links are invalid on build.
A by-pass flag would be helpful because there might be cases broken external links are ok (e.g. pages that anticipate a link to become valid later on).
This additional check would be really helpful. I'm suggesting this feature because I am building a docs site on top of Docusaurus and I found a need for this personally. I was actually going to use
markdown-link-checker
with CI. But if this can be built-in, then it saves a LOT of work.The text was updated successfully, but these errors were encountered: