// 示例：一个简化的依赖关系分析脚本
const fs = require('fs');
const path = require('path');
const { execSync } = require('child_process');

// 假设我们有一个仓库列表
const repos = ['app-main', 'lib-utils', 'lib-ui', 'lib-api'];

// 存储依赖图
const dependencyGraph = {};

repos.forEach(repo => {
  const packageJsonPath = path.join(__dirname, `../${repo}/package.json`);
  if (fs.existsSync(packageJsonPath)) {
    const pkg = JSON.parse(fs.readFileSync(packageJsonPath, 'utf-8'));
    const deps = { ...pkg.dependencies, ...pkg.devDependencies };
    
    // 过滤出内部仓库依赖
    const internalDeps = Object.keys(deps).filter(dep => dep.startsWith('@company/'));
    
    dependencyGraph[`@company/${repo}`] = internalDeps;
  }
});

console.log('静态依赖图谱:');
console.log(JSON.stringify(dependencyGraph, null, 2));
// 输出可能类似：
// {
//   "@company/app-main": ["@company/lib-ui", "@company/lib-api"],
//   "@company/lib-ui": ["@company/lib-utils"],
//   "@company/lib-api": ["@company/lib-utils"],
//   "@company/lib-utils": []
// }

# 示例：使用 Nx 计算受某个仓库变更影响的范围
nx affected:apps --base=main~1 --head=main

# 这条命令会分析当前分支与 main 分支的差异，
# 找出哪些应用（apps）被更改的库（libs）所影响。

// 使用 dependency-cruiser 进行配置和检测
// .dependency-cruiser.js 配置文件
module.exports = {
  forbidden: [
    {
      name: 'no-circular',
      severity: 'error',
      comment: '禁止循环依赖',
      from: {},
      to: {
        circular: true // 检测到任何循环依赖即报错
      }
    },
    {
      name: 'no-orphans',
      severity: 'warn',
      comment: '检测未被任何应用依赖的“孤儿”库',
      from: { pathNot: '^(apps/)' }, // 从非应用目录出发
      to: { pathNot: '^(apps/)' }, // 到非应用目录结束
      ... // 复杂规则，用于识别未被任何最终应用使用的库
    }
  ],
  options: {
    doNotFollow: 'node_modules'
  }
};

// 在根目录或共享配置中定义允许的版本范围
// .nvmrc, .npmrc 或 自定义的版本检查脚本
"allowedDependencies": {
  "@company/utils": "^2.0.0",
  "lodash": "^4.17.21"
}

# 示例：GitLab CI 配置，利用缓存和 needs 关键字实现依赖构建流水线
stages:
  - analyze
  - build-deps
  - build-app

analyze-deps:
  stage: analyze
  script:
    - ./scripts/analyze-affected-repos.sh $CI_COMMIT_SHA $CI_MERGE_REQUEST_TARGET_BRANCH_SHA > affected-repos.txt
  artifacts:
    paths:
      - affected-repos.txt

build-lib-utils:
  stage: build-deps
  script:
    - echo "Building lib-utils..."
    - cd lib-utils && npm install && npm run build
  needs: ["analyze-deps"]
  rules:
    - if: $CI_COMMIT_BRANCH
      exists:
        - affected-repos.txt
      # 仅当 affected-repos.txt 中包含 lib-utils 时才运行此 job
      when: on_success
    - when: never

build-app-main:
  stage: build-app
  script:
    - echo "Building app-main..."
    - cd app-main && npm install
    # 假设使用 file: 协议链接本地构建好的 lib-utils
    - npm link ../lib-utils
    - npm run build
  needs: ["build-lib-utils"] # 显式声明依赖关系
  rules:
    - if: $CI_COMMIT_BRANCH
      exists:
        - affected-repos.txt
      when: on_success
    - when: never

// 一个简单的基于 D3.js 的可视化思路（伪代码）
// 假设我们从后端 API 获取了 graphData
fetch('/api/dependency-graph')
  .then(res => res.json())
  .then(graphData => {
    const nodes = graphData.nodes; // [{id: '@company/app-main', group: 1}, ...]
    const links = graphData.links; // [{source: '@company/app-main', target: '@company/lib-ui'}, ...]

    const simulation = d3.forceSimulation(nodes)
      .force('link', d3.forceLink(links).id(d => d.id).distance(100))
      .force('charge', d3.forceManyBody().strength(-300))
      .force('center', d3.forceCenter(width / 2, height / 2));

    // ... 使用 d3 绘制节点和连线
    const link = svg.append('g')
      .selectAll('line')
      .data(links)
      .enter().append('line')
      .attr('stroke', '#999')
      .attr('stroke-opacity', 0.6);

    const node = svg.append('g')
      .selectAll('circle')
      .data(nodes)
      .enter().append('circle')
      .attr('r', 5)
      .attr('fill', d => colorScale(d.group));
  });