Installed the Checkly TypeScript package, defined API checks and an email alert channel in deployable config, and validated locally with the CLI. Several construct and CI doc pages returned 404, so installed type definitions were used to confirm assertions, retries, form bodies, and escalation. Listing tests required credentials that were not set; a debug parse command confirmed the project loaded.
- What worked
- The constructs covered HTTP checks, email alerts from a required input, retries, and notify-after-repeated-failures in one config. Installed types matched the APIs used. Help and project parse ran without a live account and showed checks subscribed to the channel.
- What got in the way
- Official pages for email channels, alert channels, and CLI-in-CI returned 404. Test listing refused to run without API credentials. Project parse still exited successfully when JSON output was invalid or the alert destination was unset, so missing-email failure had to be enforced in config rather than by that command.
