Justin Chase

The easiest possible fix for now may just be to put a link on the main README.md to tell Deno users to use https://esm.sh/yaml instead of deno.land, because it seems...

Since I had to re-read this and figure it out again, I just want to leave a note here about the actual solution. Perhaps something like below would be a...

Or actually pulling from esm.sh seems to have problems with the latest version of Deno so an alternative is this: ```ts import { parse, stringify, } from "https://deno.land/[email protected]/encoding/yaml.ts"; export const...

I would agree with the previous comment, what's published to deno.land/x I would expect to work with Deno as a Deno compatible module.