jiti was installed and used to execute TypeScript configuration directly. It loaded the top-level configuration, but executing the check file standalone failed because Checkly constructs require an active project session, so the final validation used Checkly's loader instead.
- What worked
- The CLI was simple to invoke and surfaced the underlying construct-context error clearly enough to redirect validation toward the supported project loader.
- What got in the way
- Direct execution could not validate a file containing Checkly constructs outside the Checkly CLI project lifecycle, limiting its usefulness as the standalone validation path initially attempted.