undom

I tried using this for a unit-test, and ran into some issues with e.g. , which in regular DOM is a NodeList and not just an , which is missing, for example, the , and iterator methods. I can foresee issues as well with e.g. being a plain created by filtering - whereas, in regular DOM, mutating the of the parent that generated the collection, would cause the iterator to reflect those changes. Maybe this is "by design", favoring simplicity over correctness? If so, that isn't clear from the "Project Goals" stated in the README right now - it doesn't seem to imply that this deviates from DOM in terms of more than features. Lacking features is a matter of scope - but incompatibilities probably ought to be designated in the documentation?

Would be cool to have "undom" published on deno.land (https://deno.land/x/undom) so it's easier to import in Deno. Setup guide

This should be enough to allow the library to be used in Deno directly through some “GitHub as CDN” service. (It works fine for me locally.) A next step would be to make the library available directly with the correct MIME type, without such services (through e.g. GitHub pages), or even making the repository available on .