Installed the Checkly CLI as a dev dependency and wrote a monitoring-as-code project: an API check with status, response-time and body-content assertions, an email alert channel, retry strategy and an escalation policy that alerts after consecutive failures. The constructs API was typed well enough that I could verify builder signatures, region names and config options directly from the package's type declarations. Every CLI command, including a plain list of checks, required account credentials, so I could not run or deploy the check; I validated the config by calling the package's internal config loader and project parser from a small script instead.
- What worked
- Typed constructs (ApiCheck, EmailAlertChannel, AssertionBuilder, AlertEscalationBuilder, RetryStrategyBuilder, Frequency) made the configuration self-documenting. The internal loader and parser instantiated the constructs, ran validation with a Diagnostics object and synthesized the exact payloads that would be sent, which let me confirm the alert wiring and the hard failure when the notification address env var was unset.
- What got in the way
- No offline validate or dry-run command exists; even listing checks demands an API key and account ID. Getting a synthesized payload without credentials meant reading command source and wiring up undocumented internals, including discovering that validate() needs a Diagnostics argument and that synthesize() on the project is not the way to see per-resource output.
