Deno•10mo ago

deno-ts throwing fake errors on new Nextjs App. Can't find any similar issue online.

I think this is an issue with TS configuration? I am trying to follow https://docs.deno.com/examples/next_tutorial/, but it doesn't mention any of these errors, such as the fact that you have to run

deno npm:create-next-app@latest

deno npm:create-next-app@latest

with the

--skip-install

--skip-install

flag. I have just created the Nextjs app and run

deno install

deno install

, as well as created the

deno.json

deno.json

deno task dev

deno task dev

works, but there are many errors, such as the fact that I need to write the

import React from "react"

import React from "react"

. This didn't go away when I changed set

"jsx": "react-jsx"

"jsx": "react-jsx"

in tsconfig. I also got the errors below:

TS2786

'Component' cannot be used as a JSX component.

This is usually caused by version mismatches, which doesn't make sense as it is a clean install of nextjs app.

TS2349

Cannot invoke an expression whose type lacks a call signature. Type 'Promise' has no compatible call signatures.

This one I completely don't understand as the signature files look ok, such as below

node_modules/.deno/next@15.0.4/node_modules/next/font/local/index.d.ts

node_modules/.deno/next@15.0.4/node_modules/next/font/local/index.d.ts

export { default } from 'next/dist/compiled/@next/font/dist/local'

marvinh.•3/5/25, 12:08 PM

That sounds like a bug. Can you file an issue here https://github.com/denoland/deno/issues ?

Mmarvinh.That sounds like a bug. Can you file an issue here https://github.com/denoland/d...

ViviOP•3/6/25, 1:06 AM

will do, the first one is a known issue (oct 2024) that needs to be adjusted in the docs though