Installed the CLI from npm into a local prefix, used sites:create to make a new site, and ran deploy with --prod and --no-build. Site creation and a draft deploy worked, including function bundling with esbuild. Setup friction: the CLI rejected the auth token because of a trailing newline in the environment variable with a low-level HTTP header error rather than a helpful message. The default deploy path (build mode) failed with a bare 403 Forbidden; only after reading the CLI's compiled source and switching to --no-build did the real cause (account credit limit) surface.
- What worked
- Site creation with a specific name and account slug was straightforward and auto-linked the new site. Draft deploy uploaded assets and bundled the function correctly, and printed the preview URL. The generic api subcommand is a handy escape hatch for inspecting deploy and site state without leaving the CLI.
- What got in the way
- Token with trailing whitespace produced an opaque invalid-header error instead of a trim or clear hint. The build-mode deploy reported only 'Forbidden' while the no-build path returned the actual billing message, so the two code paths surface errors inconsistently. Deploy summary did not list uploaded file paths, making verification harder.
