With Typescript shims not working for: this.$dialog, this.$confirm, this.$toast

[Burtsev-Alexey]

Shims are declared in module 'vue' doesnt work with options API, I changed it to be module '@vue/runtime-core' - and it works.

Reproducer

https://stackblitz.com/edit/primevue-4-ts-vite-issue-template-gss6mp?file=src%2FApp.vue

PrimeVue version

4.1.1

Vue version

3.x

Language

TypeScript

Build / Runtime

Vite

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

[mertsincan]

Interesting! Please see this issue; #6199

@sceee Could you please check this issue?

[sceee]

@Burtsev-Alexey I cannot see in your reproducer what is not working.
Also, your reproducer is using an older primevue version (4.0.0-rc.3), please update it first to use the latest version.
Could you then please explain the steps you did to reproduce it?
The Shims should only affect the typescript compile, not runtime.

FYI @mertsincan

[Burtsev-Alexey]

@sceee

The Shims should only affect the typescript compile, not runtime.

Yes, it effects only compilation errors.

Also, your reproducer is using an older primevue version (4.0.0-rc.3), please update it first to use the latest version.

I have used the one that was provided in link when I was creating an issue. I have not realized I need to change version...

I cannot see in your reproducer what is not working.

Because StackBlitz doesnt show syntax (compilation) errors... You need to open project in IDE (I use VSCode)

This is how it looks without fix:

This is how it looks with fix:

[sceee]

Hi @Burtsev-Alexey , I've updated your reproducer to primevue 4.1.1 (and removed the StepperPanel import which is no longer exported) and ran npm run build (which you can also do in stackblitz) - no issues are displayed:
https://stackblitz.com/edit/primevue-4-ts-vite-issue-template-baezk4?file=package.json

According to your screenshots it looks like you are using a different project locally - as the affected component is called Foo.vue.
Probably you have other libraries installed that incorrectly augment vue types creating that issue? See #6199 for details.

[Burtsev-Alexey]

Probably you have other libraries installed that incorrectly augment vue types creating that issue? See #6199 for details.

@sceee This could be the case, Thank you I will try now with clean reproducer and come back with result

[Burtsev-Alexey]

@sceee You are right, I found the "evil", it was https://github.com/imcvampire/vue-axios dependency that is "cleaning up" ComponentCustomProperties

Sorry for inconvenience, issue closed.