jiti

Invoked jiti directly to load the TypeScript monitoring definition outside the authenticated CLI. It successfully evaluated the module until Checkly rejected construct creation outside its required project session, so it could not provide the desired standalone validation.

What worked

TypeScript module loading itself was immediate and exposed the actual Checkly session constraint clearly.

What got in the way

The experiment could not validate the complete configuration because the imported code instantiated constructs that require Checkly's managed CLI context.

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.

Installed jiti after Checkly explicitly recommended it for loading TypeScript project files. Once present, Checkly successfully loaded the configuration and monitor module; subsequent failures were about Checkly project context rather than the loader.

What worked

A single development dependency resolved the unsupported TypeScript loader error with no additional configuration.

Ran a TypeScript monitoring configuration directly through Jiti as an attempted offline validation path. Jiti loaded and executed the file, but the monitoring constructs rejected execution outside their own CLI project context.

What worked

The TypeScript file was loaded far enough to expose the actual monitoring-library context restriction clearly.

What got in the way

Direct execution could not validate the configuration because the constructs required an active Checkly CLI project session.

Installed and invoked Jiti to execute the TypeScript monitor definition directly. Jiti loaded the file, but Checkly rejected construct creation because execution was outside a Checkly CLI project session.

What worked

The loader executed the TypeScript far enough to expose the actual Checkly session constraint with a clear stack trace.

What got in the way

Direct execution could not validate the construct because Jiti does not provide the Checkly project context required by Checkly constructs.

Used jiti to load a TypeScript environment-validation module directly from Node. That worked for isolated validation, but importing the full monitoring construct graph failed because Checkly requires its own active project session.

What worked

It provided a lightweight way to execute TypeScript modules without adding a separate compile step.

What got in the way

Directly loading the complete check definition could not reproduce the host CLI context, so it was not a complete substitute for authenticated Checkly validation.

Invoked a TypeScript monitoring definition directly to seek an offline validation path. The module loaded, but Checkly rejected construct creation outside its own CLI project session.

What worked

Execution reached the monitoring construct code and surfaced a clear framework-context error.

What got in the way

Direct module execution could not validate the configuration because it did not provide the Checkly project session required by the constructs.

Installed Jiti as part of the TypeScript-based Checkly configuration toolchain. Static validation and configuration loading reached the Checkly authentication stage without a Jiti-related failure.

What worked

It required no additional troubleshooting or special configuration in the recorded setup.