#Issue using scopes to change a version

6 messages · Page 1 of 1 (latest)

vivid sierra
#

I'm using https://deno.land/x/markdown@v2.0.0/ and I get the following error:

Warning Implicitly using latest version (0.182.0) for https://deno.land/std/encoding/_yaml/loader/loader.ts
error: Module not found "https://deno.land/std/encoding/_yaml/loader/loader.ts".

I added scopes to deno.config, but doesn't seems to work:

"scopes": {
    "https://deno.land/x/markdown": {
      "https://deno.land/std/": "https://deno.land/std@0.179.0/"
    }
}

Am I doing something wrong here?

hearty nest
#

I had the same error some days ago and think that this is because of an issue with dependency paths by the owner of deno.land/x/markdown. I switched to https://deno.land/x/markdown_renderer

vivid sierra
#

It's weird, because he has a simple import:

import { load } from "https://deno.land/std/encoding/_yaml/loader/loader.ts";
hearty nest
#

But that domain does not exist anymore

image.png
#

Which is totally weird given that he changed exactly that import only three weeks ago

image.png
vivid sierra
#

The domain is fine, it's deno.land. Maybe he had a breaking change with std library and changed the path, which now seems once again broken, because the std has changed. I still think there is an issue with scopes mechanism.