pi-lens/dist/clients/dead-code-logger.js

Real-time code feedback for pi — LSP, linters, formatters, type-checking, structural analysis & booboo

/**
 * NDJSON telemetry for cross-file dead-code scans (#127). One event per
 * session_start scan per language, so we can answer: which languages get
 * scanned, how many findings, and how long the whole-project scan takes (the
 * input to phasing decisions in the issue). Mirrors `ast-grep-tool-logger.ts`
 * for shape + size-based rotation.
 */
import * as path from "node:path";
import { isTestMode } from "./env-utils.js";
import { getGlobalPiLensDir } from "./file-utils.js";
import { createNdjsonLogger } from "./ndjson-logger.js";
const LOG_DIR = getGlobalPiLensDir();
const LOG_FILE = path.join(LOG_DIR, "dead-code.log");
const LOG_BACKUP_FILE = path.join(LOG_DIR, "dead-code.log.1");
const MAX_LOG_BYTES = Math.max(128 * 1024, Number.parseInt(process.env.PI_LENS_DEAD_CODE_LOG_MAX_BYTES ?? "1048576", 10) ||
    1048576);
const writer = createNdjsonLogger({
    filePath: LOG_FILE,
    maxBytes: MAX_LOG_BYTES,
    backupPath: LOG_BACKUP_FILE,
});
/**
 * Append one scan event. Fire-and-forget: telemetry must never break a scan, so
 * every fs error is swallowed. Skipped under test mode to keep the suite from
 * writing to the user's real ~/.pi-lens.
 */
export function logDeadCodeScan(event) {
    if (isTestMode())
        return;
    writer.log({ ts: new Date().toISOString(), ...event });
}
/** Resolve once all enqueued dead-code writes are on disk (tests/shutdown). */
export function flushDeadCodeLog() {
    return writer.flush();
}