Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSX element type <Component> does not have any construct or call signatures. #1414

Closed
vphilot opened this issue Jun 7, 2022 · 5 comments
Closed

Comments

@vphilot
Copy link

vphilot commented Jun 7, 2022

Seeing this quite a lot after the most recent update - example with routerLink. Any clues on what might be happening?

image

@PickClass
Copy link

#1408

@TheDutchCoder
Copy link

Both those issues are closed but don't seem to actually solve the problem (other than downgrading)

@kingyue737
Copy link
Contributor

image

In vue 2 project, global components explicitly typed have no error now, but for those not defined this bug still exists

@kingyue737
Copy link
Contributor

image

In vue 2 project, global components explicitly typed have no error now, but for those not defined this bug still exists

Oh no, template errors appear again after 5 mins, I didn't touch anything

@innocenzi
Copy link

On a Vue 3 project, setting the following in tsconfig.json does suppress the errors, but makes all components any (although they are all typed via components.d.ts):

"vueCompilerOptions": {
	"experimentalSuppressInvalidJsxElementTypeErrors": true,
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants