elements
Start Blog Demos UI Docs Pricing
Elements Manual
  • Getting Started
  • CLI
  • Build
  • Browser
  • Packages
  • TypeScript
  • Elements HTML
  • Assets
  • RPC
  • Router
  • Session
  • Database
  • Migrations
  • LiveTable
  • Channel
  • Jobs
  • Email
  • Payments
  • JSON
  • Async
  • Style
  • UI
  • JSOC
  • Config
  • Tests
  • Logs
  • Deploy
  • Editors
  • Recipes
  • Licenses
  • Issues
  • Changelog
    • 0.31.0
    • 0.30.0
    • 0.29.0
    • 0.28.1
    • 0.28.0
Manual / Changelog/ 0.31.0

0.31.0

elements man changelog/v0-31-0

On This Page

  • Changes
  • Upgrade

elements issue reports a bug, an idea or a question to the Elements team from the terminal, so you and your agent file an issue the moment a problem happens. elements login signs the command line in once. The install adds an Elements skill for your coding agents.

Changes

  • elements issue new, search, show, comment and vote file and read Elements issues from the terminal. An issue is a bug, an idea or a question, with a suggested priority and files you choose to attach. Only the Elements team and the person who attached a file can open it. Full topic: elements man issues.
  • elements login signs the command line in to your Elements account. It opens a page that lists what you are authorizing, and the terminal finishes as soon as you authorize. elements logout ends it.
  • The install adds an Elements skill to the skills folder of each coding agent on the machine: Claude Code, Codex, Gemini CLI, Cursor and Copilot. The skill says what Elements is, how to create an app and where the manual is.
  • The AGENTS.md of a new project is a third of its size. It gives an agent one loop to work in, and each step names the manual page to read.
  • A new project has a .gemini/settings.json, so Gemini CLI reads the project's AGENTS.md.
  • The build checks the installed version of each package against the range this version of elements works with, as error 220017. A package that states which elements or Node.js version it needs is checked the same way, as errors 220018 and 220019.
  • console.log in a test shows in elements logs -service build, one entry per line with the test file it came from.
  • The build server's log service is build, and its file is .elements/logs/build.jsonl. It was project. elements logs -service project still works.
  • elements man database/sql lists the value each Postgres column type returns, a date included.
  • elements man ui/templates/field shows how to reset a form after a successful submit.
  • elements -h shows how to open the manual.
  • Fixed: a query with a sql.raw fragment and a SQL comment containing an apostrophe bound the wrong values to the placeholders after the comment.
  • Fixed: a failed equal in a test printed the same text for both sides when one value had a key set to undefined.
  • Fixed: Object.freeze({ fn: () => ... }) around a converted function was reported as error 230018.
  • Fixed: a build that stopped with error 260056.
  • Fixed: elements create migration -h and the other generators listed options that belong to elements create <app>.

Upgrade

Upgrade @elements/app

The sql.raw fix and the test fix are in @elements/app. In each project:

Terminal
elements install @elements/app -u -json elements build -json

Restart elements start after the install.

Prev ChangelogNext 0.30.0
Product
Manual Pricing Compare
Company
History Contact
Legal
Privacy Policy Acceptable Use Terms License Agreement
© Elements Dev Corporation 2026