Fix exported DOM Element instanceof checks

[sjh9714]

Summary

Fixes instanceof checks for DOM elements passed to the replace callback.

What changed

• Added a regression test for exported Element instances in replace.
• Normalized parser-created DOM element prototypes to the Element class exported by this package.

Why

html-dom-parser can create DOM element instances whose class reference differs from the Element class exported by html-react-parser. That breaks documented checks like domNode instanceof Element.

Testing

• npm run prepublishOnly
• npm run test:esm
• npm run test:browser

Fixes#2198

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (f7e66d8) to head (fe88b54).

Additional details and impacted files

@@ Coverage Diff @@## master #2243 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 4 4 Lines 127 136 +9 Branches 48 52 +4 =========================================
+ Hits 127 136 +9 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sjh9714]

Thanks, I took another pass at this. I moved the normalization into domToReact, which also addresses your earlier question about keeping this out of index.ts, and the generated root declarations are back to the direct export { Comment, Element, ProcessingInstruction, Text } from 'domhandler' form.

I also added regression coverage for DOM node references exposed in replace (children and next) so the callback does not only work for the current node.

Local checks run:

• npm run prepublishOnly
• npm run test:esm
• npm run test:browser
• git diff --check

The new GitHub Actions runs for commit b9e8a92 are currently showing action_required with no jobs, so I cannot see the updated type-lint result until the workflows are approved/run.

[remarkablemark]

Thanks for the update! Let me know if you see this GitHub Action workflow run.

[sjh9714]

I can see the workflow run now. The b9e8a92 lint job failed at the same @arethetypeswrong/cli --pack step with Cannot read properties of undefined (reading 'filename'); build, commitlint, size, tests, and Codecov passed.\n\nI pushed fe88b54 with a narrower change: only Element nodes are normalized, and the PR title/body now match that scope. Local checks run after the update:\n\n- npm run prepublishOnly\n- npm run test:esm\n- npm run test:browser\n- git diff --check\n\nI also tried npx @arethetypeswrong/cli --pack -f json locally, but it exits with the same internal filename error before producing JSON. The new GitHub Actions runs for fe88b54 are currently action_required, so I cannot see the updated job logs until they are approved/run.

[remarkablemark]

@jinhyuk9714 I think the error might be due to something else. I'll go ahead and merge this PR

Update: the error is unrelated to your changes and is coming from arethetypeswrong/arethetypeswrong.github.io#258

[remarkablemark]

Release:

• chore(master): release 6.1.1 #2244 (comment)