Deno•14mo ago

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

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);

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.

zor•11/20/24, 10:24 AM

may be help

zor•11/20/24, 10:26 AM

If you have any better way to fix this. response it to me.

Zzor If you have any better way to fix this. response it to me.

ZweiEuroOP•11/20/24, 10:36 AM

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•11/20/24, 7:48 PM

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 , which would mean VSCode would just fall back to the normal TypeScript LSP, which we know to be working correctly for this use case.

CCCPatriot Eh, I don't think that's actually solving the problem here. That would just tell...

ZweiEuroOP•11/20/24, 7:57 PM

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

zor•11/23/24, 5:01 PM

Actually, there are other way to fix this error.
You can use the guide from the link below to configuration deno.json file for your vscode project
https://docs.deno.com/runtime/fundamentals/configuration/

Deno

deno.json and package.json

In-depth documentation, guides, and reference materials for building secure, high-performance JavaScript and TypeScript applications with Deno