Use html-parse-stringify2 from npm instead of fetching from github

[Cellule]

Checklist

• only relevant code is changed (make a diff before you submit the PR)
• run tests npm run test
• tests are included
• commit message and code follows the Developer's Certification of Origin

The github version matches the last published version to npm, there's no reason to not use npm directly.
This causes installs of this package to have to hit github on every install which can be slow and unreliable

[socket-security]

New dependency changes detected. Learn more about Socket for GitHub ↗︎

---

👍 No new dependency issues detected in pull request

Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

Pull request alert summary

Issue	Status
Install scripts	✅ 0 issues
Native code	✅ 0 issues
Bin script shell injection	✅ 0 issues
Unresolved require	✅ 0 issues
Invalid package.json	✅ 0 issues
HTTP dependency	✅ 0 issues
Git dependency	✅ 0 issues
Potential typo squat	✅ 0 issues
Known Malware	✅ 0 issues
Telemetry	✅ 0 issues
Protestware/Troll package	✅ 0 issues

---

📊 Modified Dependency Overview:

➕ Added Package	Capability Access	+/- Transitive Count	Publisher
html-parse-stringify2@2.0.1	None	+0	rayd

[adrai]

I don't think they are equal.

[Cellule]

Humm you're right they're not equal.
rayd/html-parse-stringify2@master...locize:html-parse-stringify2:master
But that's also a problem, any reason these changes were not contributed back upstream? At this point unclear if they'd take a patch, it looks pretty unmaintained.
Any idea why those changes were made in the first place?

[Cellule]

rayd/html-parse-stringify2#23
Well this PR was open a long time ago and never merged, I guess this answers my question