`deno check` ignores `compilerOptions.types` in `deno.json`

[skeithtan]

Version: Deno 2.1.1

In my deno.json, I have compilerOptions and imports defined like so:

{
  "compilerOptions": {
    "types": ["@testing-library/jest-dom"]
  },
  "imports": {
    "@testing-library/jest-dom": "npm:@testing-library/jest-dom@^6.6.3",
  }
}

And I run deno check to check the entire source with a path to the json file like so: deno check --config ./deno.json ./src/.

But when I run that, it gives me all the errors I expect to be resolved by the types option:
(These are functions extended by Testing Library. In Node they would be fixed through tsconfig.json)

TS2339 [ERROR]: Property 'toBeInTheDocument' does not exist on type 'Assertion<HTMLElement>'.
    expect(getByText(/diagnostic/i)).toBeInTheDocument();
                                     ~~~~~~~~~~~~~~~~~

And, more importantly, it goes away when I add this at the top of the file:

// @ts-types="@testing-library/jest-dom"

Or

// @deno-types="@testing-library/jest-dom"

Shouldn't deno check be able to do this automatically through the deno.json file?

However it seems to ignore the reference type directives as well:

/// <reference types="@testing-library/jest-dom" />

or

/// <reference types="@testing-library/jest-dom/types/matchers.d.ts" />

[Mqxx]

compilerOptions.types seems to really buggy at the moment... #23007

[nayeemrmn]

@skeithtan Can you give some code to reproduce with, maybe a small file in the project?

[Mqxx]

@nayeemrmn You can try this one: #23007 (comment)

[kuchta]

I'm encountering this issue in the context of #26224. I've already tried everything from deno.json:compilerOptions.types, references and even @ts-types, @deno-types but nothing works.

Basic example:

• deno.jsonc

{
	"tasks": {
		"check": "deno check src/**/*.ts src/**/*.tsx"
	},
	"compilerOptions": {
		"jsx": "react-jsx",
		"lib": [ "ESNext", "DOM", "DOM.Iterable" ],
		"types": [ "node", "vite/client" ]
	}
} 

• app.tsx

/// <reference types="vite/client" />
// @ts-types="vite/client"
// @deno-types="vite/client"

import { createRoot } from 'react-dom/client'
import { BrowserRouter } from 'react-router-dom'

createRoot(document.getElementById('root')!).render(
	<BrowserRouter basename={import.meta.env.BASE_URL}>
	</BrowserRouter>
)

• Output:

error: TS2339 [ERROR]: Property 'env' does not exist on type 'ImportMeta'.
        <BrowserRouter basename={import.meta.env.BASE_URL}>

tsc works flawlessly with whatever though...

This is probably one of the most common use case in front-end projects so even though it's not a runtime error it's quite annoying..

[nayeemrmn]

Fixed by #27631.

[nathanwhit]

This is a separate issue from the wildcard imports (though I'm also working on fixing this)