Environment
Add command-line packages to June's sandbox so they are there whenever June runs code for you.
June runs code and command-line tools in its own sandbox. On the Environment page you add packages to it, and June installs them whenever it prepares a sandbox for a request of yours, so a tool you rely on is always there.
The page is not in the app's menus: open Environment directly.
Add a package
pandoc, rather than an install command. It joins the list; this means it is saved, not that installation has succeeded.Check that pandoc is installed in your sandbox and show me its version
Remove a package from the list with the button beside it, and June stops installing it. A sandbox that already has it keeps it.
You do not need to add what the sandbox already comes with, such as git, gh and typst.
If a package is missing
Check the name in the Nix package search, then ask June to check its version in the sandbox. If the name is wrong, remove it and add the correct one. A misspelled package can also prevent packages after it from installing.
Names accept letters, digits, ., _, + and -. If a name contains other characters, the form shows an error. A name starting with . or - may appear in the list but is never installed.
What June does not do
- It does not install from npm, pip or other package managers on this page: only package names from the Nix package collection.
- It does not tell you when a package fails to install. If a tool is missing, check its name in the Nix package search and ask June to check the sandbox.
- It does not install your list for anyone else's requests. In a sandbox you share, a project's or an organization's, June installs the list of whoever asks, and what one person's list installed stays there for everyone.
- It does not run a sandbox in Slack, so the packages are not there.
