swift package init --type executable: create a Swift package

swift package init --type executable creates a new Swift Package Manager project in the current directory: a Package.swift manifest and a Sources/ folder with the executable target's code. The package takes its name from the directory, or from --name. Build and run it with swift run; use --type library for a reusable module.

Create, build, run

mkdir Hello && cd Hello
swift package init --type executable
swift build                 # debug build in .build/debug
swift run                   # build and run the executable
swift build -c release      # optimized build in .build/release
swift test                  # run tests in Tests/

What the executable template creates

The getting-started guide on swift.org shows the layout for swift package init --name MyCLI --type executable:

.
├── Package.swift
├── Sources
│   └── MyCLI
│       └── MyCLI.swift
└── Tests
    └── MyCLITests
        └── MyCLITests.swift

Package.swift declares the package, its products and targets. Each folder under Sources/ is one target, and the folder name must match the target name in the manifest. The entry point is either a main.swift file with top-level code or a type marked @main; a target cannot have both. Build output goes to .build/ (change it with --scratch-path), which belongs in .gitignore.

Package types

Other useful options

Run swift package init --help to see the list for the installed toolchain; the template set and the test options depend on the Swift version.

Add a dependency

// swift-tools-version: 5.9
import PackageDescription

let package = Package(
    name: "Hello",
    dependencies: [
        .package(url: "https://github.com/apple/swift-argument-parser", from: "1.3.0"),
    ],
    targets: [
        .executableTarget(
            name: "Hello",
            dependencies: [.product(name: "ArgumentParser", package: "swift-argument-parser")]
        ),
    ]
)

swift package resolve       # fetch dependencies and write Package.resolved
swift package update        # move to the newest allowed versions

The first comment line, // swift-tools-version:, is required: it sets the minimum Swift version that can read the manifest and the manifest API available. swift package resolve records the exact versions it picked in Package.resolved; commit that file for executables so every build uses the same dependency versions. For a library, the version requirement in from: is what consumers see, so keep it as loose as your code allows.

FAQ