Skip to content

Issues: taoqf/node-html-parser

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.

Sign up for GitHub

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

10 Open 193 Closed
10 Open 193 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Benchmark comparison
#286 opened Dec 2, 2024 by garysassano rust
1
Bug when parsing <![CDATA[]]> tag which contains <> (angle brackets)
#263 opened Feb 2, 2024 by navrkald
does it support chrome extension service worker in MV3/V3?
#262 opened Dec 22, 2023 by codeyourwayup
100% cpu while parsing document
#260 opened Dec 12, 2023 by papirosko
6
How can I parse a document with errors in the closing of tags? broken html bug duplicate
#225 opened Oct 18, 2022 by jpolstre
1
It doesn't parse all html documents correctly!!! broken html
#223 opened Oct 11, 2022 by jpolstre
3
Release note / changelog is broken
#196 opened Mar 14, 2022 by j0k3r
2
[Doc] Clarify wrapper behaviour of parse() documentation
#153 opened Sep 18, 2021 by DanKaplanSES
5
[Doc] Document DOM nodes in readme documentation
#110 opened Apr 1, 2021 by KHCode
2
Memory leak needs reproduction
#64 opened Aug 29, 2020 by AnatoliiVorobiov
9
ProTip! Add no:assignee to see everything that’s not assigned.