Issue using scopes to change a version

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".
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/"
}
}
"scopes": {
"https://deno.land/x/markdown": {
"https://deno.land/std/": "https://deno.land/std@0.179.0/"
}
}
Am I doing something wrong here?
6 Replies
MrKleeblatt
MrKleeblatt2y ago
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
MariusVatasoiu
MariusVatasoiuOP2y ago
It's weird, because he has a simple import:
import { load } from "https://deno.land/std/encoding/_yaml/loader/loader.ts";
import { load } from "https://deno.land/std/encoding/_yaml/loader/loader.ts";
MrKleeblatt
MrKleeblatt2y ago
But that domain does not exist anymore
MrKleeblatt
MrKleeblatt2y ago
Which is totally weird given that he changed exactly that import only three weeks ago
MariusVatasoiu
MariusVatasoiuOP2y ago
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.
MariusVatasoiu
MariusVatasoiuOP2y ago
GitHub
Import map scopes doesn't work as expected · Issue #18626 · denolan...
The scopes option from import_map.json or deno.json doesn't work in the following scenario: // test.js import { Marked } from 'https://deno.land/x/markdown@v2.0.0/mod.ts'; console.log(M...