Skip to content

Running deno check twice in a pure Deno project causes many type checking errors due to generated .deno folder in canary #36297

Description

@dsherret
  1. git clone https://github.com/dsherret/gagen
  2. cd gagen
  3. git checkout 871e8b7f5ff687c7adc37a2bb8bab5ed2ee58ec2
  4. deno upgrade canary
  5. deno check - Succeeds
  6. deno check - Fails

Output:

...
Found 150 errors.

error: Type checking failed.

The generated .deno folder does not spark joy and degrades the experience of working with scripts in Deno.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions