Small reproduction of a problem with processed imports not working correctly with @vitejs/plugin-vue handling of static assets (https://github.com/vitejs/vite-plugin-vue/blob/main/packages/plugin-vue/README.md#asset-url-handling)

Not completely relevant to the reproduced is the multibrand / skin mechanism - env variable VITE_SKIN controls where assets are drawn from, and if a skin is not set or a given asset is not found, then it's looked up in src/shared/assets. There's an assets/image.svg available for a skin1 and skin2, as well as in shared.

• VS Code + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).

TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue types.

If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:

1. Disable the built-in TypeScript Extension
   1. Run Extensions: Show Built-in Extensions from VSCode's command palette
   2. Find TypeScript and JavaScript Language Features, right click and select Disable (Workspace)
2. Reload the VSCode window by running Developer: Reload Window from the command palette.