@revola-ai/video-craft 0.2.1

package/src/sourceCheck.ts

@@ -0,0 +1,55 @@
+import { relative, sep } from "node:path";
+import { globSync } from "tinyglobby";
+import { Project, ts } from "ts-morph";
+import type { SourceCheck, SourceFinding } from "./types";
+
+const toPosix = (p: string) => p.split(sep).join("/");
+
+const newProject = () =>
+  new Project({
+    skipAddingFilesFromTsConfig: true,
+    compilerOptions: { allowJs: true, jsx: ts.JsxEmit.ReactJSX },
+  });
+
+export function checkFile(check: SourceCheck, absPath: string, relPath: string, root: string): SourceFinding[] {
+  return check.run(newProject().addSourceFileAtPath(absPath), relPath, root);
+}
+
+/** The files a check runs over, under an EXPLICIT scan root. Exported so the
+ *  corpus test can assert a rule's globs match something. There is
+ *  deliberately no default root: this package runs installed inside consumer
+ *  repos, where any walk-up-from-module-location guess resolves to the wrong
+ *  tree, so every caller says which tree it means. */
+export function matchedFiles(check: SourceCheck, root: string): string[] {
+  return globSync(check.include, {
+    cwd: root,
+    absolute: true,
+    ignore: [
+      // Test files are not scenes; broad per-project globs would otherwise
+      // sweep them into every check's blast radius.
+      "**/node_modules/**", "**/.worktrees/**", "**/04_exports/**", "**/*.test.{ts,tsx,jsx}",
+      // Webpack output is not scene source either. build/ is gitignored, so
+      // whether it exists depends on what was last run on this machine: a
+      // locally bundled qse-investor-video put 161 minified-bundle findings
+      // into the corpus and turned the suite red only where someone had
+      // happened to run `npm run build`. A check whose verdict varies by
+      // machine is a flake, not a guard.
+      "**/build/**",
+      ...(check.exclude ?? []),
+    ],
+  }).sort();
+}
+
+export function runSourceCheck(check: SourceCheck, root: string): SourceFinding[] {
+  // One Project for the whole pass, same reasoning as anchors.ts: constructing
+  // a compiler host is the expensive part, and these checks are syntactic, so
+  // files sharing a Project stay independent anyway. A fresh Project per file
+  // across a ~230-file corpus is what blows the vitest 30s timeout.
+  const project = newProject();
+  const findings: SourceFinding[] = [];
+  for (const abs of matchedFiles(check, root)) {
+    const file = project.addSourceFileAtPath(abs);
+    findings.push(...check.run(file, toPosix(relative(root, abs)), root));
+  }
+  return findings;
+}