<p dir="auto">I think that we should try to implement an official module like the <a href="https://github.com/b-fuze/deno-dom">Deno DOM third-party module</a> that includes the <code class="notranslate">DOMParser</code>.  The whole part about Deno is to mirror the Browser APIs, but we don't even have an official DOM Parser in the std.  I think that this should definitely be in the std as it is something that is in every single browser shipped out of the box.  I understand that the <code class="notranslate">deno-dom</code> third party module does include a <code class="notranslate">DOMParser</code>, but there are a couple of issues and if a module were created by Deno, it would be worked on as a community.  The author of the module did amazing at starting the project, but we must have one included with Deno.  Also, it would make Deno viable for scraping which is <strong>very important</strong> for a lot of node users.  Thank you for your time!</p>
<p dir="auto">Similar to other browser globals but recognize this is an ambitious request. If web compatibility is a goal then from my perspective this should be too.</p>
<p dir="auto">Currently there are only a few options for constructing a DOM on the backend. Some folks are using Chromium/Puppeteer but this is really memory intensive and crummy for places where coldstart performance is important (like AWS Lambda). JSDom has some support for doing this but resolving esmodules mixed with Node require is clunky at best. A first class runtime solution on the backend for Web Components would be extremely useful for those of us that want to render as much of the DOM as possible before sending it to the client.</p>
<p dir="auto">I think that's a very large audience and a worthwhile goal. Thanks for considering!</p>