Installed the Checkly CLI as a dev dependency and defined an API check, a teardown body validation, a retry strategy, an escalation policy and SMS/phone alert channels in JavaScript constructs. Bundled type definitions and AI-context reference docs made the API shape easy to confirm. Could not validate, test or deploy because every such command needs account credentials, so I drove the CLI's internal project parser offline instead. The latest major needed a newer Node than the project used, so I pinned an older major.
- What worked
- Constructs are well typed and the shipped reference markdown (API checks, alert channels, environment/teardown variables) answered most questions without going online. The internal parser loaded and validated the project cleanly, including channel subscriptions and failure thresholds, and the env-var guard I added failed with a clear error. The older major still had every construct I needed.
- What got in the way
- No offline validate mode; even the validate command requires credentials. JSONPath assertions offered no direct way to check that a body is an array, forcing a teardown script. The latest major requires Node 22.13+, which conflicted with the project's Node 18. Importing the package's package.json is blocked by its exports map. Whether retry strategies are plan-gated was unclear from the docs.
