Mojo Paketini Ekleme

Installing magic gave you the manager, not the language. Now you add Mojo itself into a project through that toolchain. 📦

With magic, Mojo lives inside a project folder. Each project gets its own pinned version, so different apps never clash.

Start by making a project. The magic init command scaffolds a folder ready to hold Mojo and its dependencies.

Move into the new directory so the next commands run in the right place. This folder is your project root.

Pull Mojo into the project with magic add. This downloads the compiler and standard library as a package the project depends on.

Your dependencies are tracked in a pixi.toml manifest. Adding mojo records it there so the setup is reproducible later.

Alongside the manifest sits a lock file pinning exact versions. It guarantees teammates get the very same toolchain you have.

Activate the project so its tools are on your PATH. Inside a magic shell, the mojo command becomes available to you.

Prefer not to enter a shell? Prefix any command with magic run to use the project's Mojo for just that one command.

Because Mojo lives in the project, deleting the folder removes it cleanly. Nothing is scattered globally across your system.

Commit pixi.toml and the lock file to git. A teammate then runs magic install to recreate the exact same Mojo setup.

Recall the command that pulls Mojo into your project after you create it.

You ran magic init, then magic add mojo, and the package landed in pixi.toml. Enter it with magic shell to use mojo. 🎯