fix: import map with trailing slash

[shian15810]

Fixes https://github.com/axetroy/vscode-deno/issues/141.

[shian15810]

@axetroy I have no authority over this coveralls failing the test. Please help, thanks.

[shian15810]

@axetroy Thanks! Test is ok now.

[shian15810]

Just FYI, I'm experiencing this issue a lot: kulshekhar/ts-jest#1506

Should be fixed in next release of jest, but not yet as for this moment.

ATM, I'm using jest --no-cache to workaround this issue.

[shian15810]

@axetroy Should be ok. This should be final.

[axetroy]

great work & Thx.

[axetroy]

@shian15810 This has land in v3.6.0

[shian15810]

@axetroy Just tested it, no issue! Thank you.

[btrauma8]

i have 3.6.0, but this isn't working for me when trying to setup import maps for local directories.

am i doing something wrong?
image below should show what's going on...

[shian15810]

@btrauma8

I have no problem using absolute and relative path in import_map.json.
However, if I specify the file: protocol, I get the same error like you.

You can try relative path like ./my-lib or absolute path like c:/junk/deno/my-lib.

I think you should raise another issue regarding the extension having problem with file: protocol in import_map.json.

[btrauma8]

ahhhh....
imports: { "my-lib/": "./my-lib/" } worked for both deno and vscode plugin
c:/junk... only worked for vscode plugin, not deno.

for some reason i thought the importmap had to use file: protocol if pointing to local files,
but apparently not. relative offset is nicer anyway, so, thanks!

now i can get back the tsconfig.json baseUrl functionality that i miss

[shian15810]

@btrauma8 I think you definitely should raise an issue about this problem.

In any way, this extension should comply to specs and deno standards.

[btrauma8]

done. https://github.com/axetroy/vscode-deno/issues/146