You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that deno needs a proper implementation of a html/xml parser.
There have been several issues from years ago discussing this topic (#6794, #5635) and if it should be implemented in the runtime as the DOMParser or as a separate module.
It seems there was an interest in having it be part of the runtime (#6794 (comment)), probably one reason why std does not provide a html/xml parser/stringifier to this day.
For now, the docs point to deno-dom. While this approach kinda works, deno-dom is far from complete and bug-free and a 3rd party mod.
Could this issue be reevaluated from today's standpoint?
The text was updated successfully, but these errors were encountered:
I think that deno needs a proper implementation of a html/xml parser.
There have been several issues from years ago discussing this topic (#6794, #5635) and if it should be implemented in the runtime as the
DOMParser
or as a separate module.It seems there was an interest in having it be part of the runtime (#6794 (comment)), probably one reason why
std
does not provide a html/xml parser/stringifier to this day.For now, the docs point to deno-dom. While this approach kinda works,
deno-dom
is far from complete and bug-free and a 3rd party mod.Could this issue be reevaluated from today's standpoint?
The text was updated successfully, but these errors were encountered: