Deno•3y ago

Worker: TS2304 [ERROR]: Cannot find name 'postMessage'

When type-checking a worker script that uses the global

postMessage()

postMessage()

method,

deno check

deno check

gives a

TS2304 [ERROR]: Cannot find name 'postMessage'

TS2304 [ERROR]: Cannot find name 'postMessage'

error. Is there any workaround?

jcayzacOP•7/14/23, 6:13 AM

deno check

deno check

doesn't seem to accept any argument to specify what context the script executes in (e.g. vs ), nor can it apparently infer it based on file name conventions ()

AapoAlas•7/14/23, 6:47 AM

You'll need to use triple-slash type comment.

jcayzacOP•7/14/23, 6:57 AM

Do you mean and declare

postMessage()

postMessage()

in that file?
Doesn't the comment only works on imports, tho? I'm not importing anything.

jcayzacOP•7/14/23, 6:58 AM

Also, it just occured to me that a global

postMessage()

postMessage()

isn't specific to workers, and exists on the interface too. It's weird that Deno doesn't have it.

AapoAlas•7/14/23, 7:59 AM

No, I meant including (I think) which should maybe have the definitions globally available. Maybe.

jcayzacOP•7/20/23, 5:06 AM

Thanks, it's actually mentioned in the docs and I missed it.
https://deno.land/manual@v1.35.2/advanced/typescript/types#using-triple-slash-directives

Deno

Types and Type Declarations | Manual | Deno

One of the design principles of Deno is no non-standard module resolution. When
TypeScript is type checking a file, it only cares about the types for the file,
and the compiler has a lot of log

jcayzacOP•7/20/23, 5:07 AM

jcayzacOP•7/20/23, 5:08 AM

It would be neat if could be assigned per file pattern, inthe json configuration (so that I could have the default lib everywhere but use for )