\n Organize vals into composable collections. Like folders, but vals can belong to multiple, overlapping\n collections.\n
\n Batch actions on multiple vals (clone, delete, set privacy, add/remove from collections). When a val\n is renamed, detects and offers to update all dependencies with new name, to preserve their imports.\n
Lists global-scoped variables of each val (statically parsed), as a summary.
App can uninstall itself! frontend/server/db’s, leaving no trace.

\n\n

\n Fork this val (it will copy over the necessary vals, redirect to the new app, and delete itself).For\n less magic, fork the{\" \"}\n server and{\" \"}\n frontend vals manually.\n
\n Go to your forked frontend (\n https://www.[yourusername]-mayor.web.val.run\n ) and click the button to log in.\n
\n Sometimes VT gets tripped up on lockfile mismatches. If you're getting an undefined error, go to{\" \"}\n mayor and resave it in place. If it's stuck on the load screen, do the same to{\" \"}\n mayor_server\n

\n\n

\n A top-down, bird’s eye view across all your vals, so we can think and act across them. Basically\n everything but the code editor.\n

\n\n

Has most basic VT functionality, except folders and cron vals (not part of VT API).
\n Reload the app periodically to keep it in sync, especially if you’re making frequent changes via\n val.town editor itself.\n
\n Careful not to delete the app from within itself (will be the first two vals when you first load the\n app).\n