Build failures in the browser
pliego dev starts even when the initial site compilation fails. Document requests receive a branded HTTP 500 diagnostic page containing the stable code, escaped compiler output, and the next action. Saving a fix rebuilds and reloads the page automatically.
Stable diagnostic codes
A diagnostic code identifies the failing contract, not the wording of one compiler version. Tooling may match the code and exit status; humans receive the message and recovery action.
text
PLG-BLD-001 / BUILD FAILED
The site package did not compile.
error[E0425]: cannot find value `titel` in this scope
NEXT
Correct the reported source error and save the file.HTTP failure surfaces
- 404
- The project's authored /404.html, or a branded framework fallback
- 405
- Method rejected with an Allow header
- 414
- Oversized request target rejected before filesystem resolution
- 500
- Current development build failure or an unreadable document artifact
- 503
- Bounded request queue is full; Retry-After is returned
Recovery workflow
- 01
Read the code
Start with PLG-BLD, PLG-ENV, PLG-ART, or the category shown in the browser.
- 02
Fix the first cause
Compiler output is ordered; later errors may be consequences.
- 03
Save and observe
The watcher rebuilds and the diagnostic page reloads without restarting pliego dev.
- 04
Verify production
Run pliego build and pliego inspect after the development page is green.