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.