<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>
<p dir="auto"><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/MarkTiedemann/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/MarkTiedemann">@MarkTiedemann</a> I was wondering if the jsdom port is still happening? I see it was never merged: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="470718682" data-permission-text="Title is private" data-url="https://github.com/denoland/deno_std/issues/542" data-hovercard-type="pull_request" data-hovercard-url="/denoland/deno_std/pull/542/hovercard" href="https://github.com/denoland/deno_std/pull/542">denoland/deno_std#542</a></p>
<p dir="auto">It would be amazing to be able to test code for the browser in Deno 1.0. Thanks!</p>