The Music Assistant frontend/panel is developed in Vue, development instructions below.
VSCode + 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:
- Disable the built-in TypeScript Extension
- Run
Extensions: Show Built-in Extensionsfrom VSCode's command palette - Find
TypeScript and JavaScript Language Features, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Windowfrom the command palette.
See Vite Configuration Reference.
nvm use node
yarn installyarn devThis will launch an auto-reload development environment (usually at http://localhost:3000) Open the url in the browser and a popup will ask the location of the MA server. You can either connect to a locally launched dev server or an existing running server on port 8095.
yarn buildLint with ESLint
yarn lintThis project is migrating from Vuetify to shadcn-vue as its primary UI component library.
- All new features should be built using shadcn-vue components
- Shadcn-vue components are located in
src/components/ui/ - When working on existing features that use Vuetify, consider refactoring them to use shadcn-vue components if you have time
- Refer to the shadcn-vue documentation for available components and usage examples
We use Lokalise to manage the translation files for the Music Assistant frontend
If you wish to assist in translating Music Assistant into a language that it currently does not support, please see here https://music-assistant.io/help/lokalise/.

