Your imports already say what your targets depend on.

The problem

Hand-written dependency lists drift.

In a modular app, every feature, client and helper is its own SwiftPM target. Someone adds import Analytics and forgets the manifest; someone removes the last use of Networking and the dependency stays forever. Builds break in CI, or worse, keep working with a graph nobody can reason about.

The source of truth is already in your files: the imports. PackageGenerator reads them and writes the manifest. This CLI is the part that reads them, fast enough to run on every change.

How it works

Plugin and CLI, one pass.

1. Describe targets

   You list target folders once in packageGenerator.yaml.

   Plugin

2. Hand them over

   The plugin resolves paths and writes a JSON list of targets, tests and excludes.

   Plugin

3. Scan every file

   The CLI parses each target's Swift files concurrently and writes each target's imports as JSON.

   This CLI

4. Write Package.swift

   The plugin drops Apple SDKs, maps imports to targets and products, and writes the manifest.

   Plugin

The contract

JSON in, JSON out.

The input names each target, its optional test target and paths to exclude. A bare path string, the original format, still works. The output lists each target's imported modules, sorted and deduplicated, with the target's path and its Resources folder if it has one. Both types ship in the PackageGeneratorModels library.

[
  {
    "target": { "path": "/App/Sources/Checkout", "name": "Checkout" },
    "test": {
      "path": "/App/Tests/CheckoutTests",
      "name": "CheckoutTests",
      "exclude": ["__Snapshots__"]
    }
  },
  "/App/Sources/Legacy"
]

[
  {
    "name": "Checkout",
    "isTest": false,
    "dependencies": ["Analytics", "Foundation", "Payments", "SwiftUI"],
    "path": "Sources/Checkout",
    "fullPath": "/App/Sources/Checkout",
    "resources": "Resources",
    "localDependencies": 0,
    "hasBiggestNumberOfDependencies": false
  },
  …
]

What it reads

Real Swift, parsed like the compiler does.

No regular expressions over your code: swift-syntax builds the syntax tree, so comments, strings and odd formatting never fool it.

Performance

Reads only what it needs.

Imports live at the top of a file, so the scanner finds the end of the last import declaration and parses only that much. Across 23,000 open-source Swift files it parses 9% of the bytes and finds exactly the imports a full parse finds.

p50 on an Apple silicon Mac, measured with package-benchmark on a synthetic package. Method and history: docs/performance.md.

Install

Most people never install it.

Add the plugin and it downloads the CLI as a prebuilt artifact bundle. Reach for the CLI directly only to script it or to build your own tooling on its JSON.

.package(
  url: "https://github.com/mackoj/PackageGeneratorPlugin.git",
  from: "1.0.6"
)

swift package plugin \
  --allow-writing-to-package-directory package-generator

git clone https://github.com/mackoj/PackageGeneratorCLI.git
cd PackageGeneratorCLI
swift build -c release
.build/release/package-generator-cli --help

// .product(name: "PackageGeneratorModels", package: "PackageGeneratorCLI")
import Foundation
import PackageGeneratorModels

let output = URL(fileURLWithPath: "imports.json")
let packages = try JSONDecoder().decode(
  [ParsedPackage].self, from: Data(contentsOf: output))
for package in packages where !package.isTest {
  print(package.name, package.dependencies)
}