Building, and the tier where a page is a file
Build, look at what the build says, and deploy the tier below the kernel.
Goal
Build the application, read which pages became files and why the rest did not, and serve the result from the tier where the kernel is never invoked.
The build is one command, and its report is the thing worth reading:
1 · Build it
npx weft buildIt prints a line per route — slots, markup bytes, stylesheets — then the L0 section: which pages were resolved at build time and written as files, and for every page that was not, the code and the read that refused it. That list is the performance review of your application, and it is generated rather than requested.
2 · Serve it, and check it
npx weft start # serve the build. No compiler runs
npx weft verify --probe # ask every region what it is serving
npx weft upload --to … # PUT the build to an object store3 · What the build refused, and why
Every page that did not become a file is listed with the read that stopped it. On this shop that is the cart, which reads identity, and the feed, which is somebody else’s. Neither is a fault to fix — the list is the performance review of your application, and it is generated rather than requested.
Four steps are left, and they are the ones that turn a running application into a deployed one: what to test, what to bind, what may live elsewhere, and what may change under you.