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
{{ message }}
This repository has been archived by the owner on Jan 6, 2024. It is now read-only.
I am learning the monorepo architecture of this library.
I found that components in the ui-kit are resolved to any type.
I found that this could be caused by the exports field in ui-kit's package.json (delete this field and add /dist/ in the path in the resolver.ts will work).
I'm still learning and haven't found a solution yet. I've posed an issue(vitejs/vite-plugin-vue#252) for the moment, but wondered if you have an elegant solution?
The text was updated successfully, but these errors were encountered:
Commonly we do not care about these, because we use unplugin-vue-components to auto change/add the import path in
compile time.
While this generates the type definition file correctly, it doesn't resolve to the vue file correctly.
This leads to missing type definitions at development time, even though the components can be imported.
The solution is that the consumer needs to define the paths alias in tsconfig.json.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am learning the monorepo architecture of this library.
I found that components in the ui-kit are resolved to
any
type.I found that this could be caused by the
exports
field in ui-kit'spackage.json
(delete this field and add/dist/
in the path in theresolver.ts
will work).I'm still learning and haven't found a solution yet. I've posed an issue(vitejs/vite-plugin-vue#252) for the moment, but wondered if you have an elegant solution?
The text was updated successfully, but these errors were encountered: