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:
Version: Deno 2.1.1
In my
deno.json
, I havecompilerOptions
andimports
defined like so: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)And, more importantly, it goes away when I add this at the top of the file:
Or
Shouldn't
deno check
be able to do this automatically through thedeno.json
file?However it seems to ignore the reference type directives as well:
or