veltra-vite

Veltra Vite

First determine what you are doing

When you need to first locate in the current project the @veltra/vite、@veltra/desktop, installation artifact, or workspace source code, read references/source-discovery.md
When you need to add or fix the vite.config.ts resolver configuration, confirm dependencies, and the minimal integration method, read references/integration.md
When you need to troubleshoot components not being auto-imported, styles not coming in, inconsistent dev/build behavior, or abnormal child component style mapping, read references/troubleshooting.md
When you need to confirm the resolver's exact contract,importStyle options, and the co-directory style mapping table, read references/resolver-contract.md

Treat @veltra/vite as a consumer-side integration package; do not assume the current environment necessarily has this repository's packages/vite
VeltraDesktopUIResolver() is only responsible for @veltra/desktop component auto-import; it is not responsible for installing dependencies, nor for handling non- U prefixed components
Style side effects are enabled by default; they are only disabled when importStyle: false is explicitly passed
Style side effect paths are fixed to point to @veltra/desktop/components/<dir>/style; do not hand-write src or dist paths in the consuming project
Style resolution in dev and build depends on @veltra/desktop conditional exports; when troubleshooting, first check the consumed package's exports, and do not suspect the resolver itself first

Component implementation,style.ts entry and component directory conventions:veltra-desktop
Sass infrastructure,pkg:@veltra/styles/... and theme runtime:veltra-styles