Change Request: Refactor rules to use ultrahtml for HTML parsing

[TKDev7]

Environment

ESLint version:
@eslint/markdown version:
Node version:
npm version:
Operating System:

What problem do you want to solve?

We need to refactor rules with HTML logic. Currently, these rules rely on regular expressions for parsing HTML, which leads to frequent bugs (false positives/negatives), security risks like ReDoS, and a high maintenance burden. As decided in issue #483, we'll replace this approach with a more robust solution using the ultrahtml parsing library. This change will make HTML linting more accurate, consistent, and secure.

What do you think is the correct solution?

The solution is to refactor the following rules to use ultrahtml instead of regex:

• no-bare-urls
• no-empty-definitions
• no-html
• no-missing-link-fragments
• no-multiple-h1
• require-alt-text

Participation

• I am willing to submit a pull request for this change.

Additional comments

This is currently blocked on #489.

[lumirlumir]

Thanks for outlining the rules. The rules you mentioned will be refactored as part of the ongoing work on HTML handling logic in #489.

That PR will include a complete refactor of the existing code, including the suggestions you made.

It might take a little while since there are other higher-priority tasks in progress, but I'll do my best to finish it as soon as possible.

---

I’d appreciate hearing the team’s thoughts on how to handle this issue, since it overlaps with #489 and #483. @eslint/eslint-team

[SwetaTanwar]

@TKDev7 Can I take this up since you are already occupied with other issues & PRs?

[lumirlumir]

@SwetaTanwar For your reference, the rules mentioned here will be refactored in #489.

[SwetaTanwar]

@lumirlumir Got it, thanks for the update 👍