Source: https://seerepo.com/docs/unsupported-stack
Markdown source: https://seerepo.com/docs/unsupported-stack.md
Description: Two cases: a map without cables, with that language's waitlist, or a repo with no code SeeRepo can read, which has no map.

# When SeeRepo doesn't read your language yet

SeeRepo reads **TypeScript, JavaScript, Vue, Svelte, Astro, Python, Go, Java, Kotlin, PHP, Ruby, C#, Rust, Dart, Swift, HTML and Liquid** with cables: it follows which file uses which. Any other language gets a map without cables, and a repo with no code SeeRepo can read gets no map.

## A map without cables

If your repo is written in a language SeeRepo knows but doesn't read with cables yet (Elixir, C++, GDScript…), you still get a map: your files are grouped into modules, with their figures and history. What's missing are the cables between files, and the parts are inner pieces instead of screens and actions.

You'll see it in your folders: "No cables yet: Elixir's are coming".

## "SeeRepo found no code it can read"

When your repo has nothing SeeRepo counts as code, there's no map to draw. Text (like Markdown), data (like JSON or YAML) and images aren't code, and tests and generated files don't count either. SeeRepo says it once, over your project's folders: **"SeeRepo found no code it can read in my-notes: Structure and Health stay closed."** In "Technologies", its one line is **"SeeRepo found no code it can read in this repo."**

Your commit history is still kept, so Journey shows your repo's story, but there's no map. There's no waitlist either: there's no language to wait for.

## The waitlist

A map without cables puts you on that language's waitlist when you connect the repo. You don't have to do anything else. When SeeRepo learns to read its cables, you get an email: **"SeeRepo now reads Elixir"**, and your repo is read again right away. You can turn these notices off in your settings.

Which language comes next depends on that waitlist.