You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my project vue-tsc takes about 70 seconds.
(according to --diagnostics the "Parse time" is the most time consuming task with 51.21s)
I was wondering if this is due some misconfiguration or expensive types, but I couldn't find a way to get details about what takes so long.
While experimenting and deleting parts of my app I noticed that if I delete the "element-plus" folder inside "node_modules", the execution time is 10 times faster.
I have skipLibCheck active and excluded "node_modules" in tsconfig. So I guess it is not checking the "element-plus" folder, but just parses its types.
So my question is: does this sound like a normal behaviour? Or is there any potential to get vue-tsc to run faster, or to debug where it consumes the most time?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In my project vue-tsc takes about 70 seconds.
(according to --diagnostics the "Parse time" is the most time consuming task with 51.21s)
I was wondering if this is due some misconfiguration or expensive types, but I couldn't find a way to get details about what takes so long.
While experimenting and deleting parts of my app I noticed that if I delete the "element-plus" folder inside "node_modules", the execution time is 10 times faster.
I have skipLibCheck active and excluded "node_modules" in tsconfig. So I guess it is not checking the "element-plus" folder, but just parses its types.
So my question is: does this sound like a normal behaviour? Or is there any potential to get vue-tsc to run faster, or to debug where it consumes the most time?
Beta Was this translation helpful? Give feedback.
All reactions