New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document Deno example #232
Comments
I think this is related to the discussion in #214 |
Reopening, since it makes more sense to discuss support for any specific environment in specific issues. |
for Deno users! |
@taisukef thx for providing an example of what needs to be done to switch to modules and support deno. I still think we need to find a way to additionally continue to support ES5. I'm guessing that we could migrate the code like you did but put it into mjs files and add a build/transpilation step to continue to support ES5? |
i typically don’t have any problem with import { DOMParser, XMLSerializer } from "https://esm.sh/@xmldom/xmldom@0.8.2"; (using native deno support would be nice, but the above might be useful for people trying to make this work as‐is. |
Deno supports importing from npm directly now; for example: import { DOMParser, XMLSerializer } from "npm:@xmldom/xmldom@0.8.8"; I’m not sure what the state of TypeScript support is, but as far as JS is concerned, the above works for me. |
That is true and awesome. So it basically boils down to adding an example to the examples folder for documentation purposes. PRs welcome. |
We should investigate what needs to be done to support deno
The text was updated successfully, but these errors were encountered: