Wally packages✎

Packages in the project tree, how a require reaches one, and adding and removing them.

Verified

Wally installs a project's packages into Packages/ from the list in wally.toml. Roswaal reads both: the list shows in the project tree, and a require that goes through Packages/ is followed to the package's code.

In the project tree

wally.toml is under Graph Content, with each package it lists and the version installed. Double-click one to open its code; one not installed yet says so. Packages/ is under Compile Content, in purple, and starts closed.

The Project panel's Files view in a project that uses Wally.

Hover a control or its row to light the other.

wally.tomlWhat the project depends on. Right-click it to add a package.
A packageListed by the name you require it by, with the version installed. Double-click it for its code.
Not installedIn wally.toml with nothing in Packages/ yet. Right-click it to insert its zip.
Packages/What Wally installs, in purple. It starts closed.

How a require reaches a package

wally install writes a short file for each package that requires the real one from Packages/_Index:

luau

-- Packages/Flux.lua, written by Wally
return require(script.Parent._Index["someone_flux@0.2.0"]["flux"])

Roswaal follows it there, and through the package's own project file to its code, so require(ReplicatedStorage.Packages.Flux) hovers with Flux's own functions and comments. A package whose code was copied in over that line is read as the code it is.

Adding a package

Right-click wally.toml:

	What it does
Add from Wally…	Puts the line in `wally.toml` and installs the package, with what it depends on
Insert package zip…	Installs a zip. A Wally package goes where `wally install` puts one; any other module is copied into `Packages/`
Insert GitHub repo…	Copies a repository's module into `Packages/`, found through its project file. In the installed editor

Right-click wally.toml in the project tree, or press and hold it on a touch screen.
Choose Add from Wally….
Type the package as scope/name. Pick a Realm if it is not for both sides.
Press Add. The line goes into wally.toml, then the package installs with what it depends on.
It is listed under wally.toml with the version installed.

Realm puts the line under [dependencies], [server-dependencies] or [dev-dependencies], which install into Packages/, ServerPackages/ and DevPackages/.

Info

Add from Wally asks the registry twice a package, and stops at 16 requests. Nothing is retried.

If a download fails, the line stays in wally.toml and the package shows as not installed. Download its zip, right-click the package and choose Insert its zip….

Removing a package

Remove package…, on a package's menu, lists the files that still require it and asks first. It takes the line out of wally.toml, and the package out of Packages/ with any package only it needed. Code copied in over the package's file is left where it is.

Right-click the package under wally.toml.
Choose Remove package….
It lists the files that still require it. Press Remove to take it out.

Last reviewed 30 September 2026 by @neopolitans