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
The Packages heading lists each package by realm, Shared, Server and Dev, each realm the folder Wally installs it into. A package shows the version installed, and +1 dependency opens what Wally installed with it. Code put in Packages/ from a zip or GitHub is vendored, and one in wally.toml not installed yet is not installed, with Install on its menu. Double-click a package to open its code.
How a require reaches a package
wally install writes a short file for each package that requires the real one from Packages/_Index:
-- Packages/Flux.lua, written by Wally return require(script.Parent._Index["[email protected]"]["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
Press Add on the Packages heading, or choose Add package… on a package's menu. Add a package takes it from one of three sources:
| Source | What it does |
|---|---|
| From Wally | Puts the line in wally.toml and installs the package, with what it depends on |
| Zip | Installs a zip. A Wally package goes where wally install puts one; any other module is vendored into Packages/ |
| GitHub | Vendors a repository's module into Packages/, found through its project file. In the installed editor |
- Press Add on the Packages heading in the project tree.
- Type the package as
scope/name. Pick a Realm if it is not for both sides; under it, the window says where the realm lands in Studio. - Press Add.
- If the registry has more than one version, pick one. The newest is picked already; an older one is pinned to exactly that version.
- Press Add. The line goes into
wally.toml, then the package installs with what it depends on. - It is listed under Packages with the version installed.
Realm puts the line under [dependencies], [server-dependencies] or [dev-dependencies], which install into Packages/, ServerPackages/ and DevPackages/.
Info
If a download fails, the line stays in wally.toml and the package shows as not installed. Right-click it and choose Install to try again, or download its zip 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. A vendored package that wally.toml never listed is deleted.
- Right-click the package under Packages.
- Choose Remove package….
- It lists the files that still require it. Press Remove to take it out.
Last reviewed 30 September 2026 by @neopolitans