5. Tools and languages
5.3 Overviews: matrix, relations, extensions, requirements
The overall views of the Tools page: the six systems, who requires whom, the extensions per language and what the PC needs.
In the app: «Tools»
In short
- “Matrix”: where each component can be, on the six systems the kit supports.
- “Relations”: what requires what and with which versions, and the versions the projects ask for.
- “Editor extensions”: which extensions each language receives.
- “PC requirements”: the system components the PC needs.
Matrix
A table with one component per row, split into the same eight kinds as the “All tools” table, and the six systems as columns. Each cell says whether the component can be on that system: ✓ available, ≈ emulated (the x64 version on an ARM64 PC), ↓ pre-installed, ◷ completes at the first start, ✕ not available; a green dot means installed. A click on a cell shows the reason, the version and the “Show this system” button.
Relations
Two tables, recalculated when something changes (or with “Compute the relations again”):
| Table | What it says |
|---|---|
| Relations matrix | For each tool, what it requires, with which versions, and whether it is fine (“yes”, “no: the kit uses …”, “… missing”). |
| Versions the projects ask for | For each project, the version its files ask for, from which file, and the status (“uses …”, “to download: …”), with the “Use …” and “Download and use …” buttons. |
Editor extensions
A read-only table: the extensions as rows, the languages and tools as columns. ● means the extension is on by default in projects with that language, ○ that it is optional; ✓ that it is installed. The languages of your projects are highlighted. Extensions are chosen per project: Editor, terminal and extensions (2.5).
PC requirements
Some components need something from the system: Visual C++ 2015-2026 for PHP, Apache and MongoDB on Windows, WebView2 for the app window, the Windows 11 x64 emulation on ARM64 PCs. Each row says which components need it and whether it is “present”, “missing” or “not needed”.
Under the hood
- The relation rules are in the kit's catalog (tauri/catalog/relations.json); the result in data\app\relations.json.
- Project files the kit reads for the versions:
package.json, .nvmrc, .python-version, pyproject.toml, composer.json, go.mod, global.json, pom.xml, Gemfile, Cargo.tomland others. - The extension catalog (from Open VSX) is tauri/catalog/extensions.json.