A thin layer on top of the regular DOM Document. It was, originally, necessary to "hide" the
differences between the JSDOM and Deno's DOM WASM implementations; higher layers were not supposed to depend on these.
Then deno could handle npm packages like JSDOM natively with version>1.4, but some extra utilities were added to the
class which made it useful on its own right... As these utilities were used in the package,
I follow the wisdom of "ain't broken, don't fix it" :-)
A thin layer on top of the regular DOM Document. It was, originally, necessary to "hide" the differences between the JSDOM and Deno's DOM WASM implementations; higher layers were not supposed to depend on these. Then deno could handle npm packages like JSDOM natively with version>1.4, but some extra utilities were added to the class which made it useful on its own right... As these utilities were used in the package, I follow the wisdom of "ain't broken, don't fix it" :-)