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
Because it qualifies as "derived state", we do not check in our components.d.ts file into source control. For our typechecking CI actions, it is crucial that all of the components be declared in this file so that all errors can be caught. However, since the file only gets extended / populated when a given component gets compiled by Vite, I am not sure how to properly generate this file from scratch.
One approach that does work and that does hit all components is simply:
vitebuild
But this is quite slow and costly, since it runs an entire build. I'd rather have something that walks the depencency tree like Vite does, and transform Vue components using this plugin, but that's all it does and it also doesn't emit any built files.
Has this been attempted before, or does any of you have suggestions how I might approach something like this? Maybe a build piped to /dev/null? Or is there something more direct this library offers?
The text was updated successfully, but these errors were encountered:
Because it qualifies as "derived state", we do not check in our
components.d.ts
file into source control. For our typechecking CI actions, it is crucial that all of the components be declared in this file so that all errors can be caught. However, since the file only gets extended / populated when a given component gets compiled by Vite, I am not sure how to properly generate this file from scratch.One approach that does work and that does hit all components is simply:
But this is quite slow and costly, since it runs an entire build. I'd rather have something that walks the depencency tree like Vite does, and transform Vue components using this plugin, but that's all it does and it also doesn't emit any built files.
Has this been attempted before, or does any of you have suggestions how I might approach something like this? Maybe a build piped to
/dev/null
? Or is there something more direct this library offers?The text was updated successfully, but these errors were encountered: