chromatix-app

KO | EN

gitlite — search

#javascript #python #hacktoberfest #ai #typescript #llm #machine-learning #deep-learning #macos #java #windows #cli #pytorch #mcp

(★ 86)

The primary Chromatix web app code repository.

chromatix-app 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Chromatix - Web App

Chromatix is a desktop music player for Plex, that transforms your listening experience and makes interacting with your music libraries a joy.

Get started at [https://chromatix.app/](https://chromatix.app/)

# Table of contents

- [1. Introduction](#1-introduction)
- [2. License](#2-license)
- [3. Getting started](#3-getting-started)
- [4. Deployment](#4-deployment)
- [5. Tech stack](#5-tech-stack)
- [6. Code structure](#6-code-structure)
- [7. Husky + Git Commit Hooks](#7-husky--git-commit-hooks)
- [8. Use of AI](#8-use-of-ai)
- [9. Roadmap, feature requests and bug reports](#9-roadmap-feature-requests-and-bug-reports)
- [10. Contributing](#10-contributing)
  - [10.1. Please let me know what you're working on](#101-please-let-me-know-what-youre-working-on)

# 1. Introduction

> [!IMPORTANT]
> Chromatix is a solo side project of mine, so I don't have the time or resources to maintain it as a full-time project. I do my best to keep it running, but please be patient with any issues or delays in updates.
>
> This codebase is partially migrated to TypeScript - new utilities and hooks are written in TypeScript, but legacy components remain as `.jsx`/`.js` and are migrated opportunistically.

# 2. License

At the moment the code is open source for transparency, but not for re-distribution in any form. You’re of course welcome to download, modify and build the code for personal use.

That said, if this repo goes more than 12 months without any commits, take this as advance permission that the code is free to use and distribute without limitation from 12 months after the last commit onwards.

# 3. Getting started

Install with `npm install`

Develop with `npm start`

# 4. Deployment

Deploy a new version to the staging environment with `npm run release:stage`

(Essentially just tags a new beta version and pushes to the `staging` branch)

Deploy to production by running `npm run release:prod`

(Essentially just tags a new version and pushes to the `production` branch)

# 5. Tech stack

This project is built with [Vite](https://vite.dev/) and React 18.

It uses Rematch (Redux) for global state management.

It is hosted on Vercel.

Vercel Analytics is used for some basic usage data and error logging.

Radix UI is used for some components.

Tanstack Virtual is used for virtualisation of long lists of artists, albums and tracks.

The Plex API is entirely undocumented, as far as I can tell, so all Plex API requests are reverse engineered from official Plex clients. They may not be optimised as well as they could be if I had access to official documentation, and include lots of unnecessary data, but they do the job.

All data from the Plex API is transposed into a slightly different format - partly to exclude some data we don’t need, partly to make it a bit easier to understand, and partly because I hope to add other services in future and want to make it easier to switch between them with a consistent data structure.

# 6. Code structure

Folder structure is hopefully fairly self-explanatory, but a few pointers:

Global state can be found in `/src/js/store`. Some state is saved to localStorage so that user preferences are remembered.

Connections to the Plex API can be found in `/src/js/services`.

The audio player is at `/src/js/services/player.native.ts` but playback management is handled in the store, in the `models.player.js` file.

# 7. Husky + Git Commit Hooks

This repo uses [Husky](https://typicode.github.io/husky/) to ensure that certain tasks are run before committing code.

This includes:

1. Running eslint on staged files to check for code quality issues.
2. Running prettier on staged files to check formatting.
3. Running TypeScript type checking.
4. Running knip to check for unused dependencies and exports.
5. Running tests to ensure code correctness.

If any of these fail, the commit will be aborted, and you will need to fix the issues.

You can also run these tasks manually using the following commands:

```bash
npm run lint
npm run prettier
npm run typecheck
npm run knip
npm run test
```

Or run all checks at once (excluding tests) with:

```bash
npm run check
```

# 8. Use of AI

AI is an obviously common but controversial tool in software development right now. After years of building websites and web apps by hand, and over a year of building and maintaining Chromatix manually, I do now use AI coding tools and I want to be transparent about that.

I have no interest in AI slop. All AI-assisted code is manually reviewed before it's committed. AI can be wrong, inconsistent, and confidently incorrect, so I treat it as a tool that needs oversight rather than a source of truth.

In practice, I use it for various tasks throughout the codebase. Agent instruction files are included in this repo, which document project conventions and guide AI tools towards consistent output.

I also use AI-assisted code review, which has been useful for catching minor mistakes and oversights that are easy to miss in a manual review.

I appreciate that some people have strong feelings about AI in open source projects. I respect that, and I try to use it carefully and responsibly.

# 9. Roadmap, feature requests and bug reports

You can find the roadmap at [Featurebase](https://chromatix.featurebase.app/roadmap).

This is also the best place for feature requests and bug reports, as it allows you to vote on features and see what others are requesting.

# 10. Contributing

I’m not particularly looking for contributors, and hadn’t really planned to open source the code base as I’m happy keeping this as a personal side project, but I kept getting requests to open source it for the sake of transparency, so here it is.

## 10.1. Please let me know what you're working on

If you do see something you want to help with, feel free get in touch here on GitHub, on [Reddit](https://www.reddit.com/r/chromatix/), or on [Bluesky](https://bsky.app/profile/chromaticnova.com) with any questions, or to ensure we aren’t working on the same things at once.

> [!IMPORTANT]
> I cant guarantee I’ll merge in any big features or changes, as I still view this largely as a personal project I want to maintain and control myself, so best to check with me before starting anything.

chromatix-app

chromatix-app 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

chromatix-app

chromatix-app 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README