Intellisense not working for typescript react.

I ran this to create a new Vite React project: What I did:

deno run -A npm:create-vite@latest --template react-ts
deno install
deno task dev

deno run -A npm:create-vite@latest --template react-ts
deno install
deno task dev

But the type sensing was wrong, there also was no deno.json so i created one:

{
  "imports": {
    "react": "npm:react@^18.3.1",
    "react-dom": "npm:react-dom@^18.3.1"
},
"compilerOptions": {
    "lib": [
      "dom"
    ],
    "jsx": "react-jsx",
    "jsxImportSource": "react",
    "types": [
      "npm:@types/react",
      "npm:@types/react-dom"
    ]
}}

{
  "imports": {
    "react": "npm:react@^18.3.1",
    "react-dom": "npm:react-dom@^18.3.1"
},
"compilerOptions": {
    "lib": [
      "dom"
    ],
    "jsx": "react-jsx",
    "jsxImportSource": "react",
    "types": [
      "npm:@types/react",
      "npm:@types/react-dom"
    ]
}}

But the type sensing is still wrong, for very simple code like const [count, setCount] = useState<number>(0); VsCode does not detect count or setCount to be of type number, and it complains that useState has no type argument.

4 Replies

zor•22h ago

"Deno.disablePaths" : ["./src"] may be help If you have any better way to fix this. response it to me.

ZweiEuroOP•22h ago

Thanks! That actually fixed it. But why does that help? So reading the settings, it disables deno but leaves denos built in TS analysis running ? Is there some drawback to doing this ?

CCPatriot•12h ago

Eh, I don't think that's actually solving the problem here. That would just tell VSCode to disable the Deno LSP for anything in ./src, which would mean VSCode would just fall back to the normal TypeScript LSP, which we know to be working correctly for this use case.

ZweiEuroOP•12h ago

Yeah I thought so; is there another error with the default setup for that project?