-
-
Notifications
You must be signed in to change notification settings - Fork 414
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
__VLS_globalComponents
type error
#4747
Comments
I am also facing the same issue after upgrade to 2.1.2, however it works perfect with 2.1.0. I also I experience an higher memory consumption that in some of my linux servers overpassing the maximum memory heap capacity raised by NodeJS. I tested in two different environments: Mac Os Sonoma 14.6.1 (Darwin Kernel Version 23.6.0 aarch64) Linux Debian 12 Bookworm (6.1.0-18-cloud-arm64) |
Could you provide a minimal reproduction? |
@zcf0508 : Can you try if it works with vue-tsc 2.1.0? |
Steps to reproduce
Expected result:
Received result:
Workaround:
Environment My projects has more than 50 components. |
How have you defined your global components? Please post your declaration file here (containing just one component entry), e.g.: import {default as Test} from './Test.vue'
export {}
declare module 'vue' {
export interface GlobalComponents {
Test: typeof Test
}
} |
Are you using |
@KazariEX minimal reproduction WithRefAndWithSlot.vue |
Confirmed. This is because #4644 introduces a large circular reference into the virtual code. |
|
You are right, this is a issue also. |
@davidmatter : Yes I am using the vue-facing-decorator. |
That can explain the increase of memory usage. |
Vue - Official extension or vue-tsc version
2.1.2
VSCode version
1.93.0-insider
Vue version
3.4.21
TypeScript version
5.5.4
System Info
Steps to reproduce
In a large project, the global component type is inferred as
any
.This is the components list:
What is expected?
The
__VLS_globalComponents
type should be inferred correctly.What is actually happening?
In a large project, the global component type is inferred as
any
.Link to minimal reproduction
No response
Any additional comments?
No response
The text was updated successfully, but these errors were encountered: