HSLG Media

check_dependencies.cjs

check_dependencies.cjs

Source file: tools/governance/check_dependencies.cjs

Module: tools-governance

Size: 96 lines

SHA-256: 5cae195e715f029028086f5602ab7ec4f89a95899dcd562d40ee3c822b42f2d4

Responsibility

Verifies dependency, documentation, source and release boundaries without suppressing failures.

Declared entry points

  • ts — source line 11.
  • fs — source line 12.
  • path — source line 13.
  • root — source line 14.
  • slash — source line 15.
  • relative — source line 16.
  • errors — source line 17.
  • starts — source line 18.
  • shared — source line 19.
  • mobile — source line 20.
  • demo — source line 21.
  • forbidden — source line 22.
  • excluded — source line 23.
  • files — source line 24.
  • collect — source line 25.
  • file — source line 29.
  • configPath — source line 36.
  • raw — source line 37.
  • config — source line 39.
  • edges — source line 46.
  • sourcePath — source line 48.
  • source — source line 49.
  • dependency — source line 51.
  • result — source line 55.

Imports and dependencies

  • Line 11: const ts = require('typescript');
  • Line 12: const fs = require('node:fs');
  • Line 13: const path = require('node:path');

Behaviour and audit locations

  • Line 8: * transpiler or framework. Vite/Capacitor build setup is a later milestone.
  • Line 54: if (shared(sourcePath) && /^@(?:capacitor|capgo|capawesome)\//.test(specifier)) errors.push(${sourcePath}: shared code cannot import native SDK ${specifier});

Relationship to the system

This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.

Change verification

Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.