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
Currently, when using vue-component-meta checkers, once the checker has been initialized, any request to a component metas will return the data for the component at the state it was when the checker has been created.
Including the fact that the checker can take a pretty long time to be initialized, that makes vue-component-meta impossible to add in a toolchain with HMR.
I'm not sure if this is a limitation of embedding a TS language server, what I would imagine is that any request to a file path metas would return the metas for the actual content of the file, and not a cached one.
The text was updated successfully, but these errors were encountered:
Follow up of: nuxtlabs/nuxt-component-meta#43
Currently, when using
vue-component-meta
checkers, once the checker has been initialized, any request to a component metas will return the data for the component at the state it was when the checker has been created.Including the fact that the checker can take a pretty long time to be initialized, that makes vue-component-meta impossible to add in a toolchain with HMR.
I'm not sure if this is a limitation of embedding a TS language server, what I would imagine is that any request to a file path metas would return the metas for the actual content of the file, and not a cached one.
The text was updated successfully, but these errors were encountered: