Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Motivation

Our current MDX loader code looks like this:

export default function markdownLoader(
  this: LoaderContext<DocsMarkdownOption>,
  source: string,
): void {
  const fileString = source;
  const callback = this.async();
  const options = this.getOptions();
  return callback(null, linkify(fileString, this.resourcePath, options));
}

The linkify process that turns [link](./xyz.md) to [link](/baseUrl/xyz-pathname) is based on string manipulations and regexes.

As a result, linkify has many edge case bugs related to the unability to properly resolve markdown relative file path links such as [](./relative-path.md)

We should instead do this with a Remark plugin after MDX has parsed the string.

See also:

• fix(utils): make Markdown link replacement much more rigorous #8927 (comment)
• Plugin is unable process resource links (Docusaurus process them anyway) #9041 (comment)
• fix(utils): better handling of code blocks in link replacement #9046
• Docusaurus v3 markdown links don't resolve correctly from index pages during build step when trailingSlash is set to false #9720 (comment)

Self-service

• I'd be willing to do some initial work on this proposal myself.