Replies: 2 comments 1 reply
-
deno seems to not perform typechecking unless explicitly told to: https://docs.deno.com/runtime/fundamentals/typescript/#type-checking i just tried setting this up, but deno seems to fail type checking even when tsc succeeds
I have seen similar errors when |
Beta Was this translation helpful? Give feedback.
1 reply
-
Just an FYI for all you deno heads out there, this is a bug with deno check -- the lsp should work correctly though -- see denoland/deno#28370 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I'm trying to start a new project using deno & tanstack router, however I am hitting my first bump along the road: I'm unable to get type-safety to work with my routes & Links.
For example:
Having the following file-structure (generated from the scaffold):
Running
deno task dev
(deno run -A --node-modules-dir=auto npm:vite
) generates therouteTree.gen.ts
as expected, starts the application just fine, and navigation works.However my problem is that if I make the following change to
__root.tsx
Deno does not complain about the incorrect type, although I would expect it to recognize that "inexistent" is not a valid route, as it does when using node with tsconfig, yarn etc.
Is this a problem of my setup with deno? For example I was looking around and found this, which makes me wonder if I should be adding extra configuration to my
tsr.config.json
Or is this some kind of incompatibility of deno with some typescript used here?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions