0.12.x✎

The project shell, and Luau you can read.

0.12.x2026-09-06

FeatureChangeBugfix

The project shell, and Luau you can read.

Releases

  1. 0.12.1The toolbar says what each control acts on.New2026-09-06
  2. 0.12.0The project shell, and Luau you can read.New2026-09-06

Warning

Worth knowing before you upgrade.
  • 0.12.0A .luau file is read-only in Roswaal, and that is deliberate. An editable pane would need a save path, a story for conflicting with the file watcher, and an answer for what happens when a compile overwrites what you typed. Handing the file to the editor you already use is a better answer than a second-rate one built in here.

Added

  • 0.12.0Recent projects on the opening screen, and one button that says the right thing: the path is checked before it is opened, so a Roswaal project offers Open, a plain directory offers Initialise, and a typo is reported as a typo.
  • 0.12.0A .luau file opens in a read-only code view with the editor's own highlighting and line numbers, rather than as unstyled text. It says whether Roswaal wrote the file or you did, because that changes what to do with it.
  • 0.12.0Open in VS Code on a hand-written file, and Open the graph on a generated one — both dead ends before.

Changed

  • 0.12.1The top bar is two rows now, split by what a control acts on. Everything on the first is about the project — Refresh, New graph, New map, the compile mode, Compile project, Docs. Everything on the second is about the document you have open: its name, its script class, strict, the tools that only mean anything while it is open, and Compile script.
  • 0.12.1The document row is absent when nothing is open, so the empty editor is one clean bar rather than twelve controls that mostly do not apply.

Fixed

  • 0.12.0Pointing the daemon at another project no longer writes your open graph into it. Every request that writes now carries the project it believes is open, and the daemon refuses a mismatch instead of obeying it. An editor tab is also told when the daemon moves, and closes what it was holding rather than saving it somewhere it does not belong.
  • 0.12.0A dropdown's list opened in the wrong colours — pale text on a pale background until you hovered a row. Giving a select's options their colours explicitly settles it; the browser was choosing them, and choosing badly.