deno run --no-check=remote / deno check --remote does not report remote errors if a local check was already performed successfully

[lucacasonato]

// https://example.com/test.ts
export const foo: string = 123;

// file:///main.ts
import { foo } from "https://example.com/test.ts";

# Check with default options
$ deno check /main.ts
Check file:///main.ts
$ echo $status
0

# Check with --remote
$ deno check --remote /main.ts
Check file:///main.ts
$ echo $status
0
# This should have errored!


# It does error when you wipe your $DENO_DIR
$ rm -rf $DENO_DIR
$ deno check --remote /main.ts
Check file:///main.ts
error: TS2322 [ERROR]: Type 'number' is not assignable to type 'string'.
export const foo: string = 123;
             ~~~
    at https://example.com/test.ts:1:14
$ echo $status
1

[dsherret]

We could use the "check" value to bust the emit cache. For deno check, ideally we wouldn't emit though (but still use the cache to more determine if type checking is ok as it saves a lot of time)