Issue using scopes to change a version
I'm using
https://deno.land/x/markdown@v2.0.0/
and I get the following error:
I added scopes
to deno.config, but doesn't seems to work:
Am I doing something wrong here?6 Replies
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_rendererIt's weird, because he has a simple import:
But that domain does not exist anymore

Which is totally weird given that he changed exactly that import only three weeks 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.
I opened an issue
https://github.com/denoland/deno/issues/18626
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...