Deno picks up code in comment

[jakajancar]

Ran into this error while working on fp-ts:

% cat import-in-comment.ts 
function hello(who: string): string {
  return `hello ${who}`;
}
/**
 * `
 * import { scanLeft } from 'some/path/in/comment.ts'
 */

% deno import-in-comment.ts
Compile file:///Users/jaka/Desktop/import-in-comment.ts
error: Uncaught URIError: relative import path "some/path/in/comment.ts" not prefixed with / or ./ or ../ Imported from "file:///Users/jaka/Desktop/import-in-comment.ts"
► $deno$/errors.ts:35:13
    at constructError ($deno$/errors.ts:35:13)
    at unwrapResponse ($deno$/dispatch_json.ts:41:12)
    at sendSync ($deno$/dispatch_json.ts:70:10)
    at resolveModules ($deno$/compiler_imports.ts:70:10)
    at processImports ($deno$/compiler_imports.ts:172:27)
    at processImports ($deno$/compiler_imports.ts:181:13)

Some rogue regexp somewhere?

[nayeemrmn]

Potential duplicate: #3089. Same TS bug I guess.

[kitsonk]

Duplicate of #3089

It isn't the comment persay... it is the backtick. The TypeScript pre-process parser gets confused. A work around, remove the backtick. If you want JSDoc that works until the issue in TypeScript is resolved, don't use backticks for code, use four spaces indented above the previous paragraph:

function hello(who: string): string {
  return `hello ${who}`;
}
/**
 * Example that works:
 *
 *     import { scanLeft } from 'some/path/in/comment.ts'
 */

[bartlomieju]

Closing in favor of #3089