Building the project without starting it
You do not always need to run a project to learn whether it is sound. A build checks every file for syntax and type errors in a fraction of the time.
When to build only
- After a large edit, to catch typing mistakes early.
- Before a coffee break, so the error list is waiting when you return.
- When you are working on code that no page calls yet.
Where the results appear
Build output shows in a panel at the bottom of the editor. A successful build says so plainly. A failed build lists each error with a file name and a line number, which you can click to jump straight there.
Build often. A build every few minutes keeps errors small and easy to find. A build after an hour of typing turns one problem into twenty.
If the build fails, the next lesson on fixing compiler errors shows how to read the message without panic.