I have come to realize that deno's TypeScript type checking can't be expected to work without net access. (Although I don't have a good ref to explain why: it's just my experience running deno code.)
Currently type checking is performed on app initialization via a command like deno run --check .... But this should not have net permissions, so a TS error is possible due solely to failing to get access to some needed types file or whatever (or so it seems I can't be 100% sure for now).
In any case type checking always seemed fraught with problems given that TS is evolving and now always 100% back-compatible.
So the plan is:
don't do type checking on app init
have a different summon of deno that can do type checking and has net access by default, probably using deno check ...
Make calling that command optional and possibly off by default for privacy's sake.
I have come to realize that deno's TypeScript type checking can't be expected to work without net access. (Although I don't have a good ref to explain why: it's just my experience running deno code.)
Currently type checking is performed on app initialization via a command like
deno run --check .... But this should not have net permissions, so a TS error is possible due solely to failing to get access to some needed types file or whatever (or so it seems I can't be 100% sure for now).In any case type checking always seemed fraught with problems given that TS is evolving and now always 100% back-compatible.
So the plan is:
deno check ...