Skip to content
RESONON

Fix Install and Project Problems

Find the message or the symptom, then work through the fix. Quoted blocks are what resonon prints.

No project

Section titled “No project”

No resonon.toml in /Users/you/scratch or above it. A piece belongs to a project — start one with resonon new <name>, or resonon init in the folder it should live in.

Resonon finds a piece’s project by walking up from the file — not from the folder you are in — to a resonon.toml. The editor, resonon run and the project commands all need one.

  1. Save the file inside a project folder, or
  2. make one around it: resonon init in the folder it should live in, or resonon new <name> for a new folder.

The project needs another resonon version

Section titled “The project needs another resonon version”

Error: this project needs Resonon 0.12.0, but 0.11.0 is running.

The project’s resonon.toml pins a newer minor version than the one running. The line after the error says which fix applies:

  1. Install with: resonon version install 0.12.0 — that version is not installed. Run the command.
  2. Resonon 0.12.1 is installed: run the project through the `resonon` launcher, which picks it. — it is installed, but the binary was started directly, by its path, so the launcher did not choose it. Run resonon.
  3. A project pinned to an older version runs, with a warning.

In a live session the message says this server runs …: the server runs one version. Restart the server from that project — the editor offers it.

A module is not found

Section titled “A module is not found”

Module ‘drum-kits’ not found. Searched: …

The list names every folder that was searched, and why each one was.

  1. Check the package is installed: resonon pkg list. In a cloned project, run resonon install.
  2. use the repository name, not the kit name from its kit.toml.
  3. A hyphen cannot be part of a name, so use "drum-kits" binds drum_kits.

An installed package has nothing in it

Section titled “An installed package has nothing in it”

Installed ‘my-pkg’ to …/dependencies/my-pkg (warning: no lib.non or kits/ found)

The repository is not laid out as a package. Code must be at src/lib.non; kits must be folders under kits/. See Publish a Package.

A new feature seems missing after an upgrade

Section titled “A new feature seems missing after an upgrade”

The engine runs in the server, not in the editor. Upgrading resonon does not change a server that is already running, and VSCode stays connected to it — so a feature from the new version looks like it does nothing.

  1. Stop the server (RESONON: Stop Server) and run a line again, so that a new one starts.
  2. Reload the VSCode window (Developer: Reload Window), so that the extension and the language server restart too.
  3. Check which resonon you run: resonon --version and which resonon.

resonon is not found

Section titled “resonon is not found”
  1. Check the install: resonon --version.
  2. The installer links resonon into /usr/local/bin. Check that /usr/local/bin is on your PATH.
  3. For a build from source, see Build Resonon from Source.
Section titled “Related”